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

ASP.NET
基于C#的接口基础教程之五
基于C#的接口基础教程之六
ASP.NET中数据库的操作初步----增加、删除、修改
从Internet上抓取指定URL的源码的方案(C#)
对C#中正则表达式的一些解读和总结
简述c#中对字符串进行分割的几种方法
ASP.NET中的事务处理和异常处理
用ASP.NET/C#连接Access和SQL Server数据库
ASP.NET 2.0中层次数据的处理
ASP.NET 2.0服务器控件之客户端功能
asp.net2.0 URL重写以及urlMappings问题(1)
asp.net2.0 URL重写以及urlMappings问题(2)
再议ASP.NET DataGrid控件中的“添加新行”功能
建立个人知识引擎的重要性
解析.Net框架下的XML编程技术
ASP.NET--制作功能完善的安装程序
Asp.net直接保存文件到客户端
.Net中消除Dll中的dependency
ASP.NET页面事件:顺序与回传详解
在ASP.NET+ORACLE添加数据记录并让ID自动增量

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


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