Hi Kenneth,
I agree that using My.Setting is a good way to save the software
installation time since there is the .Net Framework build-in support.
Another way may be storing it in the registry, but this may require more
..Net registry writting permission than My.Setting.
The problem I wanted to point out is the security of this solution. Once
the end user knows about where your software My.Setting configure file is
stored, it is easy for him to modify your saved date in that file and
cheats your software from thinking it did not expire.
So, I would recommend you to use .Net crypto classes to encrypt the date
before saving. This will provide a basic protection for your solution.
Please refer to "System.Security.Cryptography" section in the article below
for basic information regarding .Net Cryptography:
http://msdn.microsoft.com/msdnmag/issues/06/00/SecurityBriefs/#S6
Hope this helps.
Best regards,
Jeffrey Tan
Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.