NDepend Blog

Improve your .NET code quality with NDepend

Рґсѓрґрѕр¶рѕрёрє 11 Сѓрµсђрёсџ (2022) Guide

In Episode 11 of the 2022 Russian detective thriller The Artist ( Художник ), the investigation into the "Dead Head" gang reaches a critical turning point as internal suspicions and shocking discoveries surface. Key Plot Points

: October 2022 (part of the 16-episode first season). In Episode 11 of the 2022 Russian detective

You can find the full series on major Russian streaming platforms like Premier , IVI , and Kinopoisk . : The realization grows that the gang's robberies

: The realization grows that the gang's robberies and murders are merely a cover for a much larger, more sinister objective. Episode Details and Kinopoisk .

💡 : This episode shifts the focus from external pursuit to internal betrayal, setting the stage for the dramatic reveal of the "mole" in the subsequent chapters. To help you find exactly what you're looking for:

Comments:

  1. Ivar says:

    © 2026 Prime Forge

    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.