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

ASP.NET
asp.net Linq To Xml上手Descendants、Elements遍历节点
asp.net 过滤图片标签的正则
ASP.NET Session会导致的性能问题
asp.net 客户端浏览器缓存的Http头介绍
ASP.NET 常用 文件上传方法
异步 HttpContext.Current实现取值的方法(解决异步Application,Session,Cache...等失效的问题)
asp.net Datalist控件实现分页功能
c#中带头(声明)的xml(封装)生成
asp.net BOF或EOF有一个是真,或者当前记录已被删除
asp.net 多数据库支持的思考
一个简单的自定义程序日志小样例
asp.net DataSet进行排序
常用JavaScript代码提示公共类封装
ASP.NET 服务器路径和一般资源调用
使用母版页时内容页如何使用css和javascript
asp.net datalist 用法
asp.net js模拟Button点击事件
ASP.NET Web Page应用深入探讨
动态向页面添加控件和使用正则表达式的代码
Asp.net 连接MySQL的实现代码[]

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


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