当前位置: 首页 > 图文教程 > 网络编程 > ASP.NET > IsVS.NETreadyforenterprise?(6)

ASP.NET
ASP.NET动态创建控件之绝境求生
客户端回调实现gridView无刷新分页
ASP.NET2.0中将文件上传到数据库
ASP.NET2.0轻松搞定统计图表
asp.net ajax 使用updatepanel更新后的提示
Asp.Net对Xml文件的操作
Asp.net 远程抓取,分解,保存,匹配
ASP.NET 中处理页面“回退”的方法
ASP.NET 2.0中轻松实现网站换肤
C#+ASP.NET 2.0 定制复合组件之基础篇
C#+ASP.NET 2.0 定制复合组件之高级篇
ASP.NET 2.0 服务器控件之复合控件事件
在Apache上调试ASP.NET 1.1/2.0代码
ASP.NET中的DataGrid的属性
动态的管理ASP.NET DataGrid数据列
ASP.NET网站程序预防SQL注入式攻击策略
Windows下SVN配置和apache的配置
.NET事件处理的过程
ASP.net技术:AJAX实现留言板信息展开
三代IIS下ASP.net请求处理过程

ASP.NET 中的 IsVS.NETreadyforenterprise?(6)


出处:互联网   整理: 软晨网(RuanChen.com)   发布: 2009-11-03   浏览: 64 ::
收藏到网摘: n/a


LT: Given that the .NET platform is open to all ISVs, doesn't this mean that developers can mix and match .NET-aware lifecycle tools and get this kind of integration?
MD: There are different levels of integration. The VS.NET environment provides much more integration, and in that sense it is certainly easier to use different vendors' tools. But you still face the issue of deeper semantic integration, such as data integration. With different vendors' products, will you get, for example, common representation of use cases between your requirements management tool and your modeling tool? You benefit from deeper semantic integration, where each tool knows how the rest work.
For another example, our component test tools rely heavily on information stored in the models for test-case generation and test-stub generation. That's harder to integrate between vendors. So you can get good UI integration and control integration across vendors, but not data integration and process integration. Deep integration helps us in providing more lightweight, agile versions of lifecycle tools as well. That's why we didn't just port our stuff to .NET. We rearchitected it. The fundamentals don't change with .NET, or with lifecycle tools, but the practicality of using them with a wider variety of projects will.

LT: The old saw goes, "Wait for rev 3 of any MS product; by then it will be in great shape." That has to be doubly true with a technology as vast as .NET. What would you tell development managers who think they should sit on the sideline and let others work with the inevitable bugs in a first release this ambitious?
MD: Like all technologies, there will be glitches along the way. However, we've been impressed with the completeness and robustness of both VS.NET and Microsoft .NET. Remember, in the past we integrated with many Microsoft technologies but only embedded a few in our product. Now our basic product architecture depends upon Microsoft technology. We cannot ship if VS.NET does not work. Our experience (having built millions of lines of code on this stuff) is that this is a stable platform. We are betting our business on it, and I am happy to say that we are completely confident. Admittedly, we were pretty scared a year ago, but it is now clear that we made exactly the right bet. Those companies that "wait for version 3.0" will simply miss the boat. Those that move quickly should see (and must demand) immediate business returns.