ClickOnce: manifest reference error

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

ClickOnce: manifest reference error
Reference in the manifest does not match the identity of the downloaded assembly adxlauncher.exe 
Posts 1 - 10 of 13
First | Prev. | 1 2 | Next | Last 
Fred Balkenende




Posts: 29
 Joined: 2007-07-05
Hi

I have changed to a new Pc (win10 - VS2015) and installed the newest version of Add-in Express (8.0.4330). When publishing my addin, I get no errors, but when trying to install i get the error:

"Reference in the manifest does not match the identity of the downloaded assembly adxlauncher.exe"


I publish using the project using the Publish wizard, and I have tried to remove all files in Publish directory and publish the project Again. It does not help. The target platform of the project is .NET 4.0.

What could be the problem?

Thanks,
Fred Balkenende
OfficeReports
Posted 25 Nov, 2015 12:37:39 Top
Sergey Grischenko


Add-in Express team


Posts: 7233
 Joined: 2004-07-05
Hi Fred,

I can't reproduce the issue. Did you create a new add-in project?
Posted 26 Nov, 2015 10:27:06 Top
Fred Balkenende




Posts: 29
 Joined: 2007-07-05
Hi Sergey

No, it is an old add-in. I copied my complete solution from my old PC (Add-in Express 7.x, Win7 and VS2010), to my new PC, with newer version of all software.

Maybe you can send me your test solution, so I can try to 'publish' it? See if that works.

Regards
Fred
Posted 26 Nov, 2015 10:36:05 Top
Sergey Grischenko


Add-in Express team


Posts: 7233
 Joined: 2004-07-05
Hi Fred,

Please click the 'Populate' button in the Publish wizard and then publish the project again. Let me know if the issue still exists.
Do you get the same issue with a new add-in project?
Posted 27 Nov, 2015 04:34:07 Top
Fred Balkenende




Posts: 29
 Joined: 2007-07-05
Hi Sergey

I have tried to publish (both on the internet and on the 'localhost')and populate many times. Deleted the version folder, and tried again. All without any luck.

I have created a new add-in project, and can make a clickonce installation without any problems!

When I compare the '.deploy' files, they seem to be of the same size and date. But when I look into the application manufest files, there is a difference in the 'DigestValue' for the hash. Isn't that strange?:



<dependentAssembly dependencyType="install" allowDelayedBinding="true" codebase="adxlauncher.exe" size="600792">
<assemblyIdentity name="adxlauncher" version="8.0.4330.0" publicKeyToken="4416DD98F0861965" language="neutral" processorArchitecture="x86" />
<hash>
<dsig:Transforms>
<dsig:Transform Algorithm="urn:schemas-microsoft-com:HashTransforms.Identity" />
</dsig:Transforms>
<dsig:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1" />
<dsig:DigestValue>CjRe+BREKFbdmULb0P7Vd8T4XR8=</dsig:DigestValue>
</hash>
</dependentAssembly>



<dependentAssembly dependencyType="install" allowDelayedBinding="true" codebase="adxlauncher.exe" size="600792">
<assemblyIdentity name="adxlauncher" version="8.0.4330.0" publicKeyToken="4416DD98F0861965" language="neutral" processorArchitecture="x86" />
<hash>
<dsig:Transforms>
<dsig:Transform Algorithm="urn:schemas-microsoft-com:HashTransforms.Identity" />
</dsig:Transforms>
<dsig:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1" />
<dsig:DigestValue>6jMbqnFdMEP2y6+9me8sWLZmngk=</dsig:DigestValue>
</hash>
</dependentAssembly>






Here is the complete logfile for the installation that still fails:

PLATFORM VERSION INFO
Windows : 10.0.10240.0 (Win32NT)
Common Language Runtime : 4.0.30319.42000
System.Deployment.dll : 4.6.114.0 built by: NETFXREL3STAGE
clr.dll : 4.6.127.1 built by: NETFXREL3STAGE
dfdll.dll : 4.6.114.0 built by: NETFXREL3STAGE
dfshim.dll : 10.0.10240.16384 (th1.150709-1700)

