I'm hoping this is a quick question: can "Plain" MicroStation CONNECT (i.e.no verticals, non-ORD) access a workspace developed for ORD? I ask because I'm getting ready to work on a project where the deliverable will be ORD but, but it's a good bet not everyone will use ORD. Some of our partners doing non-roadway work will use "plain" MicroStation CONNECT. Will there be any sort of issue with them doing so? I'm guessing not, but want to confirm. The corollary question: can a user of MicroStation V8i SS10 access this workspace? With the advent of worksets and such, I am guessing not...Thanks for any information!
jcallicott:
The short answer is yes. We first developed our ORD Workspace, and I got to thinking about using a shared WS for both ORD and MSConnect. The simple solution is to use the same config files (ConfigurationSetup.cfg and WorkspaceSetup.cfg) for both products (MS Connect will not "see" the ORD data anyway). Just copy the ORD files from the C:\ProgramData\Bentley\OpenRoads Designer CE\Configuration\ directory to the C:\ProgramData\Bentley\MicroStation CONNECT Edition\Configuration\ directory. Simple.
As regards your follow-up question, I am not sure as we moved from SS2 InRoads directly to ORD, but my initial feeling is that such will not work because of WorkSpace/ WorkSet integration built within the Connect products.
Mark
Answer Verified By: jcallicott
Shared Workspaces are working quite well for us right now - after a bit of fiddling we have a common workspace for OpenRoads, OpenRail, OpenBridge Modeler and Microstation. A bit of trial and error to keep each app loading the minimal libraries they need, but works well.
Regards,
OpenRoads Designer 2022 R3 (10.12) | Microstation 2023 | ProjectWise CE 3.4