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

From: Bob Rock (nospam.yet_another_apprentice_at_hotmail.com)
Date: 04/22/04

  • Next message: Joe Kaplan \(MVP - ADSI\): "Re: Using Windows Integrated Security for Windows form application" 
    Date: Thu, 22 Apr 2004 17:06:12 +0200

    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

  • Next message: Joe Kaplan \(MVP - ADSI\): "Re: Using Windows Integrated Security for Windows form application"

    Relevant Pages