1

The question/request

Can you give an example/reference on how to create a new WPF app, sign the clickonce manifest and assembly, deploy it, and install WITHOUT getting the following errors?

+ Application manifest has either a different computed hash than the one specified or no hash specified at all.

+ File, WPFSigning.exe.manifest, has a different computed hash than specified in manifest.

Details

I have just created a brand new WPF test app. But when I "Sign the ClickOnce manifest" and "Sign the assembly" and "Publish Now", I get in trouble.

The build files goes into my MVC 5 app, and I publish that to azure. When I click install, the setup.exe downloads, and when I run it, I get the message Application validation did not succed. If I check the details log, I get this error message:

Application manifest has either a different computed hash than the one specified or no hash specified at all.

I have no idea where things go wrong from here. But let me explain what I have tried so far to fix the error.

What I have tried so far

Here is a screen shot of my project setup.

enter image description here

You can try to download my test app and install it here (note this link will expire soon, as I only has it as a temp test app).

Feel free to clone/look at my code here (also a temp link).

I'm on windows 10, Visual Studio 2015 Community.

Specific things I have tried

None of these changed the error message.

Specific things I consider trying

  • Manually signing my manifest with Mage.exe

Update

Here is a side by side comparison of the auto generated app.application and app.application.manifest files. Some of their values are identical, while some, for example the Hash is different. Red arrows are where the values are different, green where they match.

Is that good?

Click here for enlarged picture

enter image description here

Community
  • 1
  • 1
MartinJH
  • 2,590
  • 5
  • 36
  • 49

0 Answers0