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

ASP.NET
asp.net 无重复随机数代码
asp.net(C#)中上传大文件的几中常见应用方法
asp.net AJAX实现无刷新获得数据
C#中发送邮件代码
asp.net(c#) RSS功能实现代码
asp.net窗体操作总结
ASP.NET 水晶报表打印功能实现代码
ASP.Net 图片存入数据库的实现代码
让Silverlight 2.0动画动起来Making Silverlight 2.0 animation Start(不能运动原因)
asp.net Reporting Service在Web Application中的应用
C# 文件上传 默认最大为4M的解决方法
asp.net 购物车实现详细代码
asp.net repeater实现批量删除时注册多选框id到客户端
asp.net aspnetpager分页统计时与实际不符的解决办法
iis 服务器应用程序不可用的解决方法
asp.net button 绑定多个参数
asp.net Ajax 安装与卸载方法
Ajax Throws Sys.WebForms.PageRequestManagerErrorException with Response.Redirect的解决方法
asp.net 两个不同页面的传值
C# 可空类型分析

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


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