1

I have a winforms app deploying with ClickOnce.

But when i try to publish, this generates the error like application validation did not succeed, please contact application vendor.

Below given is the error in detail.

Application manifest has either a different computed hash than the one specified or no hash specified at all. File, Netspective Fluent XA.exe.manifest, has a different computed hash than specified in manifest.

I tried googling and several options stated, none of them helped, could anyone point out what will be exact issue.

I created a key and signed the manifest. But it still shows error.

Please guide me through!!!!

Thanks

csLijo
  • 481
  • 2
  • 8
  • 26
  • possible duplicate of [ClickOnce Deployment Error: different computed hash than specified in manifest](http://stackoverflow.com/questions/6231063/clickonce-deployment-error-different-computed-hash-than-specified-in-manifest) – Stefan Over Apr 28 '14 at 11:11
  • @Herdo : i have tried this already. I created a project from scratch and tried the same, but failed. Also, tried to regenerate manifest. could you please explain the steps to do? I am running .Net 4.0. will that be an issue? – csLijo Apr 28 '14 at 11:25

1 Answers1

2

Let me guess what's wrong:

Be sure that "Publishing Folder Location" or "Installation Folder" is the same as user see it. ClickOnce application can be launched only from one of these 2 locations. The problem you described can happen if you manually copied the files to different folder / server.

jing
  • 1,919
  • 2
  • 20
  • 39
  • 1
    I publish to a local folder, and later using git, pushes to the installing location, a webserver location. this is already worked before. Now recently this is raising issue. – csLijo Apr 28 '14 at 11:28
  • OK. So I assume your "Installation Folder" is different, it points to target location and it is correctly set. Check please these 2 things: 1. Did you update "*.application" file in the target server, too? 2. Ensure that git synchronized really all files correctly (compare your local directory with server content) – jing Apr 28 '14 at 12:13
  • help please, have same problem... where issue ? – Arti Sep 01 '16 at 06:25
  • 1. Open .application file in deployment folder and verify that deploymentProvider represents real path accessible to end users. If not, you must change installation path in your application settings. 2. Publish again and replace server .application with fresh version. – jing Sep 02 '16 at 12:31