How do you secure a .NET (c#) assembly?

Question

.NET

Good time.
Faced with the need to protect the assembly from disassembly, if I may say so in relation to .NET.
Tell me who covers what, and how success helps to protect? I tried the demo version of the .net reactor, but when the parameters are set to the maximum, it is removed by the stock de4dot (maybe it's because the demo? although it says that the functionality is not cut down. Or am I doing something wrong).

Answer 1

The only reliable and simple option is to take critical code to native assemblies and pinvok them or make wrappers on c++/cli. There can be a lot of problems with the obfuscator, for example if you are using remouting or wpf.

Answer 2

Have a look at SmartAssembly. Many people use it.

Answer 3

Try to combine several oscillators. For example .Net Reactor + ConfuserEx. After that, remove the signatures that obfuscators leave (detect it easy). Let's say ConfuserEx leaves an attribute with the namespace name, but it's better to cut it out, open sort. In general, it will help protect, although you will have to dance with a tambourine.
It is desirable to make a wrapper in C ++, it will greatly increase the entry threshold if someone wants to open it.
The assembly will be harder to open, but the detections will be from antiviruses (Heuristic analysis).