Manifest definition does not match the assembly reference

  • Thread starter Thread starter Alex
  • Start date Start date
A

Alex

I have an ASP.NET application that works fine locally and on
development servers. However when I deploy to a live site I get an
manifest definition error. The reference is to a 3rd party managed
control. Is there any way to 'update' this reference?

Any ideas?

Thanks

Alex
 
Hi Alex,

There is no need to update the reference. Rather, you need to deploy the 3rd
party assembly to a location where the CLR Fusion engine can locate it. Some
of such locations are:

* The GAC
* The application's "bin" folder.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

My manifest loading a reference twice 1
common Issue with Manifest while deploying using ClickOnce 0
manifest definition does not match the assembly reference 4
Assembly's manifest definition does not match the assembly reference 2
ClickOnce: Reference in the manifest does not match the identity of the downloaded assembly 1
Assembly loading error "manifest definition... does not match assembly reference" 3
Huge problem with References DLL's. Please Help 3
solution does not run after upgrading assemblies 2

Back
Top