expire the use of application after that date

Yes Jaish you are correct.. I just mentioned the logic to restrict the application when date is expired.. I didn't mean that what ever I mentioned he have to follow that.. I just given example thats it.. Dates he should decide how it should work.

 

May be expiry date can be hard coded or he can take it from DB...DateTime.now ---> I mentioned for only logic.. He can take server date also... 

 

I just given example of what logic he is looking. 

Frankly speaking if someone changed their machine calendar to an old date than current date before running application, then you still able to crack this approach :) . So ideally your logic should be on top of both static values i.e. Date it activated and the expiry date at the time of activation...

 

That's why most enterprises have their own servers&services to keep licensing information so that license check won't happen locally inside user machine, but inside product servers.

Store One Date in Database

then Fetch that date 
and write 
DateTime dtExpiryDate=Get Date from Database 

in place of
DateTime dtExpiryDate = DateTime.Now.AddDays(-1);

and Other things

@Kanimozhi M Below line

 

DateTime dtExpiryDate = DateTime.Now.AddDays(-1);

 

Normally thick client applications won't run full day, but close it end of day and open again next day. So each day if application open, dtExpiryDate will reset each time. So ideally expirydate should only set during very 1st run and need to store that value somewhere. then take that stored expiry value during each further run.

Hi ,

 

please try this below code.