ECO
(Created page with "ECO is really a rule engine that given a UML model and a Persistence Mapper will help any .net runtime to handle the objects of that model in memory. ECO will via the Persiste...")
 
No edit summary
Line 1: Line 1:
ECO is really a rule engine that given a UML model and a Persistence Mapper will help any .net runtime to handle the objects of that model in memory. ECO will via the Persistence Mapper help to dehydrate or hydrate objects from a persistent storage, ie a database.
ECO is the core engine for all MDriven applications.
 
It's the engine that given a UML model and a Persistence Mapper will help any .net application to handle the objects of that model in memory. ECO will via the Persistence Mapper help to dehydrate or hydrate objects from a persistent storage, ie a database.
 
ECO is also the name of a Visual Studio Plugin that brings ECO, Modlr, Derived Code, Derived DB scripts and Database Evolution to Visual Studio.
ECO is also the name of a Visual Studio Plugin that brings ECO, Modlr, Derived Code, Derived DB scripts and Database Evolution to Visual Studio.
ECO is UI-agnostic – it does, however, contain parts that help with asynchronous access to persistence storage (good for WPF and a must for Silverlight), it contain parts for serializing a complete object graph into a cache (very useful for ASP.NET and MVC), also it contain parts that make it easy to bring objects from the model to a format that makes it easy to data bind to WindowsForms, WPF, Silverlight, ASP.NET and ASP MVC.
ECO is UI-agnostic – it does, however, contain parts that help with asynchronous access to persistence storage (good for WPF and a must for Silverlight), it contain parts for serializing a complete object graph into a cache (very useful for ASP.NET and MVC), also it contain parts that make it easy to bring objects from the model to a format that makes it easy to data bind to WindowsForms, WPF, Silverlight, ASP.NET and ASP MVC.

Revision as of 14:05, 25 May 2017

ECO is the core engine for all MDriven applications.

It's the engine that given a UML model and a Persistence Mapper will help any .net application to handle the objects of that model in memory. ECO will via the Persistence Mapper help to dehydrate or hydrate objects from a persistent storage, ie a database.

ECO is also the name of a Visual Studio Plugin that brings ECO, Modlr, Derived Code, Derived DB scripts and Database Evolution to Visual Studio.

ECO is UI-agnostic – it does, however, contain parts that help with asynchronous access to persistence storage (good for WPF and a must for Silverlight), it contain parts for serializing a complete object graph into a cache (very useful for ASP.NET and MVC), also it contain parts that make it easy to bring objects from the model to a format that makes it easy to data bind to WindowsForms, WPF, Silverlight, ASP.NET and ASP MVC.

This page was edited 80 days ago on 02/09/2024. What links here