yep, it was the first thought i had too. but my question was not it. it's about the way you use DLL files in ASP. basically i'm concerned about this:

i'm developing an app for a customer. it's not meant to be online (but capable). the customer has Win2k. so i'm simply installing the IIS and the app a browser-based, blah blah blah... i think you got the point.

the customer has a physical access to the server (it's in his office). so i want to write such an app which, even if he does copy and paste into another machine, would not work.

any ideas?