NDepend Blog

Improve your .NET code quality with NDepend

Alan Walker - Even If You Die [ New Song 2022 ] -

This track is a prime example of the "Walker Style" genre—music produced by emerging artists that fits the atmospheric and melodic boundaries of Alan Walker’s Official Discography .

Most uploads surfaced in April and October 2022 , coinciding with the launch of Walker's actual Walkerverse project. Alan Walker - Even If You Die [ New Song 2022 ]

Videos for the song typically feature the iconic Walker Aesthetic , including characters in hoodies, masks, and futuristic urban or natural landscapes. Top 2022 Official Releases This track is a prime example of the

Hits like " The Drum ," " Shut Up " (feat. UPSAHL), and " Catch Me If You Can " (with Sorana). Top 2022 Official Releases Hits like " The

You can experience the fan-produced 'Walker Style' version of the track here: Alan Walker - Even If You Die [ New Song 2022 ] Walker Style Music YouTube• Apr 8, 2022 Alan Walker - Even If You Die [ New Song 2022 ]

While "Even If You Die" was a viral fan favorite, Alan Walker’s official 2022 highlights included:

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.