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

ASP.NET
谈谈ASP.net2.0中App_GlobalResources的用途
.Net Framework 4.0 功能介绍
ASP.NET教程:浅谈Asp.net实现的邮件发送引擎
ASP.NET教程:绝对路径与相对路径的拼合方法
ASP.NET开发电子商务网站学习经验
ASP.NET与PHP构建web程序的方法的优缺点
ASp.NET教程:页面传值的五种方法
ASP.NET教程:数据缓存和输出缓存
ASP.NET比拼PHP的测试环境
ASP.NET MVC 2的客户端验证扩展
ASP.NET实例:无刷新的文件上传
ASP.NET实例: GridView删除时弹出确认对话框
ASP.NET获取不到js写的cookie解决方法
ASP.NET MVC教程:数据库表的增删改
ASP.NET教程:form验证用户登录的Cookie
如何让.NET程序脱离.NET框架
ASP.NET开发网站程序常见错误汇总
C#教程:匿名类型和隐式类型变量的区别
C#3.0教程:自动属性和扩展方法
使用XmlDocument读取XML节点所有数据

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


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