Configuration Files

Skipper stores its configuration files in three different locations (application, user and project files location). Each type of configuration file is used in different situation and it is applied to achieve different result.

Configuration files priority

Skipper loads configuration files when new project is created or when saved project is loaded. Configuration files are loaded in a defined order:

  1. Application configuration files
  2. User configuration files
  3. Project configuration files

Important: Configuration files are searched for by their name. Valid configuration file looks like *.skipper.cfg.xml.

The load order has impact on how the settings are applied. Properties defined in the configuration file will be loaded and available to you in the visual model. If the property of the same name was already defined by previously loaded configuration file its value will be overwritten.

Configuration load order example

Note: Once a property is set up by loading the configuration file it cannot be deleted in a configuration file loaded later.

Application configuration files

Application configuration files are created on application installation. These configuration files contain setting for all supported ORM and MVC frameworks. The files are overwritten with new Skipper installation. File locations are based on platform as follows:

Mac OS





C:\Program Fiels\Skipper\Configurations

Note: Because files are overwritten during installation manual change of these files is not recommended as the changes may be easily lost.

User configuration files

User configuration files serve for customizing and extending Skipper configurations. It is possible to define new data types, new properties, new behaviors etc. Depending on the platform, files are stored as follows:

Mac OS

/Users/USER/Library/Application Support/Skipper/Configurations





Note: User configuration files are preserved during reinstallation.

Project configuration files

Each project can have its own configuration files. This is useful when your project uses some specific extension not usefull for the rest of your projects. Project configuration files can be located in the Skipper directory together with project or directly in the root of the project directory:


Note: {PROJECT_DIRECTORY} is location of the project file (file with .ormdesigner2 extension).

Warning: Project configuration files can only extend existing frameworks. It cannot be used to define new ones.

More configuration files in the same location

Skipper looks for the configuration files on the locations described above. Unlimited number of configuration files can be stored at each location and Skipper automatically identifies which files are valid configuration files. All configuration files at the same location will be merged prior to loading. This allows you to better organize your configuration files and extensions.

How to get your configuration location

Paths described above can be found in the Application Settings under the System Info tab.

Skipper configuration files location