NDepend Blog

Improve your .NET code quality with NDepend

Christophe - Confession(s) 1964-1968 - 2022 Link

: The 1968 title track that anchors the compilation.

Confession(s) 1964 - 1968 - Compilation by Christophe | Spotify Christophe - Confession(s) 1964-1968 - 2022

: Described as an intriguing, more experimental piece for its time. : The 1968 title track that anchors the compilation

is a posthumous compilation album by the legendary French singer Christophe , released on November 18, 2022 , by Capitol Music France . This collection serves as a retrospective of the artist's formative years, capturing the transition of Daniel Bevilacqua into the "dandy of French pop". Overview of the Era (1964–1968) This collection serves as a retrospective of the

: Noted for its "Dantesque dramaturgy" and complex arrangements.

During this period, Christophe emerged as a major figure in the yé-yé movement and beyond. After an unsuccessful first single ("Reviens Sophie") in 1963, he skyrocketed to fame in 1965 with the massive hit . The years that followed saw him experiment with dramatic arrangements and diverse styles, from mischievous blues to baroque pop, laying the groundwork for his later more sophisticated electronic works. Tracklist and Musical Highlights

Comments:

  1. Ivar says:

    © 2026 — New Vista

    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.