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

ASP.NET
ASP.net Menu控件在Google Chrome和Safari浏览器下显示错位的解决办法
最简单的.NET生成随机数函数
asp.net 相关文章实现方法
asp.net 分页潜谈
asp.net(C#) Access 数据操作类
asp.net 编程 实用语句(6条)
ASP.NET 小技巧(2个)
asp.net Excel转换为SQL Server的方法
asp.net String.Empty NULL 不同之处
asp.net 防止SQL注入攻击
aspx 页面弹出窗口代码大全
asp.net 点击按钮提交后使按钮变灰不可用
asp.net得到本地电脑基本信息的简单方法
asp.net 点缩略图弹出随图片大小自动调整的页面
asp.net treeview checkbox 相关问题
asp.net 特定目录form验证
C# CUR类实现代码
asp.net gridview中用checkbox全选的几种实现的区别
asp.net 文件下载的通用方法
解决AJAX.NET中的悬停panel在页面加载时闪烁的问题

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


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