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

ASP.NET
ACCESS数据库访问组件(三)
ACCESS数据库访问组件(四)
在ASP.NET访问Excel文件
使用正则表达式解析的初步体会(固定格式网页解析)
一段找出URL的代码(C#)
C#中的转意字符序列
创建表,创建行,创建列(VB.NET)
刀兄写的IIS管理类(C#)
索引服务调用代码(C#)
VB.NET里奇怪的数组赋值现象
C#运算符的优先顺序
[初学VB.NET]如何防止重复打开MDI子窗体
第二版出错的地方,大家看看第三版我的翻译对么?
VB的API编程精粹
表格架构基本框架DEMO码
用C#实现在客户区拖动窗体(转自MSDN)
在ASP.NET中利用GDI+ 设计Chart控件
关于JAXP,DOM,SAX,JDOM,DOM4J的一些想法
Nucleus.MockAOP.Net:OpenSource .Net AOP FrameWork
VB中打印ACCESS报表

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


出处:互联网   整理: 软晨网(RuanChen.com)   发布: 2009-11-03   浏览: 89 ::
收藏到网摘: n/a


Rational Software belongs to a handful of companies whose products span the full spectrum of lifecycle tools—everything from requirements analysis to production testing. So who better to ask about the impact of .NET on enterprise application development than Rational founder and CEO Mike Devlin? Visual Studio Magazine Executive Editor Lee Th?recently chatted with Devlin about this and other topics of interest to the development community.
LT: Let's discuss the impact of Microsoft .NET on large-scale software development. What will be the most fundamental change for developers?
MD: Being able to focus on developing the application proper instead of having to spend so much time on infrastructure issues. If you talk with a lot of CIOs and development team managers today, you'd be amazed to find that 70 percent of development goes into infrastructure, while only 30 percent goes into building the business logic, application architecture, and application functionality. But the combination of the .NET platform and Visual Studio .NET reverses that by handling so many infrastructure issues automatically.

This continues the tradition of Visual Basic, which made it easy for a developer to access and build upon the relatively complex APIs of Windows. Now .NET takes that same model for developer productivity and applies it to a much broader distributed domain that includes servers, Web Services, and in fact the whole Web. The underlying complexity of this environment is even greater than that of the old Windows APIs. Fortunately, .NET hides some of that complexity from the user. It's not perfect, but it's a big step in that direction. You get a common platform, a common set of components, a common set of services accessing those components, and supporting distribution and access across the Web.
LT: You say "It's not perfect, but it's a big step." What are the gaps in .NET that development managers should look out for?
MD: The biggest warning concerns training—particularly hands-on training. Don't assume that just because you used VS6 you know it all. Visual Studio .NET and Microsoft .NET are powerful. To benefit from that, power developers must understand both the development environment and the runtime platform. Fortunately it's easy to get started with VS.NET, build a few small sample applications, use the tutorials, and thereby learn to leverage the power of the solution.