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

ASP.NET
也说C#实现对Word文件读写
字符串处理:中英文混排固定长度截取问题
用asp.net还原与恢复sqlserver数据库
C#加密路径里的参数,保护参数隐私安全!
ASP.NET实现网络空间管理
Asp.net中处理共享Session的问题
ASP.NET之精通弹出窗口
禁止在TextBox中输入
将一个图片以二进制值的形式存入Xml文件中
vs.net 2003在FAT32格式的系统中安装
.Net FrameWork SDK文档的例子演示
改善C#中socket通信机客户端程序的健壮性
C#中的域(field)和属性(property)
将ASP.net中的Table中的数据导入到Execl
C#中的数组和C++中数组的区别
C#中的checked、unchecked操作符
asp.net 的 Request对象
C#中方法参数的四种类型
C#中的“装箱”与“拆箱”
C#中的代理(delegate)

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


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