Ok, I have been working on this one for about a week and am reaching the end of my idea chain.
We have a classic asp website we added a .Net 3.5 application to and are slowly phasing out asp pages as we create them in asp.net. This has been working well with the one solution (application) and several sub projects except when deploying our latest piece. Basically, every time a server in our farm is restarted, if a page from our web application isn't visited before that of another sub project in the .Net application, our application will not work. We get the error message below with no detail as to what assembly the first time any of our pages are visited. On second visit, they work fine. Anyone have any advice on how to track down this issue?
We have made sure only the root application has a bin directory and all references are there, and that none conflict with the GAC, but still no love.
System.IO.FileLoadException: The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
View Complete Post