I'm trying to sign a ClickOnce .NET Application. I have a SSL cert that I use on a website, but I'm thinking that it is not up to the job. When I select the cert in Visual Studio I get an messsage box saying 'The selected certificate is not valid for code signing. Choose another certificate file'. The cert details look like this:
whereas a temporary cert generated in VS looks like this:
It seems to have a lot more going for it in terms of looks and general charisma. Do I need to get a new cert issued? What would I need to specify when ordering it to ensure it is up to the job of signing the ClickOnce code?