Why does the C:\ProgramData\Bentley\MicroStation CONNECT Edition\Configuration\WorkSpaces\NoWorkSpace\NoWorkSet.cfg file clear out the any previous Macro and VBA definitions?
#----------------------------------------------------------------------# Set the macro creation and search paths.#----------------------------------------------------------------------MS_MACRONEWFILEDIRECTORY = $(_USTN_WORKSETROOT)MS_MACRO = $(_USTN_WORKSETROOT)MS_VBANEWPROJECTDIRECTORY = $(_USTN_WORKSETROOT)MS_VBASEARCHDIRECTORIES = $(_USTN_WORKSETROOT)
At the application level I've added a .cfg file that defines the location of custom macro files setting the MS_MACRO and MS_VBASEARCHDIRECTORIES variables. If someone selects the NoWorkSpace option the above config file blows that away.
Shouldn't those variable definitions NoWorkSet.cfg file use the < or > operators instead?
The workaround is easy enough...
%level roleMS_VBASEARCHDIRECTORIES > $(ENVISIONCAD_FREEWARE_STANDARDS)vba/%level application
Set the variable to be defined at the Role level so that it is updated after the NoWorkSet.cfg resets the definition.
However, this shouldn't be necessary.
Rod WingSenior Systems Analyst