流行的文件夹结构 [英] Popular folder structure for build

问题描述

我想知道在项目中组织构建资产和源代码的最流行或最佳方法是什么？

I am wondering what the popular or best way to organise your build assets and source code within a project is?

推荐答案

我个人使用

/client/projectname/trunk/source/Solution Name.sln
/client/projectname/trunk/source/Project.One
/client/projectname/trunk/source/Project.Two
/client/projectname/trunk/source/Project.Three
/client/projectname/trunk/source/SQL/
/client/projectname/trunk/source/SQL/SomeScript.sql
/client/projectname/trunk/libraries
/client/projectname/trunk/resources/Nunit
/client/projectname/trunk/resources/LLBLGEN
/client/projectname/trunk/documentation
/client/projectname/trunk/builds

对我们来说很好，但是我认为这不是最好的。 如果是关于.net 的，您还可以看看 treesurgeon 它本身就是：

It works fine for us but I don't think it's the best. If it's about .net you can also take a look at treesurgeon They describe it themselves as:

您是否花了几天时间建立了新的开发树？您是否花了几天时间建立了多个开发树？您甚至花了数周的时间尝试使用一套最佳实践来完善所有开发树吗？

Have you ever spent a few days setting up a new development tree? Have you ever spent several days setting up several development trees? Have you even spent weeks trying to perfect all your development trees using a set of best practices?

如果以上任何一个答案的答案都是是，那么您会喜欢Tree Surgeon！

If the answer to any of the above answers is 'yes', then you'll like Tree Surgeon!

Tree Surgeon是一个.NET开发树生成器。只要给它命名您的项目名称，它就会在几秒钟内为您建立一个开发树。不仅如此，您的新树还拥有数年的内置累积的构建工程经验。

Tree Surgeon is a .NET development tree generator. Just give it the name of your project, and it will set up a development tree for you in seconds. More than that, your new tree has years worth of accumulated build engineering experience built right in.

这篇关于流行的文件夹结构的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！