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

ASP.NET
asp.net 控件验证 FCKeditor
asp.net Repeater 自增
asp.net 安全、实用、简单的大容量存储过程分页
asp.net 编译器错误信息: CS0006: 未能找到元数据文件 该死的.NET
asp.net url 伪静态设置方法
C# 没有动态的数组,可以用arraylist或list取代
c# static 静态数据成员
ASP.NET 字符串截取
Discuz!nt 源文件变成乱码的解决方法
Javascript C#真正可以交互的DES加解密代码
asp.net 数组中字符串替换的几种方式
ASP.NET 生成静态页面 实现思路
在asp.net(C#)中采用自定义标签和XML、XSL显示数据
ASP.NET(C#)应用程序配置文件app.config/web.config的增、删、改操作
ASP.NET MVC引入JQUERY JQRTE控件
C# Base64编码
discuz 跨域整合的记录文件
SQL注入中绕过 单引号 限制继续注入
.net清空所有Cache的实现代码
discuz nt的退出实现代码

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


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