I created my own, but it says Unknown publisher and gives the warning message. I think this is as expected because I need to get a certificate from Verisign or someone like that. So my question is, if I use my self generated one for say 1 year and then I buy a real one from Verisign, what will the user have to do when I change to a real certificate? Will the user have to uninstall the wpf program with the old cert and then re-install? I'm just wondering if I can go with the one I created for a while until enough people complain, or should I just get it over with verify it.
Also, for windows 8, I get a 'Windows protected your PC' thing pop up when I try to use my own cert. I have to click more info, and run anyway to install it. Seems like I'll have to get a real cert to make that go away.
Also on the renewals, it's only for up to 3 years. If I renew after 3 years, will the customer have to un-install and re-install for updates in WPF. I think in Silverlight OOB, renewals won't work. I'm guessing for WPF it will. I just don't want interuptions. For the cert that I created, I put 99 years, so I don't have to deal with that. Anyone have experience with this?
So the real certificate I would want, would be the one below? Can I use this same one for all my silverlight lob apps too? How many WPF apps could I use this on? Or do I need to get a different cert for every program? Also, some of my click once installs will be internal with the same domain. I install on various customers servers. Then I also want the WPF click once hosted on an external site for other customers.
Code Signing Certificates for Microsoft Authenticode
dan