I have a problem deploying my ClickOnce application.  I have built my Clickonce application with visual studio 2005 Beta 2 and signed the Manifests with a Verisign Code signing certificate.  I publish it to my IIS server and then run it from my development pc and it installs and runs ok.  I then go to another pc and try to install it (over ClickOnce) and I get the error "the deployment identity at the deployment provider is not the same as the original identity".  Can anyone tell me what is happening ? 

I was hoping that if I used a Verisign certificate (Verisign being a well known publisher) that I would be able to install my ClickOnce application without having to first install a certificate on the workstation, it this correct ?

I have contacted Verisign support (if you can call it that) and have got no place with this.  Every email response comes from a new person and it is like starting over (after 2 weeks).  

thank you

jeff

The issue that you are seeign is NOT because the verisign certificate is not being recognized on the other machine - it is earlier in the manifest processing.

I am assuming you are familiar with the deploymentProvider concept of Clickonce. (Have explained ti breifly at the end of the mail).
The exception you are seeing is caused by the fact that the <assemblyIdentity> of the .application you are clicking on is different than the <assemblyIdentity> in the  deploymentProvider. Could you confirm this? These two have to be same modulo version, which could be different.

Saurabh

DeploymetnProvide logic in brief -
When a user clicks on an .application with the <deploymentProvider> specified  ClickOnce follows the deploymentProvider by default and installs the application from that URI.  <deploymentProvider> is required for all Shell Visible ClickOnce applications - VS must have put it for you - you can check out what it is by opening the .application in notepad ...

There seem to be two seperate issues here. We still need to figure our why you are the seeing the deployment identity mismatch error.

As far as signign is concerned - yes you should be able to run an application as long as the manifest is signed by verisign (You will be prompted ofcourse). Adding to trusted root allows you to install the application without a prompt.