Do we have to use new workspace with upgrade?

We are currently running ORD 2021 R2 and will be upgrading to 2022 R1. I understand that there is a new 'version' of file created with the new release, however there is also a new workspace installed.

My question is, if we have a corporate workspace that was built with 2021 R2 or earlier, do we need to use the newly created 2022 R1 workspace or can we specify the old one without any issues?

We are having a hard time understanding what changes in the workspace and some are thinking we have to copy all our customized files over to the new workspace but don't want to loose any new data that got install.

Long story short, can we keep using a 'old' workspace on our server but keep updating ORD software.

Thank you

Parents
  • Can this be done?

    In our ORD_Projects.cfg file there are the following lines

    # Restricts Text Styles to only populate from the listed file(s) plus the current active file.
    # Text Styles defined in other dgnlib files pointed to by MS_DGNLIBLIST variable are ignored.
    # All dgnlib files that include the string 'Text Style' in their name will be loaded.
    MS_DGNLIBLIST_TEXTSTYLES < $(_USTN_WORKSPACESTANDARDS)Dgnlib/Feature Definitions/*Text Style*.dgnlib

    Can an additional line be added?

    MS_DGNLIBLIST_TEXTSTYLES < C:\Company DgnLib Files\Dgnlib/Feature Definitions/*Text Style*.dgnlib

    (This file would have only our modified styles in it)

    Can you pull from 2 directories so that after each workspace upgrade you dont need to copy files over to the new workspace?

    I am trying to figure out how large corporations like US DOTs handle Release updates and new Workspaces and custom files. Any assistance would be greatly appreciated.

    Thanks in advance to all responders

  • Yes, ideally if you are inheriting the workspace from elsewhere and just want to add some additional text styles or similar then its best to keep those in a separate dgnlib and add it to the workspace. Your example above will work.



Reply Children
No Data