Windows Develop Bookmark and Share   
 index > ClickOnce and Setup & Deployment Projects > Unable to create clickonce deployment: Reference in manifest does not match the identity of the downloaded assembly
 

Unable to create clickonce deployment: Reference in manifest does not match the identity of the downloaded assembly

I have an application that I would like to deploy using ClickOnce. I've done this before so have had considerable experience with ClickOnce and Mage. I have an assembly called Launcher.exe and a number of dlls associated with it. I tried to create a ClickOnce application and deployment manifest using the mage UI and command line. Essentially, I'd like Launcher.exe to be the entry point. I finish creating both manifests and I try to launch. When I do, ClickOnce downloads the dlls but fails with the logfile message:
"Reference in manifest does not match the identity of the downloaded assembly Launcher.exe".

Strange, I thought. My assemblies are all signed with one snk.

I tried this a few more times to no avail.

I then thought that since the team recently upgraded to VS2008, maybe there was some issues, so I created a new exe project. This project included all of my dependencies, including Launcher.exe, and just executed Launcher.exe. I thought this would work for sure, but I got the exact same error:
"Reference in manifest does not match the identity of the downloaded assembly Launcher.exe".

What could be wrong with Launcher.exe so that this is occuring?
Szymon Rozga  Wednesday, August 26, 2009 1:39 PM

Hi,

The following is an article about this error.

http://geekswithblogs.net/rakker/archive/2007/12/06/117449.aspx

By the way, I found a similar issue on msdn.

Troubleshooting Specific Errors in ClickOnce Deployments

http://msdn.microsoft.com/en-us/library/ms229001(VS.80).aspx

It suggests that the identity of an assembly consists of its name, version, culture, and public key token. Examine the identity descriptions in your manifests, and correct any differences will be OK. Hope this helps.

Best regards,

Ling Wang


Please remember to click “Mark as Answer�on the post that helps you, and to click “Unmark as Answer�if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
Ling Wang  Wednesday, September 02, 2009 7:48 AM

Hi,

The following is an article about this error.

http://geekswithblogs.net/rakker/archive/2007/12/06/117449.aspx

By the way, I found a similar issue on msdn.

Troubleshooting Specific Errors in ClickOnce Deployments

http://msdn.microsoft.com/en-us/library/ms229001(VS.80).aspx

It suggests that the identity of an assembly consists of its name, version, culture, and public key token. Examine the identity descriptions in your manifests, and correct any differences will be OK. Hope this helps.

Best regards,

Ling Wang


Please remember to click “Mark as Answer�on the post that helps you, and to click “Unmark as Answer�if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
Ling Wang  Wednesday, September 02, 2009 7:48 AM

You can use google to search for other answers

Custom Search

More Threads

• Windows Installer
• Error when Intranet VPN Client tries to install
• Win32 console app call to GetCommTimeouts fails when deployed
• ClickOnce on 64-bit server with existing apps installed...creates problem
• Windows Vista/Seven Logo Testing
• ClickOnce application download error
• Problem installing an app on Vista
• Rolling back un-installation through custom action.
• Could not find file C:\Inetpub... GescomCustomActionInstaller.InstallState
• Setup & Deployment -- rerun custom action