BridgeLink is a bridge engineering application framework. BridgeLink provides a single entry point into a suite of bridge engineering applications such as BEToolbox, PGSuper, and XBeamRate. BridgeLink applications are runtime discovered and automatically integrated in the application framework.
This repository holds the source code fo the BridgeLink application.
If you are looking to download the MSI installer package for the BridgeLink bridge engineering suite, you can do so from WSDOT at http://www.wsdot.wa.gov/eesc/bridge/software.
If you are looking to build BridgeLink from source you will need to start with the Washington Bridge Foundation Libraries (WBFL) and then the BridgeLink plug-in applications (such as PGSuper).
In theory, you can build the main BridgeLink application without any of the plug-in applications and you'll have a running program. It won't do anything because it will be just an empty shell. The BridgeLink suite is most useful when there are BridgeLink plug-in applications available.
The standard BridgeLink plug-in applications are:
Once you've cloned the repositories for the BridgeLink plug-in applications you want to use:
- Satisfy the prerequisites and build WBFL
- Satisfy the prerequisites and build one or more BridgeLink plug-in applications using the VS Solution File (*.sln) in the app's repository
- Build BridgeLink using the BridgeLink.sln solution
The prefered method to build the entire BridgeLink suite is to:
- Satisfy the prerequisites and build WBFL
- Satisfy the prerequisites for all the standard BridgeLink plug-in applications
- Build the BridgeLink suite using the BridgeLinkComplete.sln solution.
The general prerequisites are:
- Download and install the following projects before you can build the WBFL
-
Define BOOSTDIR and XSDDIR environment variables for the location where the boost and code synthesis libraries are installed.
-
Clone the repository into drive letter:/ARP/ and create an environment variable ARPDIR to this folder.
-
Obtain and install the Stingray ObjectiveGrid product from Perforce (https://www.perforce.com/products/stingray). Several of the BridgeLink plug-in applications use this grid control product in the UI since a suitable open source grid control has not been identified. A do-nothing proxy for the ObjectiveGrid control is available WBFL. This proxy enables full BridgeLink suite builds without the ObjectiveGrid control. The proxy does not simulate grid functionality, it simply provides dummy classes and methods to enable builds. Accessing windows and dialogs that utilize the ObjectiveGrid control will not function properly and may crash. See WBFL for details on building the BridgeLink suite without ObjectiveGrid.
All BridgeLink applications are plug-ins to the BridgeLink-environment. BridgeLink discovers the plug-in applications at runtime using COM Component Categories.
When running BridgeLink from the Visual Studio development environment, you must register the BridgeLink plug-in applications with RegSvr32.exe. Additionally, some BridgeLink plug-in applications themselves have runtime discoverable components. One example is PGSuper. These components must be registered as well.
To make life easy, there is a script file in the BridgeLink source code called RegFiles.js. The header of this file provides step-by-step instructions for setting up the Visual Studio Tools > External Tools feature to register all these components automatically.
Before starting a debugging session, use the script file to register all of the Debug or Release build components (depending on if you are starting the debugger or just launching the application, respectively).
If anyone has a better way of automatically registering these components, please implement and send a pull request.
This project is jointly developed by the Washington State and Texas Departments of Transportation
- Richard Brice, PE - WSDOT
- Richard Pickings, PE - BridgeSight Inc for TxDOT
This project is licensed under the Alternate Route Open Source License