By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
429,435 Members | 2,033 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 429,435 IT Pros & Developers. It's quick & easy.

The located assembly's manifest definition with name 'xxxxxx' does not match the assembly reference???

P: n/a

I'm getting the following error when I update a referenced assembly, but not
recompile my client application project:

"The located assembly's manifest definition with name 'xxxxxx' does not
match the assembly reference"

I've searched the net for this error and I've read that this should be due
to a version change of the referenced assembly (and thus it is suggested
either to add a <bindingRedirect> element in the application config file or
recompile the client application project) but this IS NOT TRUE in my case.
In my case the version of my referenced assembly DOES NOT CHANGE, yet I get
this exception. I suppose that this is due to the fact that my assembly is
strongly named. Could this be the reason??? Can someone confirm to me that
it is so??

Anyhow, I've read that this problem with ASP.NET webforms can also be solved
by enabling JIT (just in time) compilation. But I have a windows forms
application. Not wanting to recompile the client application how can I solve
this problem??? Is using the same keys file to sign the new referenced
assembly (without changing the version number) enough???

Thank you.
Bob Rock

Nov 22 '05 #1
Share this question for a faster answer!
Share on Google+

This discussion thread is closed

Replies have been disabled for this discussion.