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

From: Shawn Farkas (shawnfa_at_online.microsoft.com)
Date: 04/23/04 

Date: Thu, 22 Apr 2004 23:39:06 GMT

Hi Bob,

        You're not changing the key you sign with on every compile are you? This could also cause the problem. Also, if you're using the
AssemblyVersionAttribute, know that having a * in the version string will cause a new version to be automatically generated for you on each
compile. I would check these two things first, and if you're still having a problem, check back here and we'll try to help you some more.

-Shawn
http://blogs.msdn.com/shawnfa 

-- 
This posting is provided "AS IS" with no warranties, and confers no rights.
Note:  For the benefit of the community-at-large, all responses to this message are best directed to the newsgroup/thread from which they 
originated.  
--------------------
>From: "Bob Rock" <nospam.yet_another_apprentice@hotmail.com>
>Subject: The located assembly's manifest definition with name 'xxxxxx' does not match the assembly reference???
>Date: Thu, 22 Apr 2004 17:06:12 +0200
>Lines: 31
>X-Priority: 3
>X-MSMail-Priority: Normal
>X-Newsreader: Microsoft Outlook Express 6.00.3790.0
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
>Message-ID: <exV1atHKEHA.2456@TK2MSFTNGP12.phx.gbl>
>Newsgroups: microsoft.public.dotnet.framework,microsoft.public.dotnet.general,microsoft.public.dotnet.security,microsoft.public.vsnet.debugging
>NNTP-Posting-Host: 212.7.72.184
>Path: cpmsftngxa10.phx.gbl!TK2MSFTFEED01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP12.phx.gbl
>Xref: cpmsftngxa10.phx.gbl microsoft.public.dotnet.general:131846 microsoft.public.dotnet.security:5819 microsoft.public.vsnet.debugging:5409 
microsoft.public.dotnet.framework:69858
>X-Tomcat-NG: microsoft.public.dotnet.security
>
>Hello,
>
>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
>
>
>
>
>

Relevant Pages