If I enforce a licensing restriction on my application,say the first time the application runs,then should my application check the restrictions (could be a encrypted license file) each time? How do you design this part? What is the best way? Basically I would like someway to save CPU cycles somehow(encryption means decryption blah blah ).I hope you understand my concern.
What are some good examples of “novel user experience” engineering you like/have used for web and Windows apps?
c# design question - standalone GUI application
Software design problem: circular dependency
if you only check on the first load, you are going to need to store the success/failure of the validation somewhere, so that your application knows if it is legit or not.
Create css files compatible with multiple browsers automatically
This then becomes a concern, as you need to validate that your system is the ONLY thing that is actually storing/updating that information source..
Deployment: GWT vs. Silverlight
Which C# data structure to use?
trying to understand ebay's schema
Design advice for a personal project - “Files Renamer”?
Make sure the bit is somewhere outside of the application folder (that way if somebody straight copies your app to another machine, your software will know it's no longer licensed).. If you're trying to do a web app, an encrypted license file somewhere in your site directory seem to be a popular solution.
The file contains the license type and domain name...then your web app verifies the license upon each request (a little bit of overhead, but you can make that code lightning fast)..
I would recommend checking a license key each time the application starts - this shouldn't be too expensive of an operation in terms of CPU/memory.
If you only check on the first time it is run, then it is rather prone to being hacked, and the key could be removed and installed on another computer over and over again..
Usually it's not too expensive to do at least that.. In some circumstances -- and you have to determine if this applies to you -- it can make sense to do licensing checks more often.
For example, some software licenses components of the program separately, checking the license for that component each time it is accessed.
Using commercial applications, like the ones mentioned above, this isn't that expensive so it's quite commonly done..