User`s guide

284 VEE User’s Guide
7 Using .NET with VEE
The most commonly used assembly, mscorlib, is selected in
the previous graphic. Go ahead and select this assembly.
mscorlib encapsulates many functions useful to VEE users,
such as file system manipulation, collection management,
and data type conversion. Another very commonly used
assembly is System, which contains functions such as process
management, web request and response, and regular
expressions.
Under the COM tab is a list of all the COM type libraries
currently registered on your computer. In fact, this is almost
the same list of type libraries you see when you use the
ActiveX automation references dialog box.
How do you know which of these two choices to use? You
should use the ActiveX automation references dialog box if
the following cases are all true:
• If the library appears there
• If the library is fully functional in previous versions of
VEE
• If the library has no Primary Interop Assembly (PIA).
Using the ActiveX automation references directly avoids
adding another layer, the .NET and COM Interop layer.
You should use the .NET/COM Interop explained in this
topic:
• If the library doesn't appear in the ActiveX automation
references dialog box.
• If not all of the library’s functionality gets imported
• If you know the COM library has a PIA
For example: not all IVI- COM driver interfaces are visible
from the Function & Object Browser’s ActiveX Objects list.
However, the .NET interop does allow you to see all of the
IVI driver interfaces.
When using the .NET Assembly References menu option and
selecting a COM type library from the list, VEE tries to
import the COM type library as a .NET assembly. If there is
a PIA, VEE uses it, otherwise VEE creates an Interop
Assembly (or assemblies if the COM type library references