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

ASP.NET
Asp.net Ajax--Calendar控件使用
让ASP.NET程序自动为URL加上超级链接
ASP.NET2.0MasterPage技巧总结
asp.net读取数据库乱码的解决完全方案
asp.net中生成缩略图并添加版权
ASP.Net用MD5和SHA1加密的几种方法
asp.net客户端回调功能的实现机制
ASP.NET2.0中控件的简单异步回调
用在JavaScript的RequestHelper
用Java发送图文并茂的HTML邮件
基于.NET平台的分层架构实战(一) 综述
基于.NET平台的分层架构实战(二)需求分析与数据库设计
基于.NET平台的分层架构实战(三)架构概要设计
基于.NET平台的分层架构实战(四)实体类的设计与实现
近期的几个ASP.NET开发经验总结和收集
ASP.NET中的状态管理
asp.net基础知识介绍
对数据访问层第一种实现(Acc+SQL)的重构
.NET初学者推荐课程 asp.net错误代码大全
在.net中如何利用数据工厂实现多数据库的操作

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


出处:互联网   整理: 软晨网(RuanChen.com)   发布: 2009-11-03   浏览: 76 ::
收藏到网摘: 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.