Obfuscation Attributes

Feb 5, 2013 at 6:04 PM
Does Confuser honour .net obfuscation attributes ?
JP
Coordinator
Feb 7, 2013 at 4:23 AM
Hi,
Confuser does not process ObfuscationAttributes, but you can customize the protection using the UI.
Feb 28, 2013 at 10:47 AM
Edited Feb 28, 2013 at 10:48 AM
Hi
If, for example, I have various common base DLLs which 2 different projects use.
What is the approach I should for the two projects? Do I have to customize protection of the common DLLs twice? And if there is a change in the common base DLLs, do I have to go through ALL the projects that use them and customize them all?
Thanks
JP
Feb 28, 2013 at 10:52 AM
Hi
If, for example, I have various common base DLLs which 2 different projects use.
What is the approach I should for the two projects. Do I have to customize protection of the common DLLs twice? And if there is a change in the common base DLLs, do I have to go through ALL the projects that use them and customize them all?
Thanks
JP
Coordinator
Mar 30, 2013 at 9:27 AM
Hi,
This depends on the nature of your common base DLL.
If your common DLL is intended for internal use, I recommend you create 2 crproj for the 2 project, each includes their own common DLL configuration because this allow Confuser to have greater freedom in obfuscating the projects. In this case, you can copy the protection settings using text editor as *.crproj is a XML file.
If your common DLL is shared between different product(note that a product can have multiple C# projects), I recommend you create a crproj solely for the common DLL and let the other project reference the obfuscated DLL to ensure compatibility of the API.
Apr 24, 2013 at 8:44 AM
I just submitted a patch, which adds support for ObfuscationAttribute to confuser. You might want to try it out.