Creating unsigned ClickOnce deployments with MageUI

7
votes

With .Net 3.5 SP1 it is no longer required to sign ClickOnce manifest files. We've incorporated MageUI into our deployment process and would like to deploy some unsigned applications. Mage will let me create an unsigned application manifest. However, it will not let me point the deployment manifest to the unsigned application manifest. It says, "The application manifest is not signed".

Is this a bug? I'm running version 3.5.30729.1; is there a newer version that fixes this? Any ideas for workarounds?

4
deploymentclickonce
Did you ever come up with a good work-around? - Roman Starkov
No. I was just toying with the idea of removing the signature from our deployments, but quite pursuing it after this roadblock. If you ever find a good solution, please post it. - codeConcussion

4 Answers

2
votes

I have the same issue.

Workaround is to add the XML Fragment by hand into the Application Manifest XML

2
votes

Just a word of warning -- are you deploying this internally-only? Removing the signing is allowed, but not advised. It removes all hashing of the files, and makes your application vulnerable to having the files replaced by malware.

0
votes

What XML Fragment needs to go into the Application Manifest XML to create unsigned deployment manifests?

-2
votes

Try .Net Frame work 4.0