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

ASP.NET
浅析.NET 3.5 SP1中的JIT增强
在ASP.Net中实现RSA加密
浅析ASP.NET中C++和J#的混合应用
探讨ASP.NET MVC框架内置AJAX支持编程技术
Web开发模式的颠覆者:ASP.NET MVC
设计ASP.NET应用程序的七大绝招
浅谈Asp.net多层架构中的变量引用与传递
ASP.NET遍历配置文件的连接字符串
ASP.NET2.0中配置文件的加密与解密
Ja.Net:融合 Java 1.5 和 .NET
ASP.NET 2.0 中XML数据的处理
ASP.NET中备份SQL Server数据库的方法
asp.net/c#字符格式化
在.NET应用程序中进行Erlang风格的并行编程
Flex与.NET互操作:基于WebService的数据访问
asp.net 里 include UTF8 垃圾问题
让.Net程序脱离.Net Framework框架运行
.NET上执行多线程应该注意的两点
ASP.NET应该遵守的9条代码编写规范
.Net和Java的socket机制比较

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


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