This project contains the definition of the actual EcoSpace class, and its persistence. An EcoSpace acts as a container for ECO Objects. The classes of objects that a particular EcoSpace can contain are defined in a model consisting of one or more ECO packages. This EcoSpace initally uses the package PluginRoseFileRead.
This project contains the following files:
| ReadMe.html | This file. |
| PluginRoseFileReadEcoSpace.cs | The actual EcoSpace class. |
| PluginRoseFileReadPMP.cs | The PersistenceMapper Provider for the EcoSpace. |
| licenses.licx | licx file for including the ECO runtime license. |
There a number of tools at the bottom of the designer for the EcoSpace, where the most important are:
The package selector works by reflecting over the referenced assemblies, so everything must current and compiled for the designer to pick it up correctly.
The other tools are related to persistence, and should be considered as obsolete. All persistence operations are now performed on the PersistenceMapper provider.
Persistence for the EcoSpace is configured with the designer for the PersistenceMapperProvider. A suitable PersistenceMapper component is placed on the designer, and connected to the PersistenceMapper property. In most cases a database connection component, e.g. a SqlConnection, is also needed. The connection component is configured to connect to the database to be used. If xml persistence is used, there is no need for a connection component. The name of the file is set directly on the PersistenceMapperXml component. There a number of tools at the bottom of the designer, where the most important are: