I am currently working with a licensed version of .NET Reactor. I’ve been experimenting with it to protect my .NET assemblies, but I’ve found that the sheer number of options and the complexity of the tool’s structure can be a bit overwhelming.
I've tried a few basic configurations, but I'm looking to achieve a more sophisticated level of protection. Specifically, I’m interested in:
Optimizing Obfuscation: Which combinations of Control Flow Obfuscation and String Encryption do you find most effective without breaking the application's stability?
Cryption & Protection: Does anyone have experience with the Native EXE Generation or NecroBit features for anti-tampering?
Stability Issues: Are there specific settings that I should avoid when targeting modern .NET versions (like .NET 6/7/8) to prevent runtime crashes?
If anyone has a "best practices" guide or a solid configuration template for hardening an assembly, I would greatly appreciate your insights.
I've tried a few basic configurations, but I'm looking to achieve a more sophisticated level of protection. Specifically, I’m interested in:
Optimizing Obfuscation: Which combinations of Control Flow Obfuscation and String Encryption do you find most effective without breaking the application's stability?
Cryption & Protection: Does anyone have experience with the Native EXE Generation or NecroBit features for anti-tampering?
Stability Issues: Are there specific settings that I should avoid when targeting modern .NET versions (like .NET 6/7/8) to prevent runtime crashes?
If anyone has a "best practices" guide or a solid configuration template for hardening an assembly, I would greatly appreciate your insights.