LT: for the uninitiated, what 抯 THE RELATIONSHIP or Difference Between The .NET FRMEWORK AND PATTERN MECHANIS? For Some Used to Working on a More Granular Level, Where 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 include (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 not 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 CON BE MUCH More Tightly Coupled, AS Ors Are.