SOURCES
Deployment url : http://localhost/officereports.application
Server : Microsoft-IIS/10.0
Deployment Provider url : http://localhost/officereports.application
Application url : http://localhost/5.1.0.22/OfficeReports.exe.manifest
Server : Microsoft-IIS/10.0

IDENTITIES
Deployment Identity : OfficeReports, Version=5.1.0.22, Culture=neutral, PublicKeyToken=1b8a4e57e2591051, processorArchitecture=x86
Application Identity : OfficeReports, Version=5.1.0.22, Culture=neutral, PublicKeyToken=1b8a4e57e2591051, processorArchitecture=x86, type=win32

APPLICATION SUMMARY
* Installable application.

ERROR SUMMARY
Below is a summary of the errors, details of these errors are listed later in the log.
* Activation of http://localhost/officereports.application resulted in exception. Following failure messages were detected:
+ Reference in the manifest does not match the identity of the downloaded assembly adxlauncher.exe.

COMPONENT STORE TRANSACTION FAILURE SUMMARY
No transaction error was detected.

WARNINGS
There were no warnings during this operation.

OPERATION PROGRESS STATUS
* [27-11-2015 11:10:10] : Activation of http://localhost/officereports.application has started.
* [27-11-2015 11:10:10] : Processing of deployment manifest has successfully completed.
* [27-11-2015 11:10:10] : Installation of the application has started.
* [27-11-2015 11:10:10] : Processing of application manifest has successfully completed.
* [27-11-2015 11:10:15] : Found compatible runtime version 4.0.30319.
* [27-11-2015 11:10:15] : Request of trust and detection of platform is complete.

ERROR DETAILS
Following errors were detected during this operation.
* [27-11-2015 11:10:28] System.Deployment.Application.InvalidDeploymentException (RefDefValidation)
- Reference in the manifest does not match the identity of the downloaded assembly adxlauncher.exe.
- 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.FileDownloader.OnModified()
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.PerformDeploymentActivation(Uri activationUri, Boolean isShortcut, String textualSubId, String deploymentProviderUrlFromExtension, BrowserSettings browserSettings, String& errorPageUrl)
at System.Deployment.Application.ApplicationActivator.ActivateDeploymentWorker(Object state)

COMPONENT STORE TRANSACTION DETAILS
No transaction information is available.
Posted 27 Nov, 2015 05:45:50 Top
Sergey Grischenko


Add-in Express team


Posts: 7233
 Joined: 2004-07-05
Hi Fred,

What is the target .NET Framework in the new add-in and the problematic project?
Please send me the adxlaucher.exe file from the problematic project. I will check it.
Posted 27 Nov, 2015 09:49:38 Top
Fred Balkenende




Posts: 29
 Joined: 2007-07-05
Hi Sergey

It is the target .NET Framework that is causing the problem.

The working test add-in was targeting .NET 4.5.2. When changing that to .NET 3.5 (like my problematic project), I get the same problem in the test addin!

I have only one adxlauncher.exe on my machine, in the installation folder of Add-in Express, version 8.0.4330.

Is it possible to get this working for .NET 3.5, or do I have to change to .NET 4, or .NET 4.5?

Regards
Fred
Posted 27 Nov, 2015 10:31:41 Top
Andrei Smolin


Add-in Express team


Posts: 18847
 Joined: 2006-05-11
Hello Fred,

I've just sent you an email with a link to an adxlauncher.exe version that is expected to fix the issue. Please confirm that it fixes the issue for you.


Andrei Smolin
Add-in Express Team Leader
Posted 30 Nov, 2015 06:09:10 Top
Justin Kloos




Posts: 6
 Joined: 2015-12-03
Andrei -

I appear to be having the same issue. Is that latest adxlauncher.exe posted anywhere on the site or will it be included in the next update?

Otherwise, is there any workaround I can do on my end?

Thanks for your help
Posted 03 Dec, 2015 12:41:42 Top
Fred Balkenende




Posts: 29
 Joined: 2007-07-05
Hi Justin

I'm sure Andrei can send you the adxlauncher.exe, which he sent to me.

I solved the problem by changing my addin-module assembly to .NET4

Regards
Fred
Posted 03 Dec, 2015 13:17:59 Top

Posts 1 - 10 of 13
First | Prev. | 1 2 | Next | Last