ClickOnce: <File>, has a different computed hash than specified in manifest

Add-in Express™ Support Service
That's what is more important than anything else

ClickOnce: <File>, has a different computed hash than specified in manifest
Microsoft is bad and they should feel bad 
Inspirometer Developer




Posts: 34
Joined: 2017-10-13
Before moving over to ADX we frequently encountered a bug where Visual Studio would not properly publish the add-in. Attempting to install it would give you the error in the title. As you can imagine this is a huge hassle to deal with - having to test every build we publish just in case this error appeared. So far I haven't encountered it in ADX but to be sure we're not going to come across it one day I wanted to post in here and check. Does using ADX remove the possibility of this error appearing?
Posted 17 Oct, 2017 06:36:10 Top
Andrei Smolin


Add-in Express team


Posts: 18793
Joined: 2006-05-11
Hello,

We have only three cases:
- https://www.add-in-express.com/forum/read.php?FID=13&TID=9545
- https://www.add-in-express.com/forum/read.php?FID=5&TID=13824
- https://www.add-in-express.com/forum/read.php?FID=5&TID=14046

I think the issue doesn't relate to VSTO or Add-in Express. I think it is caused by the way you create your installer. Specifically, I think you can get this issue only if you modify the files to be distributed *after* you publish them.


Andrei Smolin
Add-in Express Team Leader
Posted 17 Oct, 2017 07:17:12 Top