You can restore readable filenames for generated .spans and .ecodiag files when working with a model in source control by changing the PreserveLegacyFilenames setting in modlr.config.

Symptoms

When you prepare a commit, you may find that .spans and .ecodiag files have GUID-based names instead of the readable names you previously used.

This behavior is controlled by the old PreserveLegacyFilenames setting in the model's modlr.config file. It can be enabled when someone answers Yes to the prompt to preserve legacy filenames during a save.

Restore readable filenames

1. Locate the modlr.config file for the model.
2. Open modlr.config in a text editor.
3. Find the PreserveLegacyFilenames setting.
4. Clear its value, or set its value to false.
5. Save modlr.config.
6. Save the model again and review the generated .spans and .ecodiag filenames before committing.

For example, if the setting has been enabled, change it so that its value is empty or false. After the next model save, verify that the generated filenames are readable again.

Is this expected?

Yes. GUID-based filenames in this situation are the result of the PreserveLegacyFilenames setting, not an indication that your repository has failed or that the files are corrupted.

If the setting is not present, or changing it does not restore the expected naming, check the effective modlr.config used by the model before making broad source-control changes.

Scope

This setting concerns the filenames of generated .spans and .ecodiag files. It is unrelated to blob storage filenames. For example, external blob storage can use filenames in the form Class.Attribute.Guid.blob by design.

See also

• Documentation:Working with Code and Persistence Mapping
• Documentation:BlobStorage
• Documentation:MDriven Designer–a new Rename function to save you time