什么是Microsoft开发环境设置最佳实践

I've just joined a small team of developers and there doesn't seem to be any rhyme or reason to the way each developer sets up their development environment or how they use version control (currently Source Safe).

我刚刚加入了一个小型开发团队,每个开发人员设置他们的开发环境或者他们如何使用版本控制(目前是Source Safe)似乎没有任何押韵或理由。

I made the "mistake" of asking a question about their standard practices. To keep a long story short, this earned me the task of coming up with a plan to standardize everything we reasonably can since there currently is NO standard and this is causing unnecessary delays and headaches. So I'm hoping some of you can give me some advice or point me to some good resources in this regard.

我提出了一个关于他们标准做法的问题的“错误”。总而言之,这让我的任务是制定一项计划,将我们合理的一切标准化,因为目前没有标准,这导致了不必要的延误和头痛。所以我希望你们中的一些人可以给我一些建议,或者指出我在这方面的一些好资源。

A little background. Our team is about 10 developers all working on .NET projects ranging from DotNetNuke Portals and Modules, to Webservices, to WPF projects. Most developers work autonomously (hence the difference in everyone's setup), but we all have to have access (currently through Source Safe) to all projects for support, bug hunts and enhancements.

一点背景。我们的团队大约有10名开发人员,他们都致力于.NET项目,包括DotNetNuke门户和模块,Webservices,以及WPF项目。大多数开发人员自主工作(因此每个人的设置都不同),但我们都必须访问(目前通过Source Safe)所有项目以获得支持,漏洞搜索和增强功能。

I'm looking for suggestions as simple as should we standardize locations for third party dlls on each of our boxes or use a network location for those so all references are consistent - to what's the best way to organize our projects folder structure - to coming up with a plan to reorganize everything step by step (ie. leave it where it is until you need to work on it and then migrate it into the new system).

我正在寻找简单的建议,我们应该在每个盒子上标准化第三方dll的位置,或者使用网络位置,以便所有引用都是一致的 - 组织我们的项目文件夹结构的最佳方式 - 即将到来计划一步一步地重组所有内容(即将它留在原处,直到你需要对它进行处理,然后将其迁移到新系统中)。

Any help would be greatly appreciated.

任何帮助将不胜感激。

3 个解决方案

#1

Use project based references wherever possible. For thirdparty dlls, make sure you have a seperate folder called Lib or something like that and have each third party dll in their respective vendor folders.

尽可能使用基于项目的参考。对于第三方dll,请确保您有一个名为Lib的单独文件夹或类似的东西,并在每个供应商文件夹中包含每个第三方dll。

E.g

Lib\
Lib\Infragistics
Lib\Telerik

This structure can be sometimes outside of all your projects if multiple projects are referencing them.

如果多个项目引用它们,则此结构有时可能位于所有项目之外。

Then you can easily set the path to these dll's from your project. Also, a lot depends on if you are changing the source code of these third party vendors, then you may have to really think through as every team in your group may want to make some changes and have their instance to be independent of dependencies or bugs caused by changes from the other teams.

然后,您可以轻松地从项目中设置这些dll的路径。此外,很大程度上取决于您是否要更改这些第三方供应商的源代码,然后您可能必须真正思考,因为您组中的每个团队都可能希望进行一些更改并使其实例独立于依赖项或错误由其他团队的变化引起的。

You can look up more information on the following topics on the web to help you setup a standard process.

您可以在Web上查找有关以下主题的更多信息,以帮助您设置标准流程。

Continuous Integration
Cruise Control.NeT
Nant

Also, note that you should not emphasize too much on the solution structure organization. The real focus should be Continous Integration, good build process and automating as much build stuff as possible. It will get you a good impression if you create a streamlined release process for all your patches, app roll outs, etc.

另请注意,您不应过多强调解决方案结构组织。真正的重点应该是持续集成,良好的构建过程以及尽可能多的自动构建。如果您为所有补丁,应用程序推出等创建简化的发布流程,它将给您留下良好的印象。

#2

Workstations where I work:

我工作的工作站:

Intel Q6600
4GB RAM
3 22" LCDs

3 22“LCD

Vista Business 64-bit w/SP1 (ibstupidhate)

Vista Business 64位w / SP1(ibstupidhate)

Visual Studio 2008 w/SP1

Visual Studio 2008 w / SP1

Up to .Net 3.5

高达.Net 3.5

Visual Source Safe client (ugh)

Visual Source Safe客户端(呃)

SQL Server Management Studio

SQL Server Management Studio

Chrome/FF 3/IE7/Opera/Safari

My system also has CodeSmith Studio Professional since I deal with all netTiers generation in the office.

我的系统也有CodeSmith Studio Professional,因为我处理办公室里所有的netTiers。

Vista hasn't given me any issues, just having to start VS2008 in Administrative mode when I'm testing WCF hosts. Hate as much as you want, but Vista has been solid for me since Feb. 2007.

Vista没有给我任何问题,只是在我测试WCF主机时必须以管理模式启动VS2008。讨厌你想要的,但自2007年2月以来,Vista对我来说一直很好。

#3

1) Operating System: Use Windows XP till Windows 7 is out Install the service packs and all the updates. 2) Install .Net Framework 2.0 and service packs for it

1)操作系统:使用Windows XP直到Windows 7出来安装Service Pack和所有更新。 2)为它安装.Net Framework 2.0和Service Pack

3) Install .Net Framework 3.0

3)安装.Net Framework 3.0

4) Install .Net Framework 3.5

4)安装.Net Framework 3.5

5) Install Visual Studio 2008 and SP1 for it

5)为它安装Visual Studio 2008和SP1

6) Install SVN Server (from Collabnet) and TortoiseSVN (from tigris) for version controlling

6)安装SVN服务器(来自Collabnet)和TortoiseSVN(来自tigris)进行版本控制

7) If you people build very customized WPF interfaces then install MS Expression Studio

7)如果您构建了非常自定义的WPF界面,请安装MS Expression Studio

8) Install Chrome, Firefox 3 (with FireBug), IE 8 (it can emulate 7) and Opera for testings

8)安装Chrome,Firefox 3(使用FireBug),IE 8(可以模拟7)和Opera进行测试

9) Install SQL Server Management Studio

9)安装SQL Server Management Studio

This will set you up for starting developing WPF, Asp.net and WinForms apps.

这将为您开始开发WPF,Asp.net和WinForms应用程序。

#1