NDepend Blog

Improve your .NET code quality with NDepend

Influencer: The Power To Change Anything < Plus ◎ >

Adjust physical surroundings, tools, and data to make the right behavior easier and the wrong one harder. Key Takeaways for Change Agents

: Identify the 2 or 3 high-leverage actions that, if changed, will lead to the desired result. Influencer: The Power to Change Anything

Before applying the six sources, an influencer must focus their efforts on high-leverage areas: Adjust physical surroundings, tools, and data to make

Provide training and "deliberate practice" so people have the actual skills to perform the new behavior. Social Social : Sometimes people want to change but

: Sometimes people want to change but lack the skills or environmental support. Fixing "Ability" (Sources 2, 4, and 6) is often more effective than trying to increase "Motivation".

For further insights, you can find the book and reader reviews on platforms like Amazon or Medium . Influencer: The Power to Change Anything - Amazon.com

Comments:

  1. Ivar says:

    © 2026 Polaris Elegant Grid

    I can imagine it took quite a while to figure it out.

    I’m looking forward to play with the new .net 5/6 build of NDepend. I guess that also took quite some testing to make sure everything was right.

    I understand the reasons to pick .net reactor. The UI is indeed very understandable. There are a few things I don’t like about it but in general it’s a good choice.

    Thanks for sharing your experience.

  2. David Gerding says:

    Nice write-up and much appreciated.

  3. Very good article. I was questioning myself a lot about the use of obfuscators and have also tried out some of the mentioned, but at the company we don’t use one in the end…

    What I am asking myself is when I publish my .net file to singel file, ready to run with an fixed runtime identifer I’ll get sort of binary code.
    At first glance I cannot dissasemble and reconstruct any code from it.
    What do you think, do I still need an obfuscator for this szenario?

    1. > when I publish my .net file to singel file, ready to run with an fixed runtime identifer I’ll get sort of binary code.

      Do you mean that you are using .NET Ahead Of Time compilation (AOT)? as explained here:
      https://blog.ndepend.com/net-native-aot-explained/

      In that case the code is much less decompilable (since there is no more IL Intermediate Language code). But a motivated hacker can still decompile it and see how the code works. However Obfuscator presented here are not concerned with this scenario.

  4. OK. After some thinking and updating my ILSpy to the latest version I found out that ILpy can diassemble and show all sources of an “publish single file” application. (DnSpy can’t by the way…)
    So there IS definitifely still the need to obfuscate….

Comments are closed.