LabVIEW Configuration Files for the APx API

Created on 2013-04-24 17:42:00

The LabVIEW Project Explorer was introduced in LabVIEW version 8.0 as a means to provide a system-level view of the files needed for a LabVIEW application. While in many cases, the use of a LabVIEW project is optional, we have found that when working with .NET assemblies such as the APx500 API, the use of a LabVIEW project is critical.

The LabVIEW Driver installer puts a LabVIEW project named APx500 Examples Project.lvproj in the My Documents folder under Audio PrecisionAPx500 n.mLabVIEW (where n.m represents the APx version number). There is also a shortcut to this project placed in the Start Menu. The Examples project contains a number of example VIs to help you get started using the APx driver.

LabVIEW project with configuration file circled.

A configuration file with the same name as the LabVIEW project must be included in the folder that the LabVIEW project resides in. Using a project file and accompanying .config file like this when working with the APx Driver VIs will prevent errors caused by cross-linking and by LabVIEW referencing the wrong version of the APx API. If a project file and .config file are not used, in some cases the LabVIEW driver VIs may not work.

The Examples project shown in the figure above contains a configuration file named APx500 Examples Project.lvproj.config. You can use this file in your own LabVIEW project by simply renaming it. The config file must have the same name as your LabVIEW project, followed by “.config”. For example, if you create a new LabVIEW project named MyAPx500Project.lvproj, make a copy of the .config file above in the same folder as the project and rename it to MyAPx500Project.lvproj.config.

The text of the config file follows below. You can copy this text, or use the config file in the APx500 Examples Project.

<?xml version="1.0" encoding="utf-8" ?>
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
<assemblyIdentity name="AudioPrecision.API"
culture="Neutral" />
<!– Assembly versions can be redirected in application,
publisher policy, or machine configuration files. –>
<bindingRedirect oldVersion="" newVersion="" />

When updating a project for a new version of APx500, be sure to change the version references in the .config file accordingly. The reference shown here is the proper reference to the APx API version 3.3:
<bindingRedirect oldVersion="" newVersion="" />