A: 

You cant have the same assembly referenced twice in one program, even if they are different version, it's just the way visual studio works. You need to reconstruct and recompile the code that references the older assemblies using the new versions of the assembly. This can be done via a reflector, and is relatively easy if you know what you are doing.

Richard J. Ross III  2010-09-06 19:37:30
I'm not trying to refer to the old assemblies, and I dont want visual studio to add a reference to it. I want it to blindly add it as content that will be deployed to the build directory.
djmc  2010-09-06 21:08:06
sorry, I noticed someone changed my url to an embedded image. It was probably hard to tell what I was trying to do in my project. I made the image a hyperlink so ppl can view it in a larger size.
djmc  2010-09-06 21:13:19

related questions

Java Compiler Options to produce .exe files.
Which compiles to faster code: "n * 3" or "n+(n*2)"?
profile-guided optimization (C)
Tools for converting non-Java into Java source
What's safe for a C++ plug-in system?
C++ Compiler Error C2371 - Redefinition of WCHAR
function declaration isn't a prototype
Learning Resources on Parsers, Interpreters, and Compilers
Compiler Error C2143 when using a struct
Which 4.x version of gcc should one use?
How to remove debug statements from production code in Java
.NET Compiler -- DEBUG vs. RELEASE
C on Visual Studio
What's a 'null defined macro'?
Warning: Found conflicts between different versions of the same dependent assembly
Mixed C++/CLI TypeLoadException Internal limitation: too many fields.
Bootstrapping a language
Checking for string contents? string Length Vs Empty String
What are the best resources on designing a new language?
Code crash in MS Visual Studio 2005 in RELEASE configuration
Invalid Resource File
C# logic order and compiler behavior
CSharpCodeProvider Compilation Performance
Learning to write a compiler
Adding Scripting functionality to .NET applications