|
|
|
date: Tue, 8 Jul 2008 15:09:09 -0500,
group: microsoft.public.dotnet.framework.windowsforms
back
RE: Click Once FORCES signing
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.
"Seth Williams" wrote:
> 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?
>
>
>
date: Wed, 9 Jul 2008 10:56:01 -0700
author: Collin
Re: Click Once FORCES signing
No, there's not. Signing the manifest is required. I believe there is a way
to avoid this behavior if you use VS2008 SP-1 though.
RobinS.
GoldMail.com
"Seth Williams" wrote in message
news:eHiVFaT4IHA.1204@TK2MSFTNGP04.phx.gbl...
> 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?
>
>
date: Tue, 26 Aug 2008 22:51:19 -0700
author: RobinS
|
|
