Developers with VS 2005 and VS 2008 are working on the same project (s)

We have a solution with a website and a class library. We also have developers working in VS 2005 and VS 2008. The problem is that the user adds a file / removes the file from the class library, which he does not add to the project file for users (users) using a different version of VS. I also had to configure our automatic build to use a single project file. Is there a way around this, or do we need to upgrade each to 2008?

0
source share
4 answers

Working with two different versions of Visual Studio in a team of more than one project member makes absolutely no sense. I recommend upgrading to Visual Studio 2005 or upgrading to Visual Studio 2008. You can install multiple versions of Visual Studio on the same computer without any side effects.

+6
source

You will need to save each solution file in the same visual studio. It is normal to split your product into several solutions. In this case, you may have a .sln file that contains your 2005 projects and 1. Sln that contains your 2008 projects.

As you already mentioned, there is no automatic way to synchronize a 2005 and 2008 project, because when you add a file to one of the projects, the other will not have this new file. Similarly, when you delete files.

+5

, VS 2005 - , VS08, DLL , dll - , , , , .

0

"-" ( "-" ), 2005 2008 . .

2005 2008 /. CLR, "".

2008 , *.sln ( *.2005.sln), *.sln . "Format Version 10.0" "Format Version 9.0". .

, VS 2008, , , VS 2005.

, -. vbproj csproj - :

<Import Project="$(MSBuildExtensionsPath)\Microsoft\VisualStudio\v9.0\WebApplications\Microsoft.WebApplications.targets" Condition="" />

:

<Import Project="$(MSBuildExtensionsPath)\Microsoft\VisualStudio\v8.0\WebApplications\Microsoft.WebApplications.targets" Condition="'$(Solutions.VSVersion)' == '8.0'" />
<Import Project="$(MSBuildExtensionsPath)\Microsoft\VisualStudio\v9.0\WebApplications\Microsoft.WebApplications.targets" Condition="'$(Solutions.VSVersion)' == '9.0'" />

These two lines will conditionally select the correct MSBuild path depending on the version of VS you are using.

0
source

Source: https://habr.com/ru/post/1706452/


All Articles