What is an .exe file stub?

Question

I\'m learning how to obfuscate my assembly using .NET Reactor.

One option is to "Generate a native x86 EXE file stub," whi

Answer 1

Though your question was some time ago, I thought I'd share an answer:

Have you ever used a Tool like Reflector, ILSpy or dotPeek? Those tools can be used to generate the source from an managed assembly. If you use that native x86 stub, those tools should tell you "Cannot open unmanaged dll" (or something similar) - according to the developer.

Answer 2

All executable files have a single entry point (in C, it's the MAIN function).

For Dot Net applications, there is a standard code and file structure - to ensure that the corresponding framework is available - to locate different objects such as resources.

It is possible to analyze/uncompile such an application.

DOT NET REACTOR can replace the usual starting code with a proprietary code so that uncompilers think that its a native executable - not depending on DOT NET Framework and having proprietary file structure for different objects. So that they cannot even start to uncompile anything.

This feature is why I'm using Reactor. However early versions (< 4.7) have produced files that have been confused as virus or Trojans by AVAST.