Preventing access to an assembly

[darwen]

Dear all,

I think this might be the best place to put this - possibly it'll get a reply whereas if I put it in the C++.NET group it wont.

At any rate :

Say I deploy an application to those nice people out there in the outside world. You know, the ones that find bugs in your code and moan about them.

Now, this .NET application uses .NET assemblies which I have written.

I don't want them to be able to use the .NET assemblies because using the object browser it's going to be pretty obvious how to use them.

Can I do this ? I used to think that turning on delayed signing and using a key file might stop this but I think that TheCPUWizard told me that this isn't the case.

In the case of COM dlls I can just remove the type library from the resources (I don't use dual interfaces usually so that type library is a little redundant).

Thanks in advance,

Darwen.

[darwen]

Nobody ? Even 'don't know's' or can't do's would be great.

How about C# Gods aka moderators ?

Darwen.

[Alexei Kubarev]

well... "dont know" would come out from me Darwen
thats for sure