This project contains an ECO model and generated source code. Initially the model contains a single class with a single string attribute.
The model is edited in a separate application, EcoModeler. EcoModeler is launched by double-clicking on the .mmcseco file in the solution.
The actual use of the EcoModeler is described in C:\Program Files\CapableObjects\ECO\4.0\doc\pdf\EcoModeler.pdf.
When code is generated with Tools|Generate Eco Model in EcoModeler, the project file is automatically updated with the files added/removed.
The template contains the following files:
ReadMe.html | This file. |
Class_1.cs | The generated code for Class_1. One such file is created for each class in the model. The generated class has properties corresponding to the attributes and association ends in the model. |
GettingStartedWithEcoPackage.cs | Contains the class GettingStartedWithEcoPackage, which is used by ECO to know which classes are part of an Eco Package. |
GettingStartedWithEcoPackage.mmcseco | Contains the actual model in EcoModeler format. The name of this file does not matter, so if you wish you can rename it if you rename the package. | h
ModelInterfaces.cs | Contains the declarations of all modeled interfaces. |
ModelMergeData.ecoxml | Contains information used by EcoModeler when merging the changes into the existing classes after the model has been changed. Do not remove or rename this file. |
licenses.licx | licx file for including the ECO runtime license. |
It is also possible to start EcoModeler in other ways, e.g. from the start menu, or by double-clicking on a .mmcseco file in the windows explorer. It this case it will not be integrated into the Visual Studio IDE, and the project file will not be automatically updated. You can start the IDE integration manually by selecting "Tools"|"Start EcoModeler Integration" in the VS menu
It is best to name the package correctly in the wizard when creating it, but if you need to rename it later you need to perform the following steps: