Securing DLL's
-
Hi, I have some class libraries, which I dont want the client to use. How can we secure our dll in such a way that if someone else adds our dll to his project then it gives some error or may e do not allow to add it. Or is tehre any other way by whihc we need not send the DLL in the setup.
-
Hi, I have some class libraries, which I dont want the client to use. How can we secure our dll in such a way that if someone else adds our dll to his project then it gives some error or may e do not allow to add it. Or is tehre any other way by whihc we need not send the DLL in the setup.
the problem is if you make it so that your client can't use it, then neither can you. You can implement some security by requiring a certain key be passed in to your method calls, and you can protect against reflection and disassembly by Obfuscating your dll. You can use Dotfuscator Community Edition included with VS2005/8 to do that for you. Hope this helps! Greg