We are currently using Redgate SmartAssembly 6.9.0.114 to obfuscate a C# 7.3 / .NET Framework 4.8 application. We have configured SmartAssembly with the highest available obfuscation settings, but during security assessments, our team is still able to reverse‑engineer and understand a large portion of the code using tools like ILSpy.
Given this situation, we would like to understand:
- Are there additional SmartAssembly configurations or best practices that can improve resistance against reverse engineering?
- Are there known limitations of SmartAssembly (or obfuscation in general) when it comes to modern decompilers like ILSpy?
- What alternative approaches or tools are recommended for stronger code protection in .NET applications?
Any guidance or real‑world recommendations would be greatly appreciated.
We are currently using Redgate SmartAssembly 6.9.0.114 to obfuscate a C# 7.3 / .NET Framework 4.8 application. We have configured SmartAssembly with the highest available obfuscation settings, but during security assessments, our team is still able to reverse‑engineer and understand a large portion of the code using tools like ILSpy.
Given this situation, we would like to understand:
Any guidance or real‑world recommendations would be greatly appreciated.