Why does MS23 default to Example Workspace/Workset?

Any one?

Hi Stuart,

I don't have an answer to your question, but I may have a work-around. 

Open the file "C:\Users\User Name\AppData\Local\Bentley\MicroStation\23.0.0\prefs\configuration.xml" with Notepad (or equal).  (Replace "User Name" with your Windows user name.)

In there you will find different sections marked by "<ConfigurationModel>".  About five lines below each "<ConfigurationModel>" you will find "<IsActive>value</IsActive>" where the "value" is true or false.  On the ConfigurationModel you want to use, set this value to "true" and on the other ConfigurationModel's, set this value to "false".

--Robert

Hi Stuart,

As we have previously discussed, MicroStation is designed to work with at least one WorkSpace and WorkSet.

To ensure that MicroStation is installed and fully operational out of the box we deliver the examples WorkSpace/WorkSet.

This is included by default in the Manage Configuration Utility, again so it works out of the box.

Use of the Manage Configuration Utility, whose content is populated by "C:\Users\User Name\AppData\Local\Bentley\MicroStation\23.0.0\prefs\configuration.xml" does not really make sense without at least one WorkSpace/WorkSet.

I have not investigated how operating only with No WorkSpace/No WorkSet can be set up in MicroStation 2023 because it is not an appropriate approach and just makes configuration more difficult than it needs to be.

In MicroStation 2023 you can set a new variable to point to a folder containing a shared configuration.xml that in a single WorkSet scenario need only contain one configuration. e.g. :

MS_CONFIGURATIONXML_PATH = D:/_CONFIG_XML/

A configuration can be set up that uses the WorkSpace/WorkSet to store configuration and points to a data storage location without impacting the data structure, this could be relevant to your situation.

Marc,

Thanks for your response but things have moved on since I posted this. I have had to set _USTN_USER_CONFIGURATION in my configurationsetup.cfg because _USTN_CUSTOM_CONFIGURATION is not working as it does with the CONNECT version. I posted this on another thread and am speaking to Support about about why  _USTN_CUSTOM_CONFIGURATION and my customised 'standards.cfg' are not being processed. As part of this I now do see the Examples Workspace/Workset when staring MS2023. I also don't have a Manage Configuration Utility.

Marc Thomas said:

have not investigated how operating only with No WorkSpace/No WorkSet can be set up in MicroStation 2023 because it is not an appropriate approach and just makes configuration more difficult than it needs to be

Noted but why isn't it an appropriate approach. We don't use Workspaces/Worksets as they don't fit our workflow, but No Workspace/Workset does. Wed are not going to start using Workspaces/Worksets now, after all this time. 

Marc Thomas said:

In MicroStation 2023 you can set a new variable to point to a folder containing a shared configuration.xml that in a single WorkSet scenario need only contain one configuration. e.g. :

MS_CONFIGURATIONXML_PATH = D:/_CONFIG_XML/

A configuration can be set up that uses the WorkSpace/WorkSet to store configuration and points to a data storage location without impacting the data structure, this could be relevant to your situation.

I have read what you have written but don't understand what you are saying. What is configuratuion.xml as pretty sure that we don't use it. 

All we need to know is that our custom configuration & 'standards.cfg' are being used. Works fine with U17 so why not in 2023?

This is my configuration, which works well...

In Microstation CE Update 17, the configuration.xml file came into play to get the list to appear correctly and to get the defaults to work properly.

--Robert