469,645 Members | 1,742 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 469,645 developers. It's quick & easy.

Clickonce, Date Installed

I would like a Beta copy of my software to expire after seven days from
install. I use Clickonce for installing my applications.

How can I determine the install date of a Clickonce application.
--
Kenneth Lemieux
Project Engineer
Whelen Engineering Co., Inc.
Oct 15 '07 #1
4 1237
Ken Lemieux wrote:
I would like a Beta copy of my software to expire after seven days from
install. I use Clickonce for installing my applications.

How can I determine the install date of a Clickonce application.
You can try something simple, and on the first run write the date into
the my.settings value.

then just check the date to see when 7 days has elapsed.

An uninstall and re-install will clear this 7 days setting however.
Oct 15 '07 #2
Thanks Miro,

Your implementation is simple and straight forward. If I don't get any
responces much different from yours, then I will credit you for the responce.
--
Kenneth Lemieux
Project Engineer
Whelen Engineering Co., Inc.
"Miro" wrote:
Ken Lemieux wrote:
I would like a Beta copy of my software to expire after seven days from
install. I use Clickonce for installing my applications.

How can I determine the install date of a Clickonce application.

You can try something simple, and on the first run write the date into
the my.settings value.

then just check the date to see when 7 days has elapsed.

An uninstall and re-install will clear this 7 days setting however.
Oct 15 '07 #3
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/is...rityBriefs/#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/subscripti...ult.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/subscripti...t/default.aspx.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

Oct 16 '07 #4
Hi Kenneth,

Have you reviewed the replies to you? Do they make sense to you? If you
still have any concern or need any help, please feel free to tell me,
thanks.

Best regards,
Jeffrey Tan
Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...ult.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/subscripti...t/default.aspx.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

Oct 18 '07 #5

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

2 posts views Thread by Olaf Baeyens | last post: by
1 post views Thread by moondaddy | last post: by
reply views Thread by T | last post: by
3 posts views Thread by dgk | last post: by
8 posts views Thread by Tina | last post: by
2 posts views Thread by Alex Bögli | last post: by
5 posts views Thread by =?Utf-8?B?R29yZG9uUw==?= | last post: by
3 posts views Thread by =?Utf-8?B?Um9nZXIgVHJhbmNoZXo=?= | last post: by
reply views Thread by gheharukoh7 | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.