Framework Version Changes Depending on Protection Rules #558
Unanswered
Sanada-MQJ
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi.
I am using ConfuserEx v1.6.0 to obfuscate a DLL built for .NET Framework 2.0. However, when I reference the obfuscated DLL from my application, I encounter a framework version mismatch error.
Using DotPeek to inspect the output, I noticed that the target framework version of the obfuscated DLL has changed to .NET Framework 4.0.
I conducted several experiments and observed the following behaviors:
It seems that the required minimum framework version varies depending on the applied protection settings.
Is this expected behavior? Are there any guidelines regarding how different protection methods affect the target framework version?
Thank you for your support.
Beta Was this translation helpful? Give feedback.
All reactions