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

问题描述

我想知道当不是每个人都可以立即升级到 x64 操作系统时，.NET 团队如何处理程序集引用路径.现在的关键问题是 x64 版本的 Windows 会将 32 位安装植入 C:Program Files (x86) 而不是常规的 C:Program Files.这意味着来自第 3 方的许多额外组件和框架最终都位于 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).

因此，当将在 x86 工作站中创建/修改的源项目下载到 x64 工作站上时，需要进行一些修改工作才能使参考路径正确.很典型地，x64 用户可能会保存修改并将他们的首选项"提交回版本控制存储库，打破 x86 用户的节奏.

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 文件夹，其中包含所有 3rd 方程序集.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屋！