how to impose constraint that some feature will be disabled after some time

Question

2.00/5 (1 vote)

See more:

hi friends,

I'm making an application in which i want some feature of that application to get disable after some time lets say 15 days.
i want you to give suggestions and share your experience regarding same, so that i will not be left with any loop hole in that application.

foreg: if I'll use comparison between the day the application is installed with current day then when the count will reach 15 above i can disable
Here i can manipulate system date time moreover i can reinstall that application.
Other way is that I'll store one count variable which will count the days, but here also there is constraint that application should be used everyday(Here i can have one solution that application can be added to start-up But i don't want to do this)

So friends I need some of your experience to be shared here which can leave no stone unturned when it comes to loop hole or it should be soothing enough!!!

Thanks in Advance.

Posted 27-May-12 8:14am

preet88

Add a Solution

Comments

db7uk 27-May-12 15:30pm

This really depends on the application architecture? Is is ASP.NET, WPF?

1 solution

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)

jsdhgkjdsahklg · Answer 1 · 2012-05-27T15:58:00

I suggest that you calculate 15 days from the beginning day, and save the 15th day in the registery, and make your application always on start-up parse that day from the registery, and check for the current day, if it's the same day or not, and weather the day in registery is older than the current one.

Hope this would help!
Thank you!