Project References DLL version hell

Question

We\'re having problems getting visual studio to pick up the latest version of a DLL from one of our projects.

We have multiple class library projects (e.g. Business

Answer 1

We (and, as the only .NET developer on our team, by that I mean I) had the exact same problem. I traced it down to a referenced dll, which in turn AGAIN references the dll suffering from versionitis. It seems that because I wasn't updating all the references which in turn reference the dll, it was replaced by an older version at some point during the build process.

One of the symptoms I experienced was that when I am in the code editor, the new class I added to the referenced project would be coloured appropriately, but when I hit Build, it changes back to black and I get a message saying the class does not exist (along with a very sarcastic "Ar you missing an assembly reference?"). This led me to believe that the problem has to happen during the Build phase.

I would therefore suggest building any and every other project that points to this DLL and re-add their references too.