successfully by taking the following actions: The IVI.NET driver installer checks for the presence and version of the required IVI.NET shared components variant as specified in Section 5.2.1, Detecting the Presence of an IVI.NET Shared Components Variant. If the required variant of the IVI.NET shared components is installed, the driver installer proceeds with driver installation. IVI.NET Software Module Entries in the IVI Configuration An IVI.NET driver installer shall create a software module entry for the driver variant in the IVI configuration store, as specified in Each driver variant has a IVI-3.5: Configuration Server Specification. separate software module entry. Note: IVI.NET wrappers shall always be packaged separately from IVI-COM and IVI-C drivers. Software Module Entries for IVI.NET Drivers Table 53. Package Name Prefix ProgID Assembly Type Qualified Name IVI.NET Empty Component Empty Driver’s <DriverNamespace> driver String Identifier string Assembly <FullVersion> Qualified <FwkVerShortName> Class Name IVI.NET Empty Component Empty Driver’s <DriverNamespace>”Wrapper” wrapper String Identifier string Assembly <FullVersion> Qualified <FwkVerShortName> Class Name As an example, for an IVI.NET driver variant with an IVI.NET driver namespace of a Version of and a .NET Framework Version of the Software “Agilent.Agilent34401a”, “2.5.0”, “v3.0” Module name is the following: Agilent.Agilent34401a v2.5.0 Fx30 If the driver variant is a wrapper, the name is the following: Agilent.Agilent34401aWrapper v2.5.0 Fx30 For additional requirements on creating Software Module Entries in the IVI Configuration Store, refer to Section 5.3, Details on Software Module Entries in the IVI Configuration Store. IVI.NET Driver Uninstaller The IVI.NET driver installer provide a mechanism for the user to uninstall the driver variant that was previously installed. The uninstaller mechanism shall do the following: Remove all Windows registry entries for the driver. Remove the assemblies and policy files from the GAC. Remove all files for the driver variant. Remove the Component Version-Specific Directory for the driver variant.
successfully by taking the following actions: The IVI.NET driver installer checks for the presence and version of the required IVI.NET shared components variant as specified in Section 5.2.1, Detecting the Presence of an IVI.NET Shared Components Variant. If the required variant of the IVI.NET shared components is installed, the driver installer proceeds with driver installation. IVI.NET Software Module Entries in the IVI Configuration An IVI.NET driver installer shall create a software module entry for the driver variant in the IVI configuration store, as specified in IVI-3.5: Configuration Server Specification. Each driver variant has a separate software module entry. Note: IVI.NET wrappers shall always be packaged separately from IVI-COM and IVI-C drivers. Table 53. Software Module Entries for IVI.NET Drivers Package Type Name Prefix ProgID Assembly Qualified Name IVI.NET driver <DriverNamespace> <FullVersion> <FwkVerShortName> Empty String Component Identifier Empty string Driver’s Assembly Qualified Class Name IVI.NET wrapper <DriverNamespace>”Wrapper” <FullVersion> <FwkVerShortName> Empty String Component Identifier Empty string Driver’s Assembly Qualified Class Name As an example, for an IVI.NET driver variant with an IVI.NET driver namespace of “Agilent.Agilent34401a”, a Version of “2.5.0”, and a .NET Framework Version of “v3.0” the Software Module name is the following: Agilent.Agilent34401a v2.5.0 Fx30 If the driver variant is a wrapper, the name is the following: Agilent.Agilent34401aWrapper v2.5.0 Fx30 For additional requirements on creating Software Module Entries in the IVI Configuration Store, refer to Section 5.3, Details on Software Module Entries in the IVI Configuration Store. IVI.NET Driver Uninstaller The IVI.NET driver installer provide a mechanism for the user to uninstall the driver variant that was previously installed. The uninstaller mechanism shall do the following: Remove all Windows registry entries for the driver. Remove the assemblies and policy files from the GAC. Remove all files for the driver variant. Remove the Component Version-Specific Directory for the driver variant.