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

ASP.NET
asp.net neatUpload 支持大文件上传组件
ASP.net 动态加载控件时一些问题的总结
web用户控件调用.aspx页面里的方法
asp.net 继承自Page实现统一页面验证与错误处理
asp.net 文件下载实现代码
asp.net ToString()格式设置大全
.NET 水晶报表使用代码
c# NameValueCollection类读取配置信息
asp.net 不用组件的URL重写(适用于较大型项目)
.aspx中的命名空间设置实现代码
asp.net access web.config denied
JAVA正则表达式 Pattern和Matcher
asp.net 每天定点执行任务
asp.net fileupload 实现上传
asp.net slickupload 使用方法(文件上传)
asp.net 从客户端中检测到有潜在危险的 Request.Form 值错误解
关于asp.net button按钮的OnClick和OnClientClick事件
asp.net 权限管理分析
c# table 控件用法
asp.net repeater手写分页实例代码

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


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