Daniel Pistelli

.NET Internals and Native Compiling

Rating: 2 votes, 1.50 average.

Strictly speaking it means converting the MSIL code of a .NET assembly to native machine code and then removing the MSIL code from that assembly, making it impossible to decompile it in a straightforward way. The only existing tool to native compile .NET assemblies is the Salamander.NET linker which relies on native images to do its job. The "native images" (which in this article I called "Native Framework Deployment") technique is quite distant from .NET internals: one doesn't need a good knowledge of .NET internals to implement it. But, as the topic is, I might say, quite popular, I'm going to show to the reader how to write his Native Framework Deployment tool if he wishes to. However, the article will go further than that by introducing Native Injection, which means nothing else than taking the JIT's place. Even though this is not useful for commercial protections (or whatever), it's a good way to play with JIT internals. I'm also going to introduce Native Decompiling, which is the result of an understanding of .NET internals. I'm also trying to address another topic: .NET Virtual Machine Protections.

I hope you'll enjoy this.

P.S. As always, if you notice typos, please report them.

Submit ".NET Internals and Native Compiling" to Digg Submit ".NET Internals and Native Compiling" to del.icio.us Submit ".NET Internals and Native Compiling" to StumbleUpon Submit ".NET Internals and Native Compiling" to Google

Updated May 25th, 2008 at 10:53 by Daniel Pistelli