Can't Publish-SignToolError

[Paul Engel]

I have an app that published fine to our network. We just moved to a new
server and I am trying to publish my app to the new server. It fails and I
get the following messages:

Error 1 Cannot publish because a project failed to build. 1 1
TextFileConverter

Error 2 SignTool reported an error 'Failed to sign
bin\Release\TextFileConverter.publish\\setup.exe. SignTool Error:
ISignedCode::Sign returned error: 0x80880253

The signer's certificate is not valid for signing.

SignTool Error: An error occurred while attempting to sign:
bin\Release\TextFileConverter.publish\\setup.exe

'. TextFileConverter
Does anyone have any ideas? I noticed the double hack before setup.exe...but
can't figure out if that's a problem and where to change that.

[RobinS]

Are you using ClickOnce deployment (the publish tab) or a set&deployment
package?

RobinS.
---------------------------
"Paul Engel" <pa********@vebridge.comwrote in message
news:uD**************@TK2MSFTNGP03.phx.gbl...

>I have an app that published fine to our network. We just moved to a new
server and I am trying to publish my app to the new server. It fails and I
get the following messages:

Error 1 Cannot publish because a project failed to build. 1 1
TextFileConverter

Error 2 SignTool reported an error 'Failed to sign
bin\Release\TextFileConverter.publish\\setup.exe. SignTool Error:
ISignedCode::Sign returned error: 0x80880253

The signer's certificate is not valid for signing.

SignTool Error: An error occurred while attempting to sign:
bin\Release\TextFileConverter.publish\\setup.exe

'. TextFileConverter
Does anyone have any ideas? I noticed the double hack before
setup.exe...but can't figure out if that's a problem and where to change
that.

[Paul Engel]

Click Once.

"RobinS" <ro****@imnottelling.comwrote in message
news:S6******************************@comcast.com. ..

Are you using ClickOnce deployment (the publish tab) or a set&deployment
package?

RobinS.
---------------------------
"Paul Engel" <pa********@vebridge.comwrote in message
news:uD**************@TK2MSFTNGP03.phx.gbl...

>>I have an app that published fine to our network. We just moved to a new
server and I am trying to publish my app to the new server. It fails and I
get the following messages:

Error 1 Cannot publish because a project failed to build. 1 1
TextFileConverter

Error 2 SignTool reported an error 'Failed to sign
bin\Release\TextFileConverter.publish\\setup.ex e. SignTool Error:
ISignedCode::Sign returned error: 0x80880253

The signer's certificate is not valid for signing.

SignTool Error: An error occurred while attempting to sign:
bin\Release\TextFileConverter.publish\\setup.ex e

'. TextFileConverter
Does anyone have any ideas? I noticed the double hack before
setup.exe...but can't figure out if that's a problem and where to change
that.

[Paul Engel]

Your question gave me what I needed. i searched Google for OneClick and
Signed and found the answer. In the end, I went into the Signed property tab
of my properties for the projecdt, clicked on create test signature, used
the same password I used last year and it created a new signed certificate
that expires in a year. I was thereafter able to publish my app. Thanks!

I'll remember that next year!
"RobinS" <ro****@imnottelling.comwrote in message
news:S6******************************@comcast.com. ..

Are you using ClickOnce deployment (the publish tab) or a set&deployment
package?

RobinS.
---------------------------
"Paul Engel" <pa********@vebridge.comwrote in message
news:uD**************@TK2MSFTNGP03.phx.gbl...

>>I have an app that published fine to our network. We just moved to a new
server and I am trying to publish my app to the new server. It fails and I
get the following messages:

Error 1 Cannot publish because a project failed to build. 1 1
TextFileConverter

Error 2 SignTool reported an error 'Failed to sign
bin\Release\TextFileConverter.publish\\setup.ex e. SignTool Error:
ISignedCode::Sign returned error: 0x80880253

The signer's certificate is not valid for signing.

SignTool Error: An error occurred while attempting to sign:
bin\Release\TextFileConverter.publish\\setup.ex e

'. TextFileConverter
Does anyone have any ideas? I noticed the double hack before
setup.exe...but can't figure out if that's a problem and where to change
that.

[RobinS]

Great. Note that if you are using VS2005, and you publish with a new
certificate, your users will have to deinstall and reinstall the
application.

They fixed this problem in VS2008, so if you're using that, you won't have
any problem at all.

RobinS.
GoldMail.com
--------------------------
"Paul Engel" <pa********@vebridge.comwrote in message
news:u2**************@TK2MSFTNGP02.phx.gbl...

Your question gave me what I needed. i searched Google for OneClick and
Signed and found the answer. In the end, I went into the Signed property
tab of my properties for the projecdt, clicked on create test signature,
used the same password I used last year and it created a new signed
certificate that expires in a year. I was thereafter able to publish my
app. Thanks!

I'll remember that next year!
"RobinS" <ro****@imnottelling.comwrote in message
news:S6******************************@comcast.com. ..

>Are you using ClickOnce deployment (the publish tab) or a set&deployment
package?

RobinS.
---------------------------
"Paul Engel" <pa********@vebridge.comwrote in message
news:uD**************@TK2MSFTNGP03.phx.gbl...

>>>I have an app that published fine to our network. We just moved to a new
server and I am trying to publish my app to the new server. It fails and
I get the following messages:

Error 1 Cannot publish because a project failed to build. 1 1
TextFileConverter

Error 2 SignTool reported an error 'Failed to sign
bin\Release\TextFileConverter.publish\\setup.exe . SignTool Error:
ISignedCode::Sign returned error: 0x80880253

The signer's certificate is not valid for signing.

SignTool Error: An error occurred while attempting to sign:
bin\Release\TextFileConverter.publish\\setup.e xe

'. TextFileConverter
Does anyone have any ideas? I noticed the double hack before
setup.exe...but can't figure out if that's a problem and where to change
that.