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

ASP.NET
ASP.NET立即上手教程(13)
ASP.NET立即上手教程(14)
Repeater控件分页例子
从文本文件读取行信息
Asp.Net 2.0数据库基本操作方法学习
url传递中文的解决方案
如何实现无刷新的DropdownList联动效果
将非模态对话框显示为模态对话框
微软新版开发工具VS 2008 beta2功能定案
c#.net函数列表
.Net FW中无法正确显示中文问题
ASP.NET中的doPostBack脚本函数实例
教你在asp.net中动态变更CSS
一个功能齐全的DataGrid分页例子
在ASP.NET程序中创建唯一序号
asp.net 2.0中用GRIDVIEW插入新记录
ASP.Net中保护自定义的服务器控件
在ASP.NET中跨页面实现多选
转换DataSet到普通xml的新法
ASP.NET中用healthMonitor属性用法

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


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