Comments
3 comments
-
Thanks for your post and sorry to hear you're running into some trouble with SmartAssembly!
SmartAssembly will automatically exclude any public members from dlls to make sure that other assemblies can still call on those members. Just to confirm, are the classes and methods that aren't being obfuscated public members? (For other reasons that SmartAssembly may exclude code, kindly take a look here.) -
This is stupid. My useful are stored in the root directory. They can still modify my program
-
Hi @Imcool, so sorry if the tool doesn't meet your needs!
We have a request for the ability to force obfuscation on public types in DLLs (SA-1569) and I've +1'd this, but I want to be honest that this isn't in the road map at the moment. The only workaround would be to move the important bits of code into private members that can be obfuscated.
So sorry again as I know that's not ideal. Please let us know if you have any other questions.
Add comment
Please sign in to leave a comment.
My configuration