NDepend Blog

Improve your .NET code quality with NDepend

Promisiuni_alin_si_emima_timofte_ft_vlad_moldov... 〈Secure ›〉

It follows a standard worship build, starting with intimate verses and swelling into a powerful, anthemic chorus and bridge that encourages congregational participation. Key Takeaway for Reflection

The lyrics emphasize that while the world changes, God's promises remain "Yes and Amen." The song draws on several key biblical concepts: promisiuni_alin_si_emima_timofte_ft_vlad_moldov...

The central message of the song is . It serves as a "helpful paper" or spiritual reminder that God's history of faithfulness is the best indicator of His future reliability. For those looking for a study or meditation aid, the song encourages looking back at past "victories" to find the strength to face current challenges. It follows a standard worship build, starting with

It reflects Joshua 21:45 , stating that not one of God’s good promises has failed. For those looking for a study or meditation

The song features a collaborative vocal arrangement, blending the harmonious tones of Alin and Emima with Vlad Moldovan’s emotive delivery.

"Promisiuni" is a contemporary Christian worship song by , featuring Vlad Moldovan . The song is a Romanian version of "Promises" (originally by Maverick City Music), focusing on the faithfulness and unchanging nature of God's word. Theological Themes & Scriptural Foundations

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.