Errors using local version of DLL that differs from version in BIN folder?
Add an Answer
Your question has been submitted and is awaiting moderation.
In our root BIN folder we have a 1.x version of a DLL and we have a 2.x version of the DLL in our module folder. We want this module to use features in the 2.x version, but other modules still need the 1.x version in the root BIN folder.
I have COPY LOCAL turned off so that my local DLL isn't copied down to the root BIN folder.
But when I try to run this module I get the classic "the located assembly's manifest definition does not match the assembly reference" error.
So, I get the nature of what's wrong - my module is looking for that 2.x version of the DLL, but is (for some reason) trying to use the 1.x version of the DLL in the root BIN folder.
What all plays into this?
I understand my root WEB.CONFIG file can control which version of the DLL is to be used, but I've reviewed that file and I don't see any references to this DLL. Are there any other configurations I should be double-checking?