No Workspace/No Workset uses last workspace name and won't allow browsing

Question

When I attempt to use No Workspace (Client) -> No Workset Browse uses the previous Workspace name to look for a folder No Workset\DGN. 
 This results in an error and does not allow browsing for files using No Workspace -> No Workset

Marc Thomas · Accepted Answer

Take a look at (but DON'T change) msconfig.cfg, try a search in the text for "nowork" just to find the right area... 
 Lines 301 to 306 define the place where NoWorkSpace/NoWorkSet.cfg lives. 
 In my test setup with drives P (= project data: WorkSpaces/Worksets) and W (= resources: Organization) I can reproduce the information message (note this is not an error message, it speaks the truth, MicroStation is looking for a file and it is not there!) by deleting the copy of NoWorkSpace/NoWorkSet.cfg I put there as described in Solution 1 below. 
 I offer two solutions: 
 Solution 1 
 The easiest: Copy NoWorkSpace/NoWorkSet.cfg to the place it's looking. 
 Solution 2 
 No one likes untidy folders so in C:\ProgramData\Bentley\CONNECT Edition\Configuration\WorkSpaceSetup.cfg which is where I assume redirection to your equivalents of P and W is being done add a variation of the if loop contained in msconfig.cfg, change the two instances of the variable _USTN_WORKSPACESROOT to _USTN_ORGANIZATION where indicated: 
 In my case this is: 
 # To hide the NoWorkSpace folder from the users 
 %if !defined (_USTN_WORKSETCFG) && exists ($( _USTN_ORGANIZATION )NoWorkSpace/NoWorkSet.cfg) 
 _USTN_WORKSETCFG = $( _USTN_ORGANIZATION )NoWorkSpace/NoWorkSet.cfg 
 _USTN_HAVEWORKSET = 0 
 %else 
 _USTN_HAVEWORKSET = 1 
 %endif 
 Where I have already defined: 
 _USTN_ORGANIZATION = W:\MstnCONNECT\Organization\ 
 Copy NoWorkSpace/NoWorkSet.cfg to the matching location 
 
 This can be anywhere you like (on your LAN!) as long as the location and the if statement match. You could change the folder name but if it is out of sight why bother, that will only obscure its purpose.

Marc Thomas · Answer

As long as this tiny configuration file is in the expected place (or configured to be hidden away, if the presence of the 'NoWorkSpace' folder is unacceptable) the informative message will never be seen, so yes you can just fire it up and get on with it. If you don't want to engage with the Workset features that's fine. 
 Looking again at the content of C:\ProgramData\Bentley\CONNECT Edition\Configuration\WorkSpaces\NoWorkSpace\NoWorkSet.cfg it says at the top: 
 # Configuration File used for opening stand-alone DGN files that don't 
 # belong to a WorkSet. 
 # Set search paths to 'My Documents' 
 That is what this file is designed to do. 
 Why is it using 'My Documents'? Because that folder is always present so we know it will be found. We deliver a working testable configuration that is then amenable to change. 
 For anyone that does not want the search paths for No Workset to point to 'My Documents', the usefulness of the NoWorkSet.cfg file turns out to be that the network/standalone/'NAS box' copy of NoWorkSet.cfg can be edited to point to the desired location, e.g: 
 %if exists ( C:/MySketches/ ) _USTN_WORKSETROOT = C:/MySketches/ %else _USTN_WORKSETROOT = $(HOMEDRIVE)$(HOMEPATH)/ %endif 
 So quite handy really.

Marc Thomas · Answer

I searched MicroStation CONNECT help for "Workset". The second result down, "Including Files in the Active WorkSet" also tells us how to disassociate with a key-in, scroll down to the end of the page.