I have a website written using VS 2008 and targeting .net 3.5
The web site uses some company DLL's written using VS 2005. What the developer of the site did is to not simply reference the DLL's but to include the projects in the solution. They have subsequently been converted to the 2008 format.
Now any of the developers that still use VS2005 and we have a good number of them, can no longer run any solution that also contains these upgraded projects. Oddly the solution builds, i presume because even after the conversion they still target .net 2 and the project file isn't now an invalid format. However after a build and release we see this all the time the DLL's are used.
Could not load file or assembly 'XXX, Version=1.0.0.0, Culture=neutral, PublicKeyToken=e165e554c6dd08c3' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
This is kind of obvious, it suggests the site is looking for 1 version of the dll and finds another but I have given up trying to find out why this is happening. I've opened the solution, deleted and re added the references, checked the DLL isn't in the GAC, it's not it's in all the sites bin folders. It appears to have the correct version numbers. It must be related to the upgrade performed on the project so we rolled it back and voila the sites are working again.
The problem being I can't open the new site developed without breaking the old ones.
Anyone actually understand what's going on here ?