NDepend Blog

Improve your .NET code quality with NDepend

Casey Parkers | Winter Break

When the snow is fresh, Casey is rarely found indoors. The winter landscape offers unique opportunities for activity that aren't available at other times of the year.

The semester had been brutal. Casey had spent months running on caffeine and five hours of sleep, driven by the intense pressure of pre-med requirements. When a classmate offered the use of their family’s off-grid cabin for the three-week hiatus, Casey jumped at the chance. Total isolation. No Wi-Fi, no cell service, no expectations. casey parkers winter break

First, Casey abandoned the spacious master bedroom, dragging a mattress into the small kitchen closer to the wood stove. Next came the layering—three pairs of socks, thermal underwear, two sweaters, and a heavy winter coat. To block the freezing drafts, Casey stuffed academic textbooks and spare blankets into the gaps around the windows and doors. When the snow is fresh, Casey is rarely found indoors

Comments:

  1. Ivar says:

    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.