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

ASP.NET
用ASP.NET缓存提高站点性能
ASP.NET 中处理页面“回退”的方法
利用ASP.NET的三种缓存提高站点性能
Session丢失的解决办法小结
.Net中VSS实现版本控制管理的方法
ASP.NET中如何防范SQL注入式攻击
十天学会ASP.net之第三天
.NET Ajax的无刷新技术实例详解
剖析C# 2.0泛型类的创建和使用
解析在ASP.NET中调用存储过程的方法
在ASP.NET中使用AJAX的简单方法
DataGrid表头不动,表身动
结合JavaScript与ASP.NET Web窗体进行程序开发
asp.net里面的身份验证和授权
ASP.NET生成高质量缩略图通用函数(c#代码)
在C#中建立复杂的、灵活的SQL查询/命令
基于C#的接口基础教程之一
基于C#的接口基础教程之二
基于C#的接口基础教程之三
基于C#的接口基础教程之四

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


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


LT: For the uninitiated, what抯 the relationship or difference between the .NET framework and pattern mechanisms? For someone used to working on a more granular level, where should they start to master this approach?
MD: Pattern mechanism is a tool (an add-in) that supports model-to-model transformations specified in the form of a pattern with additional transformation semantics. In other words, you define a pattern in such a way, that it can be applied to a model and that will perform model transforms.
A .NET framework is preconfigured solution (where a solution is an integrated set of .NET language projects). The preconfiguration includes (this might be an incomplete list):Some initial content in the language projects. Customization of and constraints on the VS development environment (for example, you can disable some operations on a project, change menus, and so on). Customization and extension to the dynamic help system.

In our RDA Online Retail Kit (Rational Development Accelerator Kit), we are using both. We have created an EFT for our framework and we have created a set of patterns for customizing and extending the framework.
LT: I've been seeing texts about patterns for years. How does .NET make pattern-based architectures more doable?
MD: The key is if this is all separate from runtime environment and the implementation tools, it will be hard to do. Architectures can't be abstract patterns only analysts do. They must be real live artifacts that developers can connect directly to implementation artifacts such as Visual Studio .NET. It's also easier to generate testing from such models, because the models and the code can be much more tightly coupled, as ours are.
So it allows us to make the models more valuable. You can generate test cases, allow for model-driven development, and even debug at the model level later on. It makes the models more live—more tightly coupled with the implementation artifacts—and lets the developer view the model as a different way to interact with the application.