Click here to Skip to main content
15,670,097 members
Please Sign up or sign in to vote.
0.00/5 (No votes)
See more:
Hi All,

I am working on project for .NET project requiring Obfuscation, here we are working on specific modules comprising 12 dll's(all of .NET dll's), I need clarification on few aspects related to .NET Obfuscation of Dll's (since I am new to providing obfuscation for .NET dll's).

Using Dotfuscator tool (professional editon 4.5v) in GUI Standalone mode,

1. How we need to ensure obfuscation of dll in release mode., since, the dll obfuscation to be effected in Debug mode, could not the same dll's hold good in release mode too ?

I heard the Debug mode would be discarded by the Obfuscation tool(DotFuscator tool).

2. If multiple binaries are output by the build for same assembly/module.,

assuming C:\MyProject\Updatedll\Bin\UpdateDll1.dll and similarly C:\MyProject\SubProject\MinorUpdate\UpdateDll1.dll both these dll's are one and same, but when I build the project using DotObfuscator, I need to run the tasks again for above dll's(UpdateDll1.dll) if could it be uniquely handled ?

3. What are procedures/steps to load/build assemblies of dll's only instead of exe's in DotObfuscator tool.

Details: VS 2010 IDE, Windows 7 O/S. Using Perforce Version control tool.

Any help in resolving the above would be much appreciable.

Thanks & Regards,


This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900