Now that ORD 10.10 supports dual install with 10.9 (and future versions I assume) I've been looking at what we need to do in our workspaces to support dual installing. It looks like if we need to support both versions for projects from the same client we'll need to be able to to pick a folder (or folders) containing the dgnlibs that support the schema of the currently launched application. It doesn't currently look like their are any variables that define what schema is in use.
Variables I've looked at:
Basically I'd like to be able to have folders named $(_ENGINENAME)-$(_USTN_PRODUCT_SCHEMAVERSION) or $(_ENGINENAME)/$(_USTN_PRODUCT_SCHEMAVERSION) and then put the dgnlibs required for that version under those folders.
OneConfiguration supports this concept but there isn't a variable i can use in the _USTN_PRODUCT_ONE_* variables to pick folders based on schema.
Currently my solution is most like to be something like below, but it gets cumbersome pretty fast.
%if $(_USTN_PRODUCT_FULLMARKETINGNAME) == "OpenRoads Designer CONNECT Edition - 2020 Release 3" SCHEMA_VERSION = $(_ENGINENAME)-10.09 %endif %if $(_USTN_PRODUCT_FULLMARKETINGNAME) == "OpenRoads Designer CE - 2021 Release 1" || $(_USTN_PRODUCT_FULLMARKETINGNAME) == "OpenRoads Designer CE - 2021 Release 2" SCHEMA_VERSION = $(_ENGINENAME)-10.10 %endif
This would also be useful to make sure the correct product is being used for a workset. so in the WorkSet cfg file, if i do the above, I can do:
%if $(_ENGINENAME) == "OpenRoadsDesigner" && $(SCHEMA_VERSION) <> "ORD-10.09" %error Incorrect OpenRoads is being used. This project requires ORD 10.10 %endif
This would be very helpful!
MaryB
Power GeoPak 08.11.09.918Power InRoads 08.11.09.918OpenRoads Designer 2021 R2