(Automatically adding template at the end of the page.) |
Hans Karlsen (talk | contribs) No edit summary |
||
Line 1: | Line 1: | ||
ECO is the | ECO is short for EnterpriseCoreObjects and is the old name we used for the MDriven-technology. The ECO name was shared with Borlands/Codegears product named ECO that was a similar product targeting the Delphi development environment. Codegear discontinued their ECO-product when they switched focus to native development and no .net. | ||
MDriven has never targeted the Delphi development environment - we have always targeted Visual Studio (MDrivenFramework) and stand alone modelling (MDrivenDesigner) | |||
MDriven has honored the API and general constructs of Codegears ECO - and MDriven is a good transition path for any one wanting to stay model driven in a .net environment going forward. | |||
MDriven has no affiliation or ties to Codegear. | |||
[[Category:ECO]] | [[Category:ECO]] | ||
{{Edited|July|12|2024}} | {{Edited|July|12|2024}} |
Revision as of 18:42, 17 February 2024
ECO is short for EnterpriseCoreObjects and is the old name we used for the MDriven-technology. The ECO name was shared with Borlands/Codegears product named ECO that was a similar product targeting the Delphi development environment. Codegear discontinued their ECO-product when they switched focus to native development and no .net.
MDriven has never targeted the Delphi development environment - we have always targeted Visual Studio (MDrivenFramework) and stand alone modelling (MDrivenDesigner)
MDriven has honored the API and general constructs of Codegears ECO - and MDriven is a good transition path for any one wanting to stay model driven in a .net environment going forward.
MDriven has no affiliation or ties to Codegear.