how i provide security for dll file

Question

1.00/5 (1 vote)

See more:

VB

1)We have developed a library to use it with our software & we build it as DLL
2)We developed  a application using our library

Now what I need  that no other user can use my library in his application for example  when i give my application to end user that library is going to be added in setup, and if we dont protect it , any user can use it as reference in a .net project and can use my library and develop his own program , I need some thing that only my application will have access to my library and no other program can use it as reference and access its features

Posted 11-Mar-13 20:37pm

seema jadhav

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

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

Sergey Alexandrovich Kryukov · Answer 1 · 2013-03-11T20:46:00

Solution 1

I recently read claims of one of the companies providing a solution for reverse engineering. They claim that they can reverse-engineer any .NET product with ease, even if it it protected by most expensive and reputed and powerful protection systems, especially if this protection software is well-known. You know, I tent to trust those claims. They really can do it.

As to the use of the DLL, if your application assemblies can use it, any other developer can do it. All you can do is some obfuscation. Obfuscation can make understanding of your class library much more difficult, and the use extremely annoying.

I would not bother at all. Regular users will not use it anyway, and those who may badly need your library (do you think they really will want it?) will always find a way.

—SA

Posted 11-Mar-13 20:46pm

Sergey Alexandrovich Kryukov

Comments

seema jadhav 12-Mar-13 3:21am

yes,but how can implement the security.

seema jadhav 12-Mar-13 3:35am

but how i can protect my dll from end users.

Sergey Alexandrovich Kryukov 12-Mar-13 11:11am

I already answered, didn't I? This is what it is.

As a side note: I would advise to care about the users, not protect yourself from them. What tells you that someone will steal your code?
What tells you that using your library (library, not DLL, "DLL" is nothing but a file name) will harm your business? Start from there.

By the way, do you understand that there is no essential difference between EXE and DLL? Even if you merge all code in one EXE (which is quite possible to do after the regular build), your EXE can be referenced by user's application in exact same way as a regular library. There are assemblies and modules, that's all that matters, not "EXE" or "DLL", which are just parts of customary file names...

—SA