Class Library Protection

[gnome5482]

Hello,

I'm wanting to protect my library files (dll's) from being imported/referenced in a workspace outside of the project I am currently working on. Put simply, I don't want anyone else to be able to reference and use my dll's in their own projects. Is this even possible? If so, what do I need to do? Thanks for your time.

I'm using Visual C# 2005 Express Edition

[vanc]

Hello,

I'm wanting to protect my library files (dll's) from being imported/referenced in a workspace outside of the project I am currently working on. Put simply, I don't want anyone else to be able to reference and use my dll's in their own projects. Is this even possible? If so, what do I need to do? Thanks for your time.

I'm using Visual C# 2005 Express Edition

I've reckoned that you should use some protection keys that can encrypt your library and any code you want. If you don't want to pay for that kind of protection then you can use the unique key of you application as condition in order to run anything in your library. In this way I think you have to rebuild your library every time you upgrade your application to another version. Anyway, it will help you to run your library only with one version of your application only. Cheers.

[jjvainav]

Also, any classes/functions that are declared internal can't be accessed outside of that assembly.