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

ASP.NET
asp+文件上传增强实例
ASP.NET学习手记:验证用户表单输入
关于Microsoft.NET Beta1与Visual Studio.NET Alpha不兼容
asp+ 操作Cookie 方法大全
asp+ 现在已经被官方正式更名为 asp.net
在ASP+ 中我们如何使用 Class 而不是组件
asp+ 如何跨站抓取 页面
在 ASp+ 中的一些可能会用到的 小函数
列出asp+中所有request 的属性和数值
妙用asp+的global.asax
一个asp+ 版本的 Active Server Explorer
asp+中的session 的使用和原理() 不需要cookie也可以使用session
asp.net 的菜单制作(asp.net 的菜单application)
如何在asp+ 中使用自定义的pagelet
如何使用asp+ 动态创建页面元素
用DataGrid分页
给上次的DataGrid分页增加些功能!
asp+ 利用数据绑定来处理XML文件
两种没有使用绑定的 数据显示
asp+中的hash表操作

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


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