LOL



Glad the tool worked for you too!

worst case scenario:

telling someone that it wasnt my fault

best case scenario:

laying on the beach, enjoying the cocktails -and the girls who get them to me

[quote]... and it now has a certificate expiring on the 13.01.2059

Have you started worrying about what you are going to do after that?

Cool! This is a must have when using ClickOnce. Your smart to figure this out early instead of suddenly getting a ton of support calls because the app won't install anymore!

Hi Greg,

i have now tried this at home. I installed VC++ Express and downloaded the Renewcert Project from the URL you linked. i then changed the code to add 50 years instead of 5 and compiled it.

It really works Made a little test c# solution and it now has a certificate expiring on the 13.01.2059

Many thanks for that information !!

Yes, you only see the untrusted message on first install. After that, when the user starts the app, a "launching application" dialog will appear that indicates that ClickOnce is verifying the app. The app will then either startup or if a new build is available and required, it will automatically start downloading, install itself and the app will start. I can't remember what happens with an optional upgrade...just don't do optional installations (maybe once in two years).

Hi Greg,

thanks. i will try that tool tommorow.

Can u confirm that the "Untrusted Source" Message only appears on the first install, and not anymore on updates ? Because we plan to distribute the ClickOnce-Setup.exe file through novell NAP, so that a user clicks that and it will allways be up-to-date.

If it were showing the message for the updates aswell, instead we would need to distribute 2 shortcuts (one for update, and one for regular program use).

Philip,



What I did for ClickOnce is to just generate the certificate using Visual Studio, then I used the tool from this site to extend the time of the certificate:



http://www.may.be/renewcert/



I made it last like 10 years...probably by then we'll be using something else anyway. I did this about a year ago, so I don't remember exactly how it works, but I got it to work eventually. If you are already installing your app via ClickOnce in production, be sure to update the current certificate, or everybody has to uninstall/reinstall.



Good luck!



Greg

Hi Trend, thanks for the reply.

However, we dont have a spc from a certificate company. basicly i want to make my own certificate. i dont care about the warning message during install. but i want it to last very long, or better never expire during the applications lifetime.

Yeah, this can be a frustrating process.  It is never straight forward.  The ultimate goal is to get the certificate in a pfx format then you can use the code signing tool to sign any EXE or install.  This is the approach that we take.  Generally you are starting with a .SPC file that you received from the certificate company as well as the PVK.  To produce a PFX, you can use this pvkimprt tool: