LabWindows/CVI

Content Type
Programming Language
Current manual
Product DocumentationLabWindows/CVI....NET LibraryCreate LabWindows/CVI .NET Controller Dialog BoxCurrent page
Table of Contents

Create LabWindows/CVI .NET Controller Dialog Box

Create LabWindows/CVI .NET Controller Dialog Box

Use the Create LabWindows/CVI .NET Controller dialog box to generate a LabWindows/CVI wrapper for a .NET assembly. LabWindows/CVI generates the wrapper in the form of an instrument driver, source file, and header file. You also can use the LabWindows/CVI .NET Library functions in conjunction with the generated wrapper when calling a .NET assembly.

Note  LabWindows/CVI supports Microsoft .NET Framework 1.1 Service Pack 1 or later. To create a LabWindows/CVI wrapper for a .NET assembly or to use the .NET Library, you must have .NET Framework 1.1 Service Pack 1 or later installed on your computer. You can download the .NET Framework from the Microsoft Web site.

If you install the .NET Framework after you install LabWindows/CVI, you must then reinstall LabWindows/CVI or repair the existing LabWindows/CVI installation.

Select Tools»Create .NET Controller to open the Create LabWindows/CVI .NET Controller dialog box. The Create LabWindows/CVI .NET Controller dialog box provides the following controls:

  • Assemblies in Global Assembly Cache—Lists the .NET assemblies that are available in the Global Assembly Cache (GAC) on your computer. If you enable the Specify Assembly by Path option, this control is not available. The Assemblies in Global Assembly Cache list provides the following information:
    • Name—The assembly name.
    • Version—The version number of the assembly.
    • Culture—The language or region the assembly targets. The culture can affect strings, time, currency formats, and so on. Neutral indicates that the assembly does not target a specific language or region.
    • Public Key Token—The key, provided by the assembly creator, that is used for security and cryptographic purposes.
    • Processor Architecture—The processor of the target platform of the assembly. The values in this field can include x86, AMD64, and MSIL. If the assembly does not identify a processor architecture, the field is blank.
    Note  If two or more assemblies differ by name, version, culture, or public key token, .NET considers them to be different assemblies.
  • Specify Assembly by Path—Specifies whether to generate the wrapper for the .NET assembly in the Assembly Path control. If you enable this option, the Assemblies in Global Assembly Cache control is not available.
  • Assembly Path—Specifies the path and filename of the .NET assembly for which LabWindows/CVI generates a wrapper. You can use the Browse button to browse to the .NET assembly.
  • Target Instrument—Specifies the path and filename of the instrument driver LabWindows/CVI generates. You can use the Browse button to browse to a new or existing .fp file.
  • Add Instrument to Project—Specifies whether to add the generated .fp file to the current project.
Note   LabWindows/CVI returns an error if you attempt to run multiple instances of the Create LabWindows/CVI .NET Controller dialog box at the same time.

When you click OK, LabWindows/CVI opens a renaming dialog box, which you can use to modify the names of .NET identifiers in the target assembly. You also can use the renaming dialog to select the .NET identifiers you want to include in the target assembly.

After LabWindows/CVI generates the wrapper, it opens a dialog box that indicates it has successfully generated an instrument driver to control the selected .NET assembly. If the selected assembly references types that are defined in other assemblies, the dialog box displays a list of the names and locations of the assemblies in which these types are defined. You must generate wrappers for the assemblies if you need full access to the types defined in them. If the wrapper generation process returned errors and/or warnings, the dialog box displays a Warnings and Errors section.

Was this information helpful?