Variable to open specific version of OpenRoads per project?

RE: Variable to open specific version of OpenRoads per project?

mwlong — Thu, 22 Jun 2023 11:30:42 GMT

We had a meeting with our Bentley PW consultant who provided another aspect of this function. If you select your main project folder you can right click on it and select Properties. Select the Resources tab and verify the Resource Type is set to Application.

Scroll down to the versions of ORD and select the ones you are not using for the project, then select Remove.

This removes the ORD versions from the list available if a user tries to right click on a file and selecting Open With.

RE: Variable to open specific version of OpenRoads per project?

mwlong — Tue, 13 Jun 2023 14:32:16 GMT

I think I found what the issue was. Under <Tools <Associations <User my ORD version was not set correctly for 2022 R1. It was set to use 2022 R3. Making that correction I am able to apply the application to a file and it opens with the correct version.

RE: Variable to open specific version of OpenRoads per project?

mwlong — Tue, 13 Jun 2023 10:28:40 GMT

Kevin van Haaren

I seem to have run into an issue with this method. Working in a client's datasource, they use ORD 10.11 (2022 R1) currently. They have a vba that runs upon opening a file which checks for the ORD version. If it does not match ORD 10.11 it will not open the file. I applied my ORD 10.11 Application to a file (we are helping them update their workspace to ORD/CONNECT so I have Admin privileges). When I double click on a file in PWE I receive the dialog stating the version attempting to open the file is not 10.11. If I right click on the file and select Open With & browse to the 10.11 OpenRoadsDesigner.exe the file opens.

Do you think something with that vba module is causing the issue?

RE: Variable to open specific version of OpenRoads per project?

Kevin van Haaren — Sat, 10 Jun 2023 16:07:05 GMT

That lets you change what applications are available in the application drop down for files in the project, but doesn’t let you change what an extension maps to in that project.

I don’t remember what happens when you drag a dgn file into a project that does not have the application with the dgn extension in its resources. I want to say it assigns the default anyway, but it may assign the no application instead.

RE: Variable to open specific version of OpenRoads per project?

Mark Shamoun — Sat, 10 Jun 2023 04:07:46 GMT

What about editing your Work Area Resources to change the Application list to the new version specific ones?

RE: Variable to open specific version of OpenRoads per project?

mwlong — Fri, 09 Jun 2023 13:08:44 GMT

I finally had a chance to work on this. Your method works. I wish there was a way to apply it to an entire project rather per file.

RE: Variable to open specific version of OpenRoads per project?

mwlong — Fri, 14 Apr 2023 11:23:09 GMT

Kevin van Haaren

Thanks for the information. I have not had time to fully digest this information but I will go over this with our PW Administrator and discuss this option. I have one question. I believe I have found the location to set this up. In PW Admin I go to <Datasources <Datasource <Applications. In the pane I see OpenRoads Designer. When I select that, right click, select Properties. Now I see the dialog like the screenshot you posted.

This is where I add the various version specific Class Names?

RE: Variable to open specific version of OpenRoads per project?

Kevin van Haaren — Thu, 13 Apr 2023 18:33:26 GMT

Not in a configuration block. You can create application definitions that specify a specific version, then assign that application definition to a file. The trick is to use the version specific Program Class Name in the open action.

Here's the definition i use for OpenRoads 10.11

When that application is assigned to a file and the user double-clicks the file, ORD 10.11 will be opened automatically. If they right-click and select Open With..., or the default application is not installed, Any installed application that has a matching Open action will be listed in the Open With... dialog and they can pick one of those apps. (The Open With... dialog will also show an option for whatever application is assigned to the file extension this file has. For dgn that'll probably be whatever the last Bentley application that was installed)

By default you can only set one application to be assigned to files with a specific file extension per datasource and it's annoying to manually assign the application for all files i a project, but if the files are created from a seed file inside the microstation products it will retain the application of the seed file, so you can assign those properly it will help for a project. Additionally users can set which application is assigned to a particular extension when the file is created by going to Tools > Associations > File Extensions... Note this doesn't affect what application is used when the file is opened, just what application is assigned to a new file created in PW.

Basically we create a generic "Microstation" application that has all the versions listed for all products and we make that the default for .dgn. Then we create version specific application definitions. When we setup a workspace we make sure the seed files are properly assigne to the correct application for that workspace, then if user's ask we show them how to change their association for the .dgn extension to what they want.

Here are all the version specific Program Class Names I have:

Application	Version	Version PCN
MicroStation	All V8i	Bentley.MicroStation.Application.{B1E9E1E2-213C-47e5-BDD0-6A528DAE0244}
MicroStation	All Connect	Bentley.MicroStation.Application.{39949BF5-7E21-4A7B-A640-6E7199B7D588}
OpenBridge Modeler	V8i SS3	Bentley.OpenBridgeModeler.Application.{8AF1BE9F-A6FD-470D-8ED0-0758ACC9592C}
OpenBridge Modeler	10.8/10.9	Bentley.OpenBridgeModeler.Application.{81969A98-EDF7-4B21-9D23-7A15482E543F}
OpenBridge Modeler	10.10.00	Bentley.OpenBridgeModeler.Application.{5C3DC36B-828F-3D8D-AB76-B1510491B515}
OpenBridge Modeler	10.10.20	Bentley.OpenBridgeModeler.Application.{59AFC35E-CC0C-3943-9947-DFBA383D9A97}
OpenBridge Modeler	10.11	Bentley.OpenBridgeModeler.Application.{69A810CF-865E-39AD-A727-BAD768EFF32C}
OpenBridge Modeler	10.12	Bentley.OpenBridgeModeler.Application.{B2BAF2DC-F2FB-3A63-A5FE-18BECD5260AF}
OpenRail Designer	10.8/10.9	Bentley.OpenRailDesigner.Application.{718972C7-007F-4F72-8AD5-5B0B750E2493}
OpenRail Designer	10.10	Bentley.OpenRailDesigner.Application.{217410A6-1CD3-383A-A300-1A63A1CF5925}
OpenRail Designer	10.11	Bentley.OpenRailDesigner.Application.{E4DBA4A0-5F0B-31C8-8206-BB7EC9495183}
OpenRail Designer	10.12	Bentley.OpenRailDesigner.Application.{1049CC57-E951-3C6B-A4AD-FB24B9FF1D90}
OpenRoads Designer	10.8/10.9	Bentley.OpenRoadsDesigner.Application.{D11A86DD-FF26-4139-9C79-C1ABB4C8B5BF}
OpenRoads Designer	10.10	Bentley.OpenRoadsDesigner.Application.{359F376F-B120-3DD3-BC30-56D5687B766D}
OpenRoads Designer	10.11	Bentley.OpenRoadsDesigner.Application.{B0DCB521-5CE0-3CB5-AD8A-477E98D9B913}
OpenRoads Designer	10.12	Bentley.OpenRoadsDesigner.Application.{0A1BD8D1-4A49-3D5C-9824-0BC589BE1DEA}
OpenSite Designer	10.8/10.9	Bentley.OpenSiteDesigner.Application.{7EA0E81E-B260-4808-8921-5C6824F6E48F}
OpenSite Designer	10.10	Bentley.OpenSiteDesigner.Application.{6C9E6F02-C9CE-3439-BE38-BE20FB1B3795}
OpenSite Designer	10.11	Bentley.OpenSiteDesigner.Application.{F2103407-E1A1-352E-B57D-469212FB8D8D}
OpenSite Designer	10.12	Bentley.OpenSiteDesigner.Application.{0FEEB2DB-1678-3DA0-9539-89A662D41850}
Power GEOPAK	V8i SS2	Bentley.PowerGEOPAK.Application.{9B761AD8-C9AB-40F1-BA77-C24AE5B72D18}
Power GEOPAK	V8i SS10	Bentley.PowerGEOPAK.Application.{C6AAA004-FECD-4f5f-8E45-BBDED70BD222}
Power InRoads	V8i SS2	Bentley.PowerInRoads.Application.{593F2B8E-BDEE-490c-B4C3-B48BC356DB91}
Power InRoads	V8i SS10	Bentley.PowerInRoads.Application.{6AADD2ED-E230-47b9-928D-2AC9518B8A8C}
Power Rail Track	V8i SS2	Bentley.PowerRailTrack.Application.{C495A45E-6B0A-411b-AA3B-E327C56D95E4}
Power Rail Track	V8i SS10	Bentley.PowerRailTrack.Application.{6F40A634-F96C-4092-AD64-1E8AF69F47D4}