I am having difficulties signing the manifests in ClickOnce. I've already taken care of the single named assembly problem but for some reason Visual Studio Beta 2 intermittently signs the manifest when I try to publish. I have obtained an Ascertia "code signing" certificate and a dialog window pops up three times. Are there any more quirks I am missing in ClickOnce Beta 2 I need help bad.

ClickOnce Beta 2
Jemima
See supplying the Publisher name is not only way that the application
recognizes you. For this you have top go to the proper channel for the
Application to accept your supplied Publisher name and recognize you
the Valied Publisher you have to do the follwing :-
For that: - Open the Project Properties {NOT THE FORM OR CONTROL
PROPERTIES}
Go to the Signing tab ::: Sign you manifests with Secure Cetificates,
then Create a new SNK called Strong KEY to sign in your Assembly. One
more thing after signing your app.manifest you have to installed the
valid certificate at you Server from where you want to deply the
Application.
Do not Select Delay signIn Checkbox...
--------------------------------------------------------------------------------------
All the above i.e first the valid Certificate creation and SNK
Generation are ery easily performed by Wizards with simple Click Next -> click
Next.