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

ASP.NET
如何用Response.Redirect方法传递汉字
在ASP.NET中调用存储过程方法新解
决定何时使用 DataGrid、DataList 或 Repeater(ASP.NET 技术文章)
AlternatingItemTemplate类似于 ItemTemplate 元素
c#中过滤html的正则表达式
ASP.NET:ADO.NET的DataAdapter对象
repeater分页 内容显示
内容添加asp.net
VS2003 SP1发布
DataReader深入解析:持续更新
C#.Net 学习笔记(一)
从ASP过渡到ASP.net遗留的二十大积习
如何改变asp.net项目名称
asp,asp.net学习教程下载
基于.net开发的遵循web标准的个人站点程序包下载
FileUpload1 上传文件类型验证正则表达式
ASP.NET与数据库相关技巧
读取TXT文件内容的方法
简单的启动窗体
c#中实现文件拖放打开的方法

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


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