Where Does ASP.NET Store Assembly References Other Than web.config?


I am getting the classic exception

Could not load file or assembly 'XXX.Base, Version=, Culture=neutral, >PublicKeyToken=xxxxxxxxx' or one of its dependencies. The located assembly's >manifest definition does not match the assembly reference. (Exception from >HRESULT: 0x80131040) The assembly D:\xxx\xxxx\xxx\bin\xxx.xxx.xxx.xxx.dll was found but could not >be loaded. It might have the same name as the referenced one but different version, >culture or public key token.

I know there are tons of these posts on SO and all over the web, but I have one question to which I have not been able to find an answer. Where else, other than web.config, does an ASP.NET get these version numbers from? In the references section of my app, the version is listed as However, when I compile the app and put into IIS, I'm getting exceptions for the wrong version number.

I have already tried:

  • recompiling the app,
  • restarting the server,
  • restarting IIS,
  • clearing the ASP.NET temp files
  • restarting the app pool,
  • putting a newly recompiled version of the app onto the server,
  • checking the web.config (I can't even find some of these dlls referenced at all in the web.config file)
  • checking the packages.config file (it's not in here either)

Are there any other spots where these references are stored? I know that in visual studio I can expand references, but I'm assuming that list is stored in a file somewhere and I'm wondering where that file might be?

Where does my app get the idea that it needs version of the assembly when it's listed as in references?

asked on Stack Overflow Aug 5, 2019 by hexagod • edited Aug 5, 2019 by Jester

0 Answers

Nobody has answered this question yet.

User contributions licensed under CC BY-SA 3.0