Windows Develop Bookmark and Share   
 index > ClickOnce and Setup & Deployment Projects > Help Signing ClickOnce Manifest And Sharing Certificate
 

Help Signing ClickOnce Manifest And Sharing Certificate

When trying to publish an update of a click once application today, I found that the certificate we have been using since I started this job, had expired since the last publish. It appears that it was created through the signing tab in visual studio by clicking the "Select From Store" button. Here is the information I see for the old key:

Issued ToDOMAIN\user1

Issued By DOMAIN\user1

Intended Purpose <All>

Expiration Date 8/31/2007 2:19:13 PM

If I click the "Select From Store" button, I see the same type of certificate except it is my user name instead of user1's user name. If I publish with my certificate, the application is then considered different so it would require everyone to re-install it. Since the certificate is good for a year, they would then have fo re-install every year. How can I re-new the certificate we have been using and set the expiration date? How do we share the certificate between developers? We're using sourcesafe to manage the code. Our senior developer was just let go so I'm a little lost. Thanks.

xr280xr  Friday, September 14, 2007 6:49 PM

I was able to use RenewCertconsole app (from the link above)to create a new certificate using the same key. I first modified the RenewCert code to make the certificate expire in 99 years instead of 5 so that no one here will have to deal with the problem again.Ithen selected my new certificate fileas the manifest certificate (which added it to my certificate store automatically) and added the file to thevisual studio project. It was available to the other developers through source safe so I didn't have to do anything else for them to use it.Thanks for my help!

xr280xr  Friday, September 14, 2007 10:49 PM

I have found these articles stating that if it is a self issued certificate it can be renewed using this microsoft hack utility:

http://support.microsoft.com/?kbid=925521

Here is a similar forum topic with some good discussion on the problem:

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=442030&SiteID=1

My other question still stands. If I successfully renew our certificate, how do I make it available to the other developers so that any of us can publish?

xr280xr  Friday, September 14, 2007 7:59 PM

I was able to use RenewCertconsole app (from the link above)to create a new certificate using the same key. I first modified the RenewCert code to make the certificate expire in 99 years instead of 5 so that no one here will have to deal with the problem again.Ithen selected my new certificate fileas the manifest certificate (which added it to my certificate store automatically) and added the file to thevisual studio project. It was available to the other developers through source safe so I didn't have to do anything else for them to use it.Thanks for my help!

xr280xr  Friday, September 14, 2007 10:49 PM

You can use google to search for other answers

Custom Search

More Threads

• Clickonce and installation files
• ClickOnce and Setup (can publish but cannot INSTALL)....
• put the msi file in a different folder
• problem with signing application and deployment manifest
• Setup and Deployment Project FAQ
• Update database structure
• Signing an IE Control
• How to register with window to view specific file format?
• Deploying program to web site.
• Read Embedded Resource file in Setup Project