{var%20f='http://v.t.sina.com.cn/share/share.php?appkey=1515056452',u=z||d.location,p=['&url=',e(u),'&title=',e(t||d.title),'&source=',e(r),'&sourceUrl=',e(l),'&content=',c||'gb2312','&pic=',e(p||'')].join('');function%20a(){if(!window.open([f,p].join(''),'mb',['toolbar=0,status=0,resizable=1,width=440,height=430,left=',(s.width-440)/2,',top=',(s.height-430)/2].join('')))u.href=[f,p].join('');};if(/Firefox/.test(navigator.userAgent))setTimeout(a,0);else%20a();})(screen,document,encodeURIComponent,'','','https://www.manongdao.com/data/attach/logo/logo.png', '推荐 Evening l夕情丶 的问题《ClickOnce error after deploying — has a different》','https://www.manongdao.com/q-766114.html','页面编码gb2312|utf-8默认gb2312'));){kind=link}
Afer deploying my VSTO add-in with ClickOnce, I get the following error message when trying to launch setup.exe:
File, Addin.resources.dll, has a different computed hash than specified in manifest.
Why is this happening? What can I do to fix this?
相关问题
- Can ClickOnce or InstallShield setup SQL Server or
- ClickOnce updates all files. Why?
- Excel Workbook Activate Event Ambiguity for C# VST
- WCF service deployment - tools
- Robocopy to copy files to a remote machine
相关文章
- How to add external file to application files ( cl
- Override env values defined in container spec
- What is a good way to deploy a Perl application?
- Automatically install updates with ClickOnce deplo
- Deploying C++ game in Linux
- Deleting columns from a table with merged cells
- Can't get Jenkins to start using Tomcat
- Swift 4 - Setting a minimum deployment target
I was able to resolve this just by doing a clean build and publish. For some reason the manifest wasn't updated like it was supposed to.
I'm using Visual Studio 2013 SP2, and am having the same issue.
Regularly, I will create a new release of our Excel Addin by Rebuilding the solution in VS, signing it, deploying it, but it is uninstallable.
If I then quit Visual Studio, then run Visual Studio again, Rebuild and Redeploy, then it'll work without any problems. Which is fine... but, of course, it means each time I deploy, I need to check that the damn thing will install okay !
It's worrying that VS continues to build installables which quietly contain this issue.
There are plenty of articles mentioning this bug, errr, issue (some from 8 years ago !!), suggesting I need to "rebuild my manifest file", but why doesn't this happen automatically when a do Rebuild in Visual Studio..?
ClickOnce Deployment Issue
ClickOnce Deployment Error