ConfigurationSetup.cfg being changed

My testing is with OpenRoads Designer 10.08.01.33 (2020 Release 2 Update 8) but I believe this is more a MicroStation Connect issue (I have not tested in MicroStation Connect).

default ConfigurationSetup.cfg as below:

[General]
_USTN_CUSTOM_CONFIGURATION=C:/ProgramData/Bentley/OpenRoads Designer CE/Configuration/

[SetConfiguration]
%if !defined (_USTN_USER_CONFIGURATION)
%if defined (_USTN_CUSTOM_CONFIGURATION) && ($(_USTN_CUSTOM_CONFIGURATION) != "") && exists ($(_USTN_CUSTOM_CONFIGURATION))
_USTN_CONFIGURATION = $(_USTN_CUSTOM_CONFIGURATION)
%endif
%endif

Open a file with one of the installed workspace/workset.

Now change _USTN_CUSTOM_CONFIGURATION (I changed to C:/CADDLib/Connect/ which is an internal location for us)

Open ORD again, when the backstage workspace/workset selector is open check ConfigurationSetup.cfg and (if you have the same problem as us) you'll see the line _USTN_CONFIGURATION has been hard-coded to the _USTN_CUSTOM_CONFIGURATION.

[General]
_USTN_CUSTOM_CONFIGURATION=C:/CADDLib/Connect/

[SetConfiguration]
%if !defined (_USTN_USER_CONFIGURATION)
%if defined (_USTN_CUSTOM_CONFIGURATION) && ($(_USTN_CUSTOM_CONFIGURATION) != "") && exists ($(_USTN_CUSTOM_CONFIGURATION))
_USTN_CONFIGURATION = C:/CADDLib/Connect/
%endif
%endif

I can also trigger this by setting _USTN_CONFIGURATION in a different file (for example WorkspaceSetup.cfg), i admit this would be a kind of dumb thing to do but it does trigger it.

Important part seems to be you have to open a file using the one _USTN_CONFIGURATION, then exit, modify _USTN_CONFIGURATION and open ORD again. At that point the _USTN_CONFIGURATION is re-rewritten. If at this point you change _USTN_CONFIGURATION back to _USTN_CONFIGURATION = $(_USTN_CUSTOM_CONFIGURATION) it won't be changed again until you change _USTN_CUSTOM_CONFIGURATION in ConfigurationSetup.cfg (or _USTN_CONFIGURATION in a different cfg file)

This is kind of killing me at the moment because we actually need to change the _USTN_CUSTOM_CONFIGURATION for a particular client and flipping back and forth is going to be necessary. My normal ConfigurationSetup.cfg has logic for detecting this and setting the correct one, but when it does the value is then hard-coded into the configurationSetup.cfg.

Parents
  • I've had problems with the _USTN_CUSTOM_CONFIGURATION variable too.

    To get around this I set the value of _USTN_CUSTOM_CONFIGURATION as needed in a different config file that gets loaded prior to the loading of ConfigurationSetup.cfg. After defining the variable I lock it so it can't be changed. 

    Have you tried moving the logic you have in the ConfigurationSetup.cfg to a custom config file that loads earlier in the startup process?

Reply
  • I've had problems with the _USTN_CUSTOM_CONFIGURATION variable too.

    To get around this I set the value of _USTN_CUSTOM_CONFIGURATION as needed in a different config file that gets loaded prior to the loading of ConfigurationSetup.cfg. After defining the variable I lock it so it can't be changed. 

    Have you tried moving the logic you have in the ConfigurationSetup.cfg to a custom config file that loads earlier in the startup process?

Children