.NET Page, IVI-COM Driver Settings

Interop assembly code signing

Three different options are available for performing code-signing on the interop assembly used to access the IVI driver from .NET applications. It is important to understand the implications of each option before proceeding. For a detailed discussion of .NET code-signing, see the topic Supporting .NET Client Applications.

Use full signing with temporary Nimbus public-private key file

This option uses a “default”, non-secure public-private key that ships with Nimbus. This option is useful when testing a driver and neither a fully public-private key pair nor a public key is available.

Caution

You should never ship a driver that has been built with this option selected. Always use a public-private key that represents the actual driver vendor.

Use delay signing with the following public key file

This is the preferred setting because it only requires the driver developer to have access to the public key file, rather than the full public-private key. Note that a driver compile with this option cannot be used from .NET without re-signing the interop assembly with the full public key. For a discussion of delay signing, see the topic Supporting .NET Client Applications.

Use full signing with the following public-private key file

This option enables a driver developer to sign the driver with the full public-private key so that it will be immediately usable from .NET without the need to perform a separate re-signing step.

Caution

Though convenient, this option is the least secure because it requires the driver developer to have direct access to the full public-private key pair. The public-private key should be maintained in a secure location with limited access. The delay-signing option above is the recommended approach.

Interop assembly naming

Assembly name prefix

This entry controls the name of the .NET interop assembly as well as that of any .NET policy files shipped with the driver. The IVI specifications require that this prefix represent the driver vendor. The full name of the .NET assemblies based on this prefix is displayed in the Assembly name text box just below this entry.

For a detailed discussion of .NET interop assemblies, see the topic Supporting .NET Client Applications.

For more information on .NET policy files, see the topic Understanding .NET Versioning.

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

See also

• Supporting .NET Client Applications