Confusing projects with common base DLLs

Feb 28, 2013 at 11:33 AM
If, for example, I have various common base DLLs which 2 different projects are using.
What is the approach I should do for the two projects? Do I have to customize protection of the common DLLs twice? And then, 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?
Mar 30, 2013 at 8:27 AM
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.