Protect DLL
-
Hey guyz, I am currently working on a project and using many ddl files. My question is.. How to protect those dll files so that when I deploy it on the client machine.. nobody can leech and use it for themselves? I hope you guyz got my point. Thanks.
------------------------------------------------------------------ Life would have been much easier if I had the source-code!!
-
Hey guyz, I am currently working on a project and using many ddl files. My question is.. How to protect those dll files so that when I deploy it on the client machine.. nobody can leech and use it for themselves? I hope you guyz got my point. Thanks.
------------------------------------------------------------------ Life would have been much easier if I had the source-code!!
Swader wrote:
nobody can leech and use it for themselves?
You can protect the methods by using
internalaccess modifier. Internal members can be access only in the same assembly.
-
Swader wrote:
nobody can leech and use it for themselves?
You can protect the methods by using
internalaccess modifier. Internal members can be access only in the same assembly.
Oke. I know that. But the problem is.. I use the same dll for other apps too. Its kinda a shared dll. What to do about that? Also.. Is there a way where I can merge all the dll's in one single file or any other way to manage them so that it doesnt look ugly :) Thanks for the help.
------------------------------------------------------------------ Life would have been much easier if I had the source-code!!
-
Oke. I know that. But the problem is.. I use the same dll for other apps too. Its kinda a shared dll. What to do about that? Also.. Is there a way where I can merge all the dll's in one single file or any other way to manage them so that it doesnt look ugly :) Thanks for the help.
------------------------------------------------------------------ Life would have been much easier if I had the source-code!!
Make sure only you can call those libraries. You basically just need to have some mechanism to put someone off (the idea of stealing), by making it break when they attempt to use it.
xacc.ide
The rule of three: "The first time you notice something that might repeat, don't generalize it. The second time the situation occurs, develop in a similar fashion -- possibly even copy/paste -- but don't generalize yet. On the third time, look to generalize the approach." -
Hey guyz, I am currently working on a project and using many ddl files. My question is.. How to protect those dll files so that when I deploy it on the client machine.. nobody can leech and use it for themselves? I hope you guyz got my point. Thanks.
------------------------------------------------------------------ Life would have been much easier if I had the source-code!!
Oke.. Allright.. So basically.. there is no simple way of safeguarding a dll. So.. Atleast.. is there a way.. I can organize all the ddl's a subfolder? Suppose.. I have an application say.. Abc.exe So when I Build it.. The exe and the dll gets copied to the bin folder. How can I make it store all the dll in a subfolder? Thanks.
------------------------------------------------------------------ Life would have been much easier if I had the source-code!!
-
Oke.. Allright.. So basically.. there is no simple way of safeguarding a dll. So.. Atleast.. is there a way.. I can organize all the ddl's a subfolder? Suppose.. I have an application say.. Abc.exe So when I Build it.. The exe and the dll gets copied to the bin folder. How can I make it store all the dll in a subfolder? Thanks.
------------------------------------------------------------------ Life would have been much easier if I had the source-code!!
Swader wrote:
How can I make it store all the dll in a subfolder?
Create a sub folder inside bin directory, copy dll's over there, and refer it from there.
-
Swader wrote:
How can I make it store all the dll in a subfolder?
Create a sub folder inside bin directory, copy dll's over there, and refer it from there.
So will that work the same way.. even if I were to change the location of the folder or after I deploy?
------------------------------------------------------------------ Life would have been much easier if I had the source-code!!
-
So will that work the same way.. even if I were to change the location of the folder or after I deploy?
------------------------------------------------------------------ Life would have been much easier if I had the source-code!!
You can use a licensing scheme like CryptoLicensing: 1. Expose a public method like "SetLicenseCode" 2. Call this method with a valid license key. 3. The dll methods ill work only if a valid license key has been provided. This will ensure that others cannot use your dll.