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

ASP.NET
.NET可复用TCP通信层之消息分派器组件
Asp.Net结合JS在图层上显示记录信息
.NET 2.0里使用强类型数据创建多层应用
ADO.NET Entity Framework 试水——并发
.Net开发:ADO.NET实用技巧两则
使用LINQ来简化编程的7个技巧
VC.NET扩展Windows磁盘清理工具的功能
Asp.Net页面执行流程分析
用asp.net程序备份或还原SQLServer
ASP.NET实现页面间值传递的几种方法介绍
技巧实例:如何在.NET中访问MySQL数据库
asp.net中数据校验部分的封装与应用
ASP.NET中前台javascript与后台代码调用
翻译 一些很酷的.Net技巧
ASP.NET常用的26个优化性能方法
了解VB.NET中的常量与枚举功能
.NET FileStreams将DTD插入XML文件中
Windows CE.Net下矩阵键盘开发设计详解
.Net编程接口剖析系列之比较和排序
在.NET中字符串替换的五种方法

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


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