Preventing others from using my class library assembly.

Question

0.00/5 (No votes)

See more:

I have created a class library assembly (.dll) file. At the main GUI
application, this assembly is referenced and used.

If I redistribute these files with my application, somebody can also
add the class library assembly to their .NET project. How to prevent others to use my class library assemly files?

Posted 8-Jul-10 20:30pm

bibijojo

Add a Solution

2 solutions

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)

idenizeni · Accepted Answer · 2010-07-09T14:17:00

http://www.codeguru.com/csharp/csharp/cs_misc/security/article.php/c8329[^]

http://www.codeproject.com/KB/security/UB_CAS_NET.aspx#Security Namespace

Or another way would be to add logic (using reflection) to your class to prevent it being called by any assembly that doesn't match the one you want to allow...

http://www.eggheadcafe.com/software/aspnet/34287552/prevent-dll-usage.aspx[^]

Christian Graus · Accepted Answer · 2010-07-08T20:35:00

Solution 1

Write it in C++ so that they can't break your protection with reflector, then add a security layer so that they need to know a password or you identify the calling assembly or something.

Posted 8-Jul-10 20:35pm

Christian Graus