ASP.Net applications protection through a license scheme

Question

0.00/5 (No votes)

See more:

Would any body guide me or give me useful references on how to protect asp.net applications using a licensing scheme which allows a trial version for, let say, 60 days, producing license key after product's license is purchased, and controlling yearly license once product key is purchased?
Thanking you in advance

Posted 5-Nov-12 8:55am

Joseph Cheriaux MPORANYI

Add a Solution

3 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Sergey Alexandrovich Kryukov · Answer 1 · 2012-11-05T09:29:00

Don't you think this is way too easy, compared to desktop programming? There is no special technology for that except already existing authentication and user profiles. If you are using ASP.NET, you have server side, so you user cannot do anything without your site. And your business has full control over it. You create user profiles, and, for each profile, track service time, payment, all what involved. And, after the end of trial period, limit the access to resources if the user does not upgrade the account to the payment-based one, renew subscription based on history and payment status, etc.

So, you don't need any special manual on trial period and licensing. You only need to know authentication.

—SA

Sandeep Mewara · Answer 2 · 2012-11-05T09:30:00

Tracking trial-paid version for a website is much simpler than desktop application. All you need is to keep a record of every username from when they are using the product in your database. On username login, check the start date they started using and then calculate days since then using today's date. Use your if-else strategy based the package. If they were on trial version and it was for 15 days, in case it is less than 15 days - flash it somewhere 'x days left'. If more than 15, then say 'trial version expired, if you want to use more purchase'.

Once bought, your app should pick the flag as 'valid/purchased' username and you should allow for full feature.

Joseph Cheriaux MPORANYI · Answer 3 · 2012-11-05T18:40:00

Solution 3

Thanks for replying.
In case user changes system date, or uninstall and re-install the app, it might be a challenge!
How to overcome such scenarios?

Posted 5-Nov-12 18:40pm

Joseph Cheriaux MPORANYI

ASP.Net applications protection through a license scheme

3 solutions

Solution 1

Solution 2

Solution 3

Add your solution here

Preview 0