I’m the author of a tool that could really help in situations like this. ClickOnceMore is a ClickOnce tool designed to assist in automating ClickOnce builds. You can check it out at http://www.clickoncemore.net.

It includes the concept of “macro sets”, for example you could have a DEV and PROD macro set that each indicate a different certificate to use. Then when you run the command line version during your build you just indicate which macro set to use and the manifests will be signed with the correct certificate.

Check it out and let me know what you think. I’m constantly trying to improve the software so any feedback would be greatly appreciated.

Regards,
Greg Jackman
Red Sky Software

You could do something like:

mage -Sign ClientShell.manifest -CertFile companyPFX.pfx -Password pa$$word

see: http://cs.blueberryislandmedia.com/blogs/blueberries/archive/2009/04/24/clickonce-deployment-via-command-line-with-makecert.aspx

———-

I haven’t tried this myself, but the other thing you could try is to use the certificate off the certificate store. To do this,
1) Import the certificate to the certificate store (it will ask for the password here),
2) Only specify the /p:ManifestCertificateThumbprint value and specify /p:ManifestKeyFile=”" as blank.

———-

Hope this helps

I have pfx which requires password. Could you plaese provide me the parameter that i can use to pass password for my pfx file.

Thanks,
Divyesh.

You solution can contain all the .pfx files. The .pfx files aren’t deployed with the ClickOnce app. They are used to sign application and deployment manifests.

So, all you need to make sure is that you’re using different .pfx files for each environment when you’re publishing the ClickOnce app.

To select .pfx files in Visual Studio:
Properties -> Signing -> Check “Sign the ClickOnce manifest” -> Select from File

If you’ve got only one .pfx file you can create as many certificates as you want using “Create Test Certificate”

Hope this helps