Click Once FORCES signing

[Seth Williams]

We have a couple of apps on our intranet, needing only to be published
within our network, so we don't need signing

On one developer's computer, every time we try to Publish the application,
(even though we UNCHECK the signing checkbox in the Signing tab), it
automatically checks it again, and then, because it's not signed, will throw
an error and not publish.

Any ideas on where there might be a setting so I can stop this behavior?

 

[Collin]

In ClickOnce deployment, there's two types of signing. The first signing is
the ClickOnce manfest which I believe controls the ClickOnce security
settings. i.e. full trust vs. partial trust.

Then there's the signing the assembly which is code signing where you have
to buy the certificate for Verisign.