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

ASP.NET
ASP.Net中Session失效的一种编程思路
VS2003创建和打开ASP.net 工程的若干问题
用VS.NET打开或创建web项目出错的解决办法
Windows2003中配置ASP.net动态网站运行环境
Web.config中注册用户控件和自定义控件
ASP.NET AJAX 控件中HTML Intellisense功能的丢失
ASP.NET程序防范SQL注入式攻击的方法
Request.Form中的一些特殊的东西
ASP.NET最常见错误提示
VS2005构建针对DB2的应用程序和Web站点
ASP.NET 2.0控件处理DB2 9应用程序之二
Sandcastle介绍:生成.NET API文档的工具
教程:Asp.net与Xml开发网络硬盘技术
.NET事件处理的步骤
SVN配置和apache的配置
.NET命名空间和目录划分的经验
.NET开发时使用正则表达式的BUG
各版本IIS下ASP.net请求处理过程
ASP.NET MVC实现自己的一个视图引擎
C#关键字

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


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