在管理团队x86和x64工作站之间的参考路径 [英] Managing reference paths between x86 and x64 workstations in a team

问题描述

我想知道如何.NET团队出有处理组件的参考路径时，并不是每个人都可以立即升级到64位操作系统。关键的问题，现在是64位版本的Windows将种植32位安装到C：\ Program Files文件（x86）的\，而不是常规的C：\ Program Files文件。这意味着许多额外的组件和第三方框架，最终在C：\ Program Files文件（x86）的

I would like to know how .NET teams out there are handling assembly reference paths when not everybody can immediately upgrade to a x64 operating system. The key issue right now is x64 versions of Windows will plant 32-bit installations into C:\Program Files (x86)\ instead of the regular C:\Program Files. This means many extra components and frameworks from 3rd parties end up in C:\Program Files (x86).

所以当你下载了86工作站修改到64位工作站创建的源项目/，还有就是获得参考路径正确需要进行一些修改工作。非常典型地，64用户可以保存修改并提交自己的preferences回版本控制库，打破了86用户的节奏。

So when one downloads source projects created/modified in a x86 workstation onto a x64 workstation, there is some modification work required to get the reference paths correct. Quite typically, x64 users may save the modification and commit their "preferences" back into the version control repository, breaking the rhythm of the x86 users.

有什么好的方法来保持和谐在不同的团队？

What are some good approaches to maintain harmony in a varied team?

推荐答案

无论是每台机器上安装在GAC中的程序集，或者根据您的解决方案根特殊的LIB文件夹包含所有的第三方组件。 lib文件夹是我用在过去的几年里我自己。我甚至把在源头控制的组件，以便其他/新的开发者让他们不必去想它。

Either install the assemblies in the GAC on each machine, or have a special LIB folder under your solution root that contains all your 3rd party assemblies. The LIB folder is what I've used for the last few years myself. I even put the assemblies in source control so other/new developers get them without having to think about it.

这篇关于在管理团队x86和x64工作站之间的参考路径的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！