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

ASP.NET
AspNetPager与Socut.Data使用实例代码
asp.net JavaScript插件 JavaScript Function Outliner
asp.net for循环语句
asp.net access添加返回自递增id的实现方法
asp.net SAF 中缓存服务的实现
asp.net小孔子cms中的数据添加修改
asp.net自定义控件代码学习笔记
用javascript css实现GridView行背景色交替、鼠标划过行变色,点击行变色选中
.net三层结构初探分析
asp.net+js实时奥运金牌榜代码
asp.net SqlHelper数据访问层的使用
asp.net中利用ashx实现图片防盗链的原理分析
asp.net 2.0多语言网站解决方法
Ajax.net Sys未定义错误解决办法
.dll 文件反编译的工具软件集合
asp.net gridview 72般绝技
常用的在数据库中建立无限级树形菜单的asp.net代码
asp.net生成静态页并分页+ubb
Asp.net 通用万级数据分页代码[修正下载地址]
较为全面的Asp.net提交验证方案分析 (上)

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


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