I'm also familiar with the 'Subversion + Cruise Control + Fogbugz + nCover + ...' setup used in dev houses. But what other options are there? I'm pretty naive outside of these 2 combinations. I'm from the .net world and perhaps LISP of Ruby developers do it completely differently?
我也熟悉开发室中使用的'Subversion + Cruise Control + Fogbugz + nCover + ...'设置。但还有其他选择吗?在这两种组合之外,我很天真。我来自.net世界,也许Ruby开发人员的LISP完全不同吗?
3 个解决方案
#1
I'm mostly into open-source software stack for developing in .NET (except for the Microsoft Project which does not have any alternatives when you need to handle really complex projects).
我主要是用于在.NET中开发的开源软件栈(除了Microsoft Project,当你需要处理真正复杂的项目时没有任何替代方案)。
In short, primary software ingredients are:
简而言之,主要软件成分是:
- CruiseControl.NET
- Subversion
- Trac (issues + wiki + SVN) / Google Code for open-source projects
- NCover, NUnit, FxCop, SandCastle, Wix, Lokad Shared Libraries, Autofac, FxCop etc.
Trac(issue + wiki + SVN)/ Google Code for open-source projects
NCover,NUnit,FxCop,SandCastle,Wix,Lokad共享库,Autofac,FxCop等。
Project management approach: start projects in a PM style (a lot of planning, clarification and prototyping), get to the first release (minimal functionality, all services are mocked, plain UI), then turn on continuous integration and switch to Agile (while still using PM to plan and schedule on a larger scale).
项目管理方法:以PM风格启动项目(大量规划,澄清和原型设计),获得第一个版本(最小功能,所有服务都被模拟,纯UI),然后打开持续集成并切换到敏捷(同时仍然使用PM来规划和安排更大规模)。
Related links:
- Software I've been using
- Common Development principles
- Component-Driven Development of applications
- xLim development approach
我一直在使用的软件
共同发展原则
组件驱动的应用程序开发
xLim开发方法
#2
look here for Application Life Cycle start point
在这里查看应用程序生命周期的起点
ALM + TFS链接在这里
What some people do (me for instance) is to simply have Git doing the source version control and perform project management separately with SharePoint (WSS 3.0) or MOSS and/or with Microsoft Office Project
有些人(例如我)做的就是让Git单独使用SharePoint(WSS 3.0)或MOSS和/或Microsoft Office Project来执行源版本控制并执行项目管理
(Windows应用程序,服务器)
#3
Concerning code quality checking, architecture exploration, code versions diff and more... you can have a look at NDepend.
关于代码质量检查,架构探索,代码版本差异等等......你可以看看NDepend。
#1
I'm mostly into open-source software stack for developing in .NET (except for the Microsoft Project which does not have any alternatives when you need to handle really complex projects).
我主要是用于在.NET中开发的开源软件栈(除了Microsoft Project,当你需要处理真正复杂的项目时没有任何替代方案)。
In short, primary software ingredients are:
简而言之,主要软件成分是:
- CruiseControl.NET
- Subversion
- Trac (issues + wiki + SVN) / Google Code for open-source projects
- NCover, NUnit, FxCop, SandCastle, Wix, Lokad Shared Libraries, Autofac, FxCop etc.
Trac(issue + wiki + SVN)/ Google Code for open-source projects
NCover,NUnit,FxCop,SandCastle,Wix,Lokad共享库,Autofac,FxCop等。
Project management approach: start projects in a PM style (a lot of planning, clarification and prototyping), get to the first release (minimal functionality, all services are mocked, plain UI), then turn on continuous integration and switch to Agile (while still using PM to plan and schedule on a larger scale).
项目管理方法:以PM风格启动项目(大量规划,澄清和原型设计),获得第一个版本(最小功能,所有服务都被模拟,纯UI),然后打开持续集成并切换到敏捷(同时仍然使用PM来规划和安排更大规模)。
Related links:
- Software I've been using
- Common Development principles
- Component-Driven Development of applications
- xLim development approach
我一直在使用的软件
共同发展原则
组件驱动的应用程序开发
xLim开发方法
#2
look here for Application Life Cycle start point
在这里查看应用程序生命周期的起点
ALM + TFS链接在这里
What some people do (me for instance) is to simply have Git doing the source version control and perform project management separately with SharePoint (WSS 3.0) or MOSS and/or with Microsoft Office Project
有些人(例如我)做的就是让Git单独使用SharePoint(WSS 3.0)或MOSS和/或Microsoft Office Project来执行源版本控制并执行项目管理
(Windows应用程序,服务器)
#3
Concerning code quality checking, architecture exploration, code versions diff and more... you can have a look at NDepend.
关于代码质量检查,架构探索,代码版本差异等等......你可以看看NDepend。