If you are going to move the View Set VBA to native Code for 2026 - actually move it to native code to make it part of the program and not just pieces of it. The variable should be assigned at an application level (CIVIL_VIEWSET_CONFIGURATION), the default configuration xml should be added to a "Program Files" location like "C:\Program Files\Bentley\OpenRoads Designer 2026.00\OpenRoadsDesigner\Cif\Defaults". The "Custom_Tools" dgnlib should have the right click menu items added to a "program Files" location gui dgnlib. There should not be pieces of it scattered in a workspace unless a user/company chooses to customize the delivered ones. This would mirror standard MicroStation configuration behavior.
| Civil Product Used | OpenBridge Modeler, OpenRoads Designer, OpenRail Designer |
Thanks for the detailed feedback. OpenRoads Designer 2026 has already been released, so this type of architectural change is not something we can address in that version. In the current implementation, View Set configuration is intentionally handled as a workset-level configuration variable to support project-specific control. That said, your request for a more fully application-delivered and centralized model is useful feedback, and we are marking it as Future Consideration for evaluation in a future release.