Setting up some kind of security for my .net autocad api application

[Proctor]

hello: I wasn't sure if this was the best forum to pose this question, so I apologize if it's not.

 

I have an application i created using .net api for autocad. The application is dependent on a variety of files such as acad.lin, template files, drawing files, startup .dll, application .dll, access db.

 

The registry settings are configured so that when the program loads, after you give a command to start the application, it looks at the application .dll version is newer on the server. if yes, it places the newest version onto the clients machine. All other files are on the server ....

 

most my users are set up this way; however, i have a few clients that needed to be set up as a standalone...meaning, after they open cad and enter the command to start the app, it doesn't go to the server....all the files are on their local machine.

 

A user could easily copy all the files and then used on another person's machine and I'd like to prevent this from happening.

 

I was thinking that i could implement a login..and that would make the app more secure; however, i'm wondering if there's a way to prevent them from just copying the files to their computer?

 

Any thoughs are truly appreciated.

Thanks,

Proctor

[10west]

I know there are third party packagers to help police licensing etc. Maybe this has to go in with an install that has other setting(s) which are set in registry or file system, while the original app on the standalone client is being installed. Then when executable or fucntions are called, they look for dependancies that are "hidden" in the system, just by their mere existance, the "dependancy" could just be an obscure registry setting that could only be there, because it is placed on install, if not there, harmless exit, or message notification. Then unauthorized users wont just copy a couple files, and be raedy to go on another machine, there will also be one or two other reqmnts, even a single "key". I know it's a bit of a hack, but it's to try to avoid a third party cost, or a third party technique that's already cracked. You may search that topic, it sure is not my specialty, and it's gotten more popular in demand.

 

Maybe it keys to a particular machine, and exits on non matched systems.