When creating a Named Configuration, the process should store the named configurations Setting (Name, Description, etc). Then retrieve the Name, Description, etc when connecting to the named configuration. If the information doesn't exist, then the user can enter it manually, but in this case the user should be create it not connecting to it. The list of connected configurations would still be stored in the configuration.xml as it does now. Since the Named Configuration is branded to the DGN file its name needs to be consistent. This would provide consistency a crossed users connecting to a common Named Configuration that is stored locally or on a network. Also, since the Configuration Name is available as a field and also branded into the DGN it is import to always be the same.