How do you setup licencing
-
We've written a program that was only intended for single users. Now we're in a situation where people want to install it in a network. We can sell it in 10 or 20 or 100 licence packages, thats no problem. BUT... How do we stop them buying a 10 licence and using it on 11 etc...You get the idea. I've never done this before (the business end) and any advice or comment would be greatly appreciated. Thanks in advance, Langdon wlangdon@bigpond.net.au LCW
-
We've written a program that was only intended for single users. Now we're in a situation where people want to install it in a network. We can sell it in 10 or 20 or 100 licence packages, thats no problem. BUT... How do we stop them buying a 10 licence and using it on 11 etc...You get the idea. I've never done this before (the business end) and any advice or comment would be greatly appreciated. Thanks in advance, Langdon wlangdon@bigpond.net.au LCW
You could do something like this: Every time the program starts, you increase a number in a file, in the programfile dir, and every time the program ends, you decrese the number. If the number is higher than the number in their licence, you could display an errormessage, and close the program... Anyway, just an idea, there might be better ways to do it - Anders Money talks, but all mine ever says is "Goodbye!"
-
We've written a program that was only intended for single users. Now we're in a situation where people want to install it in a network. We can sell it in 10 or 20 or 100 licence packages, thats no problem. BUT... How do we stop them buying a 10 licence and using it on 11 etc...You get the idea. I've never done this before (the business end) and any advice or comment would be greatly appreciated. Thanks in advance, Langdon wlangdon@bigpond.net.au LCW
I recommend network hardware key with fixed number of maximum application instances. You can implement service on server which will inform application instance if it can be launched or not. During startup, application can contact service and get permission to start. Such process must be repeated, cause think about the situation when fe: application crashes. The number of currently running application instances must be decreased. I strongly do not recommend putting it to the file, as one good program is enough to track all disk or registry activity. See for instance: http://www.sysinternals.com/ to download such programs. Use hardware key/encypt (or better: both together) - these are the safest ways. You can hard code the number of maximum application instances into the service, but I do not recommend this too, cause it does not provide strong protection.