Difference between revisions of "RPC HELP Dev Considerations"

Revision as of 20:25, 3 July 2015

RPC Broker Help Home

Developer Considerations

Source Code

As of RPC Broker Patch XWB*1.1*14, the RPC Broker source code was released. The release of the source code does not affect how a developer uses the Broker Components or other parts of the BDK.

NOTE: Modified BDK source code should not be used to create VistA GUI applications. See Developer Utilities for details.

Suggestions for changes to the BDK should be done via VistA 's National Online Information Sharing (NOIS) system (for bugs) or VistA 's Electronic Error and Enhancement Requests (E3R) system (for enhancements) for review and possible inclusion in a future patch.

The source code is located in the ..\BDK32\Source directory.

Design-time and Run-time packages

As of RPC Broker Patch XWB*1.1*14, the BDK now has separate run-time and design-time packages. There is no longer a VistA Broker package. The new packages are XWB_Dxx and XWB_Rxx, where "D" means Design-time and "R" means Run-time and where "xx" is two digits indicating the version of Delphi with which it should be used (e.g., XWB_D50 is the design-time package for Delphi V. 5.0). The run-time package should not be used to create executables that depend on a separate XWB_Rxx.bpl installed on client workstations. There is no procedure in place at this time to reliably install the correct version of the run-time bpl on client workstations.

NOTE: Do not compile your project so that it relies on dynamic linking with the BDK's run-time package; that is, do not check the "Build with runtime packages" box on the Packages tab of the Project Options dialog.

Reuse

Developers should be aware of existing resources that may be of use. These resources may be available nationally or through a particular project. Possibilities include:

• Delphi components such as the VA FileMan Delphi components (FMDC). See [here]
• RPC BROKER APIs
• Existing M APIs