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

ASP.NET
.net开发绑定到LINQ查询的结果实例
vc.net中配置OpenOffice的SDK应用开发
用.NET读取 Flash格式文件信息
点缩略图弹出随图片大小自动调整的页面
关于VS 2008和.NET 3.5 Beta2新特性介绍
网友分享:详细解读.NET中的代码动态编译
基于.NET Framework 微软Silverlight下载
Asp.net多层架构中的变量引用与传递
VS2008中查看.NET源码的设置方法
Asp.net中如何过滤html,js,css代码
ASP.NET 2.0中CSS失效解决方案
使用ADO.NET2.0提升数据交互性能(1)
使用ADO.NET2.0提升数据交互性能(2)
使用ADO.NET2.0提升数据交互性能(3)
使用ADO.NET2.0提升数据交互性能(4)
使用ADO.NET2.0提升数据交互性能(5)
解决CSV字段数据带有双引号的问题
VB.net实现sql数据库的备份与恢复
Asp.net FMS 开发视频网站
.Net平台下开发中文语音应用程序

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


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