Practice for hiding executable code of compiled applications

Question

This is standard practice for decompiling and reversing .net assemblies.

I would like to release some plugin assemblies that will be added to existing applications, but I do not want others to use them.

How can I hide the source of these assemblies?

Answer 1

It is theoretically impossible to achieve 100% protection if you do not control the target equipment. If the CPU is able to fulfill it, given sufficient time and knowledge, a person can read it. This is not even limited to C # (although it is usually easier to do this in managed languages). You can use an obfuscator such as Dotfuscator or XenoCode to make understanding decompiled code more difficult. If you are really worried, you should go to the server application.

Answer 2

You can use the obfuscator tool , this will help, but reverse engineering will still be very possible.

, , . , , - .

Answer 3

; . , . , , .

Answer 4

, host CLR CLR COM api, . , , .

Answer 5

, steganography. , CodeProject, . "" 1 12, . -, .

"Phoenix Protector", , .NET-, , , .

, , , .

Answer 6

, DLL, . 100% , .

, Crypto Obfuscator, dll exe, DLL , Reflector.