我们有一台新的构建机器可供我们的编程团队使用。我们仍在尝试弄清楚如何组织一切以获得构建 EXE 和 DLL 的最佳配置。
我们使用VB6和VB.Net 2005以及VSS2005。
我们正在考虑为每个项目、发布和支持票证设置工作文件夹。有人有类似设置的经验吗？你喜欢/不喜欢什么？有什么建议（新的 VSS ID、文件夹配置、设置工作文件夹、更新/构建文件）？
We have a new build machine to start using for our programming team. We are still trying to figure out how we want to organize everything to get the best configuration for building EXEs and DLLs.
We are using VB6 and VB.Net 2005, and VSS2005.
We were thinking of making working folders set for each project, release and support tickets. Does anyone have experience with a similar set up? What were your likes/dislikes? Any recommendations (New VSS IDs, folder configuration, setting working folder, updating/building files)?
发布评论
评论（2）
保持敏捷——不断成长，不要害怕随着时间的推移而改变。选择一些非常简单的事情开始，看看效果如何。
这是我的简单环境。确定您想要在桌面上执行什么操作来实施 joel 测试问题 #2。根据我的经验，这一点至关重要。一旦您可以通过一次（或几次）点击在桌面上完成完整的构建和测试，那么您就拥有了自动化构建机器的基础。
诀窍是使用手边的任何工具快速完成此任务 - 例如 VSS 和 巡航控制，MSBuild等，并进行调整。经过几天的迭代努力，您应该能够获得相当好的结果（80/20 规则）。
编辑：只是为了回答评论。
是的，你是对的，学习其他人的经验（而不仅仅是他们的做法）是非常有益的。然而，在不同的公司建立构建环境后，我可以说最好的事情是，一旦您从其他人的复杂性开始，您最终会与其他人的要求和假设作斗争。是的，我现在已经有了经验，我可以用它作为衡量标准来轻松开始。
be agile - just grow it and and don't be afraid to change as you go a long. Pick something very simple to start with and see how it goes.
Here is my simple environment. Decide what you want to do on a desktop to implement the joel test question #2. This in my experience is pivotal. Once you can do the complete build and test on a desktop with one (or a couple of) clicks then you have the basis for an automated build machine.
The trick is get this going quickly using what ever tools are at hand quickly - e.g. VSS and Cruise control, MSBuild etc, and tune. You should be able to get a pretty good (80/20 rule) in a few days of iterative effort.
Edit: Just to answer comment.
Yes you are correct is is be very beneficial to learn from other people experiences (not just their practises). However having set up build environments in may different companies I can say the best thing is once you start with some else's complexity you end up fighting other peoples requirements and assumptions. Yes I've now got experience and I can use that as a metric to start easily.
构建相互依赖的 VB6 组件时要注意问题 - 请参阅 这个问题。
Watch out for issues when building VB6 components that depend on each other - see discussion in this question.