The driver name is the primary identifier for the entire IVI.NET driver project. Virtually all names associated with the driver will be based on the driver name. The driver DLL, the IVI Configuration Store entries, the driver interfaces, the main driver class, and many other items are based on this entry.
General Page, New IVI.NET Driver Wizard
The General Page of the New IVI.NET Driver Wizard presents basic information about the IVI.NET driver project.
Driver name
Instrument manufacturer
The instrument manufacturer is used to identify the manufacturer of the instrument for which the driver is being written. This entry is used in the IVI Configuration Store registration as well as in the implementation of the IIviDriver.InstrumentManufactuer property.
Driver vendor
The driver vendor identifies the company responsible for development and support of the driver. This entry is used in the IVI Configuration Store registration as well as in the implementation of the IIviDriverComponentIdentity.Vendor property.
Assembly name prefix
This entry controls the name of the .NET assembly. The IVI specifications require that this prefix represent the driver vendor. The full name of the .NET assembly based on this prefix is displayed in the Assembly name text box just below this entry.
Assembly name
This is a read-only field that displays the .NET assembly name resulting from the choice entered in the Assembly name prefix field
Instrument model
The name of the instrument model for which the driver is being written. The driver must be able to use this string to identify the actual connected instrument during driver initialization, such as through the use of a “*IDN?” query.
If the driver is to support multiple instrument models, enter one of the most common models here. The Models Page of the Driver Settings Editor can be used to add models to the driver. See the topic Adding Support for Multiple Instrument Models for more information on multi-model drivers.
.NET Support
Nimbus supports building IVI.NET drivers as NuGet packages targeting one or more .NET targets at version .NET 6.0 or greater. If None is selected, then no NuGet package is created and only a conventional .NET Framework driver is created.
Although only a single .NET target can be specified here in the wizard, multiple .NET targets can be added later after the project is created by simply editing the TargetFrameworks MSBuild property in the driver project file.
.NET Framework support
Specifies the version of the .NET Framework to be used for the driver. The .NET Framework assembly will be included in the driver installer, as with previous versions of Nimbus. Additionally, a reference assembly for the specified version of the .NET Framework will be included in the driver NuGet package.
Nimbus supports building only a single .NET Framework target for IVI.NET drivers. The value specified here can be changed after project creation by editing the TargetFramework MSBuild property in the driver project file.
Code template set
The code template set the driver is created with, chosen from the sets in the machine catalog that have an IVI.NET part, or <none>. The set is copied into the driver project, and its default templates supply the bodies of the driver’s members, including the ones the driver is created with. The set can be changed later on the Code Templates page of the Driver Settings Editor.
The field starts out with the Template set for new drivers chosen on the General page of the per-user preferences.
If the wizard also creates a linked IVI-C driver, that driver gets the set’s IVI-C part, if the set has one. See Linked IVI-C drivers.