Workspace/workset set-up

Hello

I have converted our old workspace to the new format for CE and have used the text below in the desktop shortcut shortcut to bring in the workspace when MicroStation (or Descartes or View) is opened;

 -wrZ:\Config\ -wkEMP -ww"Networks Eng" where Z:\ is the network drive where the configuration is stored.

It all works fine when you open a file from within the app but how do I ensure that the workspace comes in with a design file when it's double-clicked directly? Is there a way to add the workspace configuration at  installation so that its always there, no matter how a file is opened? We don't have separate workspaces for different projects or clients, just the one to cover everything and we're running Update 16.

I have created deployment images for the three apps and included the path to the configuration in the layout setup but it doesn't seem to bring the workspace with it automatically on a new installation. Am I missing something here?

Thanks

Paolo

Parents
  • Thanks to Shawn for linking the Command Line blog. In this case they won't help as Windows file association cannot be directed to use the command line switches.

    However as you only have one WorkSpace and WorkSet you can lock the applications to that combination.

    I suggest adding the following to ConfigurationSetup.cfg on each user's machine for each application, replacing any existing _USTN_CUSTOM_CONFIGURATION statements:

    [General]

    _USTN_USER_CONFIGURATION_LABEL = MyCompany Projects
    _USTN_USER_CONFIGURATION = Z:/Config/

    this is described in:

    CONNECT Edition - Configuration Tips: What does _USTN_USER_CONFIGURATION do?

    Then in Z:/Config/WorkSpaceSetup.cfg add:

    _USTN_WORKSPACENAME = EMP

    %lock _USTN_WORKSPACENAME

    _USTN_WORKSETNAME = Networks Eng

    %lock _USTN_WORKSETNAME

    I'd suggest adding an underscore to the WorkSet name, it's always best to avoid spaces in names.

    ConfigurationSetup.cfg can be distributed using a system policy or just a batch file that users can run to copy and replace if IT can't help immediately.

    Note that use of only one WorkSet does limit the functionality of some WorkSet based features, sheet indexing for instance, but I suspect that you are not using those. This is an area we are taking a look at BTW.

    I think that will work but have not tested that exact combination as I'm in the middle of other config stuff right now. Please let us know how it goes.

    Marc

Reply
  • Thanks to Shawn for linking the Command Line blog. In this case they won't help as Windows file association cannot be directed to use the command line switches.

    However as you only have one WorkSpace and WorkSet you can lock the applications to that combination.

    I suggest adding the following to ConfigurationSetup.cfg on each user's machine for each application, replacing any existing _USTN_CUSTOM_CONFIGURATION statements:

    [General]

    _USTN_USER_CONFIGURATION_LABEL = MyCompany Projects
    _USTN_USER_CONFIGURATION = Z:/Config/

    this is described in:

    CONNECT Edition - Configuration Tips: What does _USTN_USER_CONFIGURATION do?

    Then in Z:/Config/WorkSpaceSetup.cfg add:

    _USTN_WORKSPACENAME = EMP

    %lock _USTN_WORKSPACENAME

    _USTN_WORKSETNAME = Networks Eng

    %lock _USTN_WORKSETNAME

    I'd suggest adding an underscore to the WorkSet name, it's always best to avoid spaces in names.

    ConfigurationSetup.cfg can be distributed using a system policy or just a batch file that users can run to copy and replace if IT can't help immediately.

    Note that use of only one WorkSet does limit the functionality of some WorkSet based features, sheet indexing for instance, but I suspect that you are not using those. This is an area we are taking a look at BTW.

    I think that will work but have not tested that exact combination as I'm in the middle of other config stuff right now. Please let us know how it goes.

    Marc

Children
No Data