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

ASP.NET
自定义控件(支持模板)
自定义控件(模板+数据绑定)
自定义控件(可以动态加载用户控件)
在代码隐藏中遍历当前页的所有控件
关于C#调用Office Web Components绘图的问题
利用Visual C#打造一个平滑的进度条
[VB] 防止程序运行多个实例
Visual Studio.Net 快捷键表
WinForm中ToolBar与TabControl的一些事件写法(C#)
【翻译】Managed DirectX(第六章)
利用.NET语言开发自己的脚本语言(一)
自动改变CheckBoxList选择项目的背景颜色
vb.net中windows服务的创建
BASE64编码规则及C#实现
.net中判断该应用程序是否已经启动,防止重复启动
XML Web Service 数据交换
开发花絮:一个DataList的ItemCommand事件意外
Snake.Net中的ORM(二)
ASP操作XML数据小结
可用来显示空值的时间选择控件4

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


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