是否有任何由 Asp.net MVP + 组成的示例或资源甚至框架？沙堡+ TDD/Nunit +健身？
我们的开发团队目前正在使用 asp.net 2.0，经过大量浏览和跨站点引用，我发现新的东西是 asp.net MVC，但发现它不能做一些事情，例如支持 asp .net 控件，视图状态。
我不确定除了范式的总体变化之外还有什么其他限制，其中每个页面现在将链接到控制器，该控制器将链接到某个视图。因此，为了使学习曲线不那么陡峭，我想首先学习 MVP，因为我认为只要能够取出应用程序和领域层并使其可测试，就已经对我们的整个过程有很大帮助又不会太麻烦。
经过更多浏览后，我发现 ndoc 现在有点过时了，正在被 sandcastle 取代，它有一个额外的附加调用 docproject，这样应该很好地涵盖代码中文档的自动生成。
为了处理验收测试，我发现这个工具称为fitnesse，它基于FIT，应该会有所帮助。
因此，对于所有这些都是全新的，我想知道这是否是一个很好的过程，可以使用这个工具来覆盖我们团队的开发过程。是否有其他示例/资源/框架涵盖了所有这些步骤，并且比尝试使用多种工具（即框架）来弥补差距更好？
基本上我的问题是我的 上面很好地涵盖了整个流程 通过我研究过的工具？
有没有更好的方法来做到这一点 asp.net tdd + 自动文档生成 + 验收测试？
任何建议/反馈表示赞赏。 谢谢！！ :)
our dev team is currently using asp.net 2.0 and after a lot of browsing and cross site referencing i found that the new in thing is the asp.net MVC but found that there's a few things that it can't do such as support asp.net controls, view state.
i'm not sure what are the other limitation besides the total change of paradigm where each page will now link to the controller which will be linked to a certain view. so in order to make the learning curve to be less steep, i wanted to pick up on MVP first as i think by just being able to take out the application and domain layer out and make them testable is already a big help to our total process without being too much of a hassle.
after more browsing around, i find that the ndoc is a bit outdated now and is being replaced by sandcastle which has an additional add in call docproject so that should covers the auto generation of the documentation in the codes very well.
and to handle the acceptance test, i find this tool call fitnesse which is based on FIT which should helps.
so being totally new to all of this, i'm wondering if this is a good process overall to have this tool in to cover our team's development process. and if there's other sample/resources/framework out there which covers all of these steps and does a better job than trying to piece in the gap by using several tools, i.e. a framework?
basically my question is is my
overall process above well covered
by the tools that i've researched?and is there a better way to do the
asp.net tdd + auto doc generation +
acceptance testing?
any advice/feedback is appreciated.
thanks!! :)
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
是的，带有 NUnit 和 FitNesse 的 ASP.NET MVC 是“敏捷”方法的合理选择。只是不确定自动文档生成在哪里适合这个。有人会阅读这个生成的文档还是只会查看代码？如果您还没有阅读过，请阅读 Robert Martin 的“干净代码”，了解一些关于如何使代码可维护和易于理解而无需大量注释和生成文档的好技巧。
Yes, ASP.NET MVC with NUnit and FitNesse are reasonable choices for an 'agile' approach. Just not sure where auto-doc generation fits into this. Will anyone read this generated documentation or will they just look at the code? If you haven't read it yet, get Robert Martin's 'Clean Code' for some good tips on how to make code maintainable and understandable without lots of comments and generated documents.