🚀 Welcome to MDriven Learn –  MDriven is now on Discord!  Don’t miss the latest Release Notes.
Version Control and Team Collaboration
This page was created by Wikiadmin on 2026-07-29. Last edited by BSMaintenance on 2026-08-13.

Store shared models as .ecomdl[edit source]

MDriven Framework uses the .ecomdl format to save a model. This format is multi-file and uncompressed to facilitate use with diff tools and source-code repositories such as Git and SVN. This is particularly relevant when multiple developers change the model at the same time.

In MDriven Designer, save a model in this format by selecting FileSave as and choosing ecomdl (*.ecomdl).

The .ecomdl file structure can be opened in MDriven Designer, so teams can continue to use MDriven Designer together with MDriven Framework.

Use .ecomdl in a .NET MDriven project[edit source]

When creating a .NET MDriven project:

  1. Save the MDriven model as .ecomdl.
  2. Copy the .ecomdl model and its related files into the .NET project.
  3. If the project uses CodeDress, ensure that an Assets_TK folder exists at the same folder level as the .ecomdl file.
  4. Open the .ecomdl file in Visual Studio with the MDriven Framework extension and use Codegen to generate C# files for the classes in the model.

The project-creation documentation states that assemblies are uploaded to MDriven Server using the Assets_TK folder.

Reusable repository content[edit source]

MDriven maintains the MDrivenComponents GitHub repository. It contains sample models, mergeable models, and reusable components, including components for AngularJS and the Blazor client implementation.

See also[edit source]