Project Dependencies on Multiple Versions of Visual Studio

Question

I have a 3.net project.

Project1.dll is created by project VS2008.

Project2.dll is created by project VS2005, which references Project1.dll.

Project3.dll is created by project VS2008, which refers to both Project1.dll and Project2.dll.

Now I create Project1.dll and manually copy it to the place where Project 2 can pick it up.

Then I create Project2.dll and manually copy it and Project1.dll to where Project 3 can pick them up.

Obviously, I am doing something wrong (manual). What is the right way to update the relevance of our projects?

---

Upgrading Project2 to VS2008 and then creating one solution containing all 3 projects is currently not an option. We have a third-party visualstudio plugin that does not work in VS2008 yet. Project2 should stay in VS2005

Undoing the upgrade of Project1 and Project3 to VS2005, and then creating one solution is also not an option. We rely on the capabilities of C # 3.0 and .net 3.5 in these projects.

Answer 1

, . Project Properties-> Build → Output path. . , , - , . (Debug, Release), .

Answer 2

pre-build Project3, Project1, Project2, 2 project3.

Answer 3

csproj/vbproj . ( , , ), VS2008 2.0, . , .

, , - -, . , MSBuild.

Answer 4

script, , DLL , .

Answer 5

The trick I used in the past is to move everything to 2008. Then I set up a special solution in 2005 for the second project and use it to work with the add-on. How it works, it depends on how poorly the two projects work in 2008.