Our requirement is being able to integrate our DLLs with ClickOnce. Dotfuscator does the obfuscation job nicely but the obfuscated DLLs cannot be deployed with ClickOnce on customer side. On our side, we can handle it perfectly. Moreover, the obfuscated assemblies sometime crash our .NET CF app. It turns out to a solution that creates a temporary source and obfuscates it before compiling with VS. This ensures that the compiled assembly can be integrated with ClickOnce and fully compatible with .NET CF. What is the best tool to obfuscate C# SOURCE CODE (not assemblies)?
It does not allow me to download!
Mark Attwood
2010-05-30 06:32:35
@markattwood: Send a note to SD asking for an evaluation version.
Ira Baxter
2010-05-30 07:26:07
They actually obfuscate even the System.Collection namespace which is not what we want.
Mark Attwood
2010-05-30 21:38:51
The SD obfuscator will obfuscate only the names you ask it to. If you want to leave the System Collection namespace member names unobfuscated, that's easy enough to do.
Ira Baxter
2010-05-31 00:14:13
+1
A:
{SmartAssembly} - Simple, efficient, brilliant and comes with more than just obfuscation.
We currently use it with ClickOnce and it supports the Compact Framework - You just add a post build script and you're done. It also has various levels of security, so you can simply go by trial and error to the most compatible level of protection.
Kyle Rozendo
2010-05-30 09:48:42
+1 while I don't use it, they are using and happy with it where I'm working
kenny
2010-05-30 10:45:36
I think I need to explain the situation clearly. Our complied DLLs need to be obfuscated and shipped to our customers. On customer side, they may want to integrate our DLLs with their product and deploy it with the ClickOnce tool. The problem is the obfuscated DLLs with all obfuscator tools we have tried on the market are not compatible with CLickOnce. Your solution is for your side, not customer side.
Mark Attwood
2010-05-30 21:37:28
@Mark - There's no difference then. You can exclude certain signatures for obfuscation so that people can use your library, and then the ClickOnce just deploys the already obfuscated library.
Kyle Rozendo
2010-05-31 05:55:57
A:
You don't need to obfuscate the source code, you just need an assembly obfuscator which supports ClickOnce. Crypto Obfuscator supports this - it performs the obfuscation as part of the build process, so the assemblies that end up being in the ClickOnce manifest and setups are already obfuscated.
logicnp
2010-06-15 05:26:56
A:
In most cases, if you're asking this question, you're using the wrong language (and framework). Many of the things that make .NET powerful are incompatible with obfuscation, so you might as well be using native C++.
ClickOnce might be an exception to this, but I think it still will severely limit the obfuscation level you can use.
If you really want to protect your IP, you should host a web service so your proprietary code never leaves your computer. Once your code is running on someone else's CPU, you've lost the battle to hide it.
Ben Voigt
2010-06-15 05:51:11