Does anyone have experience collaborating with someone using a different version of Visual Studio?
有没有人有使用不同版本的Visual Studio与某人合作的经验?
If I upgrade to VS 2008 or 2010, how hard will it be to work with someone using VS 2005?
如果我升级到VS 2008或2010,与使用VS 2005的人合作有多难?
I realize that I'll have to target .NET 2.0 or whatever in the projects we will share, but I'm more interested in how to deal with project/solution file differences.
我意识到我必须针对.NET 2.0或我们将分享的项目中的任何内容,但我对如何处理项目/解决方案文件差异更感兴趣。
If I update my .vcproj to VS 2008, will I not be able to check it into source control because the other person wouldn't be able to read it? If so then how do I make sure that if I add a file to my project, that their project will pick it up?
如果我将.vcproj更新到VS 2008,我是否无法将其检入源代码管理,因为其他人无法读取它?如果是这样,那么如何确保如果我将一个文件添加到我的项目中,那么他们的项目会把它拿起来?
Is there some way to automate generating multiple project files for each VS version? If not what are some best practices for dealing with this situation.
有没有办法自动为每个VS版本生成多个项目文件?如果不是,处理这种情况的最佳做法是什么。
4 个解决方案
#1
The easiest and simplest way that I've found is to maintain a copy of downlevel versions of Visual Studio on my machine. I've not had any problems or issues to date.
我发现的最简单和最简单的方法是在我的机器上维护Visual Studio的下层版本。到目前为止,我没有任何问题或问题。
If you do want to only have 2k8 or 2k10 on your machine, then the next option is to maintain two sets of SLN/CSPROJ files in each format. Obviously this involves the risk of having to check for new files to add into the project yourself but that shouldn't be too bad if there's just two of you working on the project.
如果您确实希望机器上只有2k8或2k10,则下一个选项是在每种格式中维护两组SLN / CSPROJ文件。显然,这涉及到必须检查要自己添加到项目中的新文件的风险,但如果您只有两个人正在处理该项目,这不应该太糟糕。
#2
regarding source control it's even more annoying: they have to be the exact version, release, service pack & everything else otherwise they'll have different version numbers in the project/solution files. One guy here has forgotten a service pack or something. You always know when he's checked in.
关于源代码控制,它更令人讨厌:它们必须是确切的版本,发行版,服务包和其他所有内容,否则它们将在项目/解决方案文件中具有不同的版本号。这里的一个人忘记了服务包或其他东西。你总是知道他什么时候办理登机手续。
#3
If possible, you should really try to use the same version of Visual Studio for all developers working with the same code.
如果可能,您应该尝试为使用相同代码的所有开发人员使用相同版本的Visual Studio。
The last time I was in a situation where the same project needed to be used in different versions of Visual Studio we were switching between VS 2003 and VS 2005 (building a class library targeting .NET 1.1 and 2.0). That was somewhat of a pain, since we manually needed to keep the project files in sync.
我最后一次遇到需要在不同版本的Visual Studio中使用相同项目的情况时,我们在VS 2003和VS 2005之间进行切换(构建面向.NET 1.1和2.0的类库)。这有点痛苦,因为我们手动需要保持项目文件同步。
#4
The way I would try to solve this is by getting the other developer to upgrade to Visual Studio 2008, as you are able to target older versions of the framework in the compiled binary is there any reason for them not to upgrade? :)
我试图解决这个问题的方法是让其他开发人员升级到Visual Studio 2008,因为你能够在编译的二进制文件中定位旧版本的框架是否有任何理由让他们不升级? :)
#1
The easiest and simplest way that I've found is to maintain a copy of downlevel versions of Visual Studio on my machine. I've not had any problems or issues to date.
我发现的最简单和最简单的方法是在我的机器上维护Visual Studio的下层版本。到目前为止,我没有任何问题或问题。
If you do want to only have 2k8 or 2k10 on your machine, then the next option is to maintain two sets of SLN/CSPROJ files in each format. Obviously this involves the risk of having to check for new files to add into the project yourself but that shouldn't be too bad if there's just two of you working on the project.
如果您确实希望机器上只有2k8或2k10,则下一个选项是在每种格式中维护两组SLN / CSPROJ文件。显然,这涉及到必须检查要自己添加到项目中的新文件的风险,但如果您只有两个人正在处理该项目,这不应该太糟糕。
#2
regarding source control it's even more annoying: they have to be the exact version, release, service pack & everything else otherwise they'll have different version numbers in the project/solution files. One guy here has forgotten a service pack or something. You always know when he's checked in.
关于源代码控制,它更令人讨厌:它们必须是确切的版本,发行版,服务包和其他所有内容,否则它们将在项目/解决方案文件中具有不同的版本号。这里的一个人忘记了服务包或其他东西。你总是知道他什么时候办理登机手续。
#3
If possible, you should really try to use the same version of Visual Studio for all developers working with the same code.
如果可能,您应该尝试为使用相同代码的所有开发人员使用相同版本的Visual Studio。
The last time I was in a situation where the same project needed to be used in different versions of Visual Studio we were switching between VS 2003 and VS 2005 (building a class library targeting .NET 1.1 and 2.0). That was somewhat of a pain, since we manually needed to keep the project files in sync.
我最后一次遇到需要在不同版本的Visual Studio中使用相同项目的情况时,我们在VS 2003和VS 2005之间进行切换(构建面向.NET 1.1和2.0的类库)。这有点痛苦,因为我们手动需要保持项目文件同步。
#4
The way I would try to solve this is by getting the other developer to upgrade to Visual Studio 2008, as you are able to target older versions of the framework in the compiled binary is there any reason for them not to upgrade? :)
我试图解决这个问题的方法是让其他开发人员升级到Visual Studio 2008,因为你能够在编译的二进制文件中定位旧版本的框架是否有任何理由让他们不升级? :)