Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people, just like you, are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
Solved

Reference in the manifest does not match the identity of the downloaded assembly Interop.Microsoft.Office.Interop.Outlook.dll

Posted on 2008-10-28
4
10,056 Views
Last Modified: 2013-11-10
Greetings:

I have a project that is distributed/published to the company via a file share.  The certificate for the Visual Studio project recently expired and was replaced/updated in order to publish successfully.  However, after the publish succeeded, the application would not install on any machines due to the following exception:

Reference in the manifest does not match the identity of the downloaded assembly Interop.Microsoft.Office.Interop.Outlook.dll

I'm new to this particular project and all of its details.  Thus, at this point I don't know what to make of this error.  Also, during the actual 'Publish' the message in the picture below was given.  I assume this is not an issue seeing how the new certificate was not created with the same name as the old.

Any ideas on how I can straighten this out?

Thanks!
WARNINGS
	There were no warnings during this operation.
 
OPERATION PROGRESS STATUS
	* [10/28/2008 10:52:34 AM] : Activation of C:\Documents and Settings\...\Start Menu\Programs\...\CompanyApplication.appref-ms has started.
	* [10/28/2008 10:52:34 AM] : Performing necessary update check as specified by the deployment.
	* [10/28/2008 10:52:34 AM] : Consuming new update.
	* [10/28/2008 10:52:37 AM] : Installation of the application has started.
	* [10/28/2008 10:52:37 AM] : Processing of application manifest has successfully completed.
	* [10/28/2008 10:52:37 AM] : Request of trust and detection of platform is complete.
 
ERROR DETAILS
	Following errors were detected during this operation.
	* [10/28/2008 10:52:37 AM] System.Deployment.Application.InvalidDeploymentException (RefDefValidation)
		- Reference in the manifest does not match the identity of the downloaded assembly Interop.Microsoft.Office.Interop.Outlook.dll.
		- Source: System.Deployment
		- Stack trace:
			at System.Deployment.Application.DownloadManager.ProcessDownloadedFile(Object sender, DownloadEventArgs e)
			at System.Deployment.Application.FileDownloader.DownloadModifiedEventHandler.Invoke(Object sender, DownloadEventArgs e)
			at System.Deployment.Application.SystemNetDownloader.DownloadSingleFile(DownloadQueueItem next)
			at System.Deployment.Application.SystemNetDownloader.DownloadAllFiles()
			at System.Deployment.Application.FileDownloader.Download(SubscriptionState subState)
			at System.Deployment.Application.DownloadManager.DownloadDependencies(SubscriptionState subState, AssemblyManifest deployManifest, AssemblyManifest appManifest, Uri sourceUriBase, String targetDirectory, String group, IDownloadNotification notification, DownloadOptions options)
			at System.Deployment.Application.ApplicationActivator.DownloadApplication(SubscriptionState subState, ActivationDescription actDesc, Int64 transactionId, TempDirectory& downloadTemp)
			at System.Deployment.Application.ApplicationActivator.InstallApplication(SubscriptionState& subState, ActivationDescription actDesc)
			at System.Deployment.Application.ApplicationActivator.ConsumeUpdatedDeployment(SubscriptionState& subState, ActivationDescription actDesc)
			at System.Deployment.Application.ApplicationActivator.PerformDeploymentUpdate(SubscriptionState& subState)
			at System.Deployment.Application.ApplicationActivator.ProcessOrFollowShortcut(String shortcutFile, TempFile& deployFile)
			at System.Deployment.Application.ApplicationActivator.PerformDeploymentActivation(Uri activationUri, Boolean isShortcut)
			at System.Deployment.Application.ApplicationActivator.ActivateDeploymentWorker(Object state)

Open in new window

certificate-warning.JPG
0
Comment
Question by:John500
  • 3
4 Comments
 
LVL 13

Accepted Solution

by:
TechTiger007 earned 500 total points
ID: 22822613
Seems like you have not signed all the components with same certificate.
0
 

Author Comment

by:John500
ID: 22822841
Thanks for your input.

Regarding the 'Interop.Microsoft.Office.Interop.Outlook.dll' which appears as the sole error in the error message:

"Reference in the manifest does not match the identity of the downloaded assembly Interop.Microsoft.Office.Interop.Outlook.dll."

... how would a certificate apply here?  I can easily identify this dll among the project references (see picture below) but how would a certificate come into play with this?

As far as the message which is given during the Publish, I read this as saying - the three key files already existing on the server (most importantly - publish.htm) don't have the same key:

CompanyApplication.application
publish.htm
setup.exe
references.JPG
0
 

Author Comment

by:John500
ID: 22822983
Notice also the exception type:

System.Deployment.Application.InvalidDeploymentException (RefDefValidation)

I read that:

A deployment manifest is an XML file that describes a ClickOnce deployment, including the identification of the current ClickOnce application version to deploy.

InvalidDeploymentException indicates the existence of a corrupt deployment or application manifest in a ClickOnce application. The error might occur because the manifests are poorly formed, have unrecognized elements for their schemas, or have mismatched digital signatures.

You are more likely to have corruption if you manually edit the deployment or application manifest files with a text editor. You can usually correct this problem by regenerating your ClickOnce deployment, which will create new deployment and application manifests. For more detailed debugging steps, see the following links.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------

I figure my situation is due to 'mismatched digital signatures.'   How would I regenerate the ClickOnce deployment, isn't that the *Publish* process?  How do I know I have a 'ClickOnce' deployment?

Thanks
0
 

Author Comment

by:John500
ID: 22824660
Problem ended up being related to the manifest.  After all related projects were updated with the correct certificate there was no longer any conflict in the manifest.
0

Featured Post

Connect further...control easier

With the ATEN CE624, you can now enjoy a high-quality visual experience powered by HDBaseT technology and the convenience of a single Cat6 cable to transmit uncompressed video with zero latency and multi-streaming for dual-view applications where remote access is required.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

In this article I will provide some simple productivity hacks that will help you use Google to specifically show results from any web site (Experts-Exchange.com in my example), with minimal effort in Chrome and Firefox. I've seen a common theme a…
This article describes how to use the Send to Mail Recipient command. The instructions apply generally to Office 2007 and later versions, but Microsoft® Word 2013 was used for the specific steps and figures.  What is Send to Mail Recipient? Send…
The viewer will learn how to create two correlated normally distributed random variables in Excel, use a normal distribution to simulate the return on different levels of investment in each of the two funds over a period of ten years, and, create a …
The viewer will learn how to use and create keystrokes in Netbeans IDE 8.0 for Windows.

860 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question