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

ASP.NET
8月编程语言榜:.Net前景如何?
.NET调PHP Web Service的典型例子
ASP.NET热点问题解答14个
ADO.NET实用技巧两则
ASP遗留的二十大积习
从零开始学ASP.NET-基础篇
asp.net WebForm页面间传值方法
一个经典的ADO.NET入门例子
ASP.net中md5加密码的方法
C#Web应用程序入门经典学习笔记之二
程序中常用的种代码
页面包含的处理
几个C#常用正则表达式的总结
c#对xml的简单操作
获取当前url
检测含有中文字符串的实际长度
ASP.NET 数据访问类
利用Ajax传递Xml文档
给.net初学者的一些建议(共勉之)
asp.net网络数据库开发实例精解 源文件

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


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