Configuration of the .NET environment

For being able to access devices supported by Impact Acquire in a .NET environment, the unmanaged/native libraries providing the low-level access to the hardware must be added to the search path of the runtime. This is achieved by calling mv.impact.acquire.LibraryPath.init(). Other functions of the class mv.impact.acquire.LibraryPath will allow to fine tune the search behaviour for native libraries.

Every program written using this interface will then continue by talking to the mv.impact.acquire.DeviceManager. This class has a static constructor, thus accessing any of the functions will automatically result in the object being created. To find out how to gain access to a certain device look at the detailed description of this class.

Once access to the desired device represented by an instance of the class mv.impact.acquire.Device has been obtained every other device related properties or functions can be accessed.

Stuff from the mv.impact.acquire.GenICam namespace is only available when using the mv.impact.acquire.TDeviceInterfaceLayout.dilGenICam interface layout (by setting mv.impact.acquire.Device.interfaceLayout to mv.impact.acquire.TDeviceInterfaceLayout.dilGenICam before opening the device. Classes from the mv.impact.acquire namespace might only be available in interface layout mv.impact.acquire.TDeviceInterfaceLayout.dilDeviceSpecific. These classes will state their limited availability in the documentation. Without setting the interface layout, mv.impact.acquire.TDeviceInterfaceLayout.dilDeviceSpecific will be used by default for all non GenICam™ devices and all mvBlueCOUGAR-X/XD devices. All other GenICam™ compliant devices will only support the mv.impact.acquire.TDeviceInterfaceLayout.dilGenICam layout. All example applications as well as complex GUI applications like ImpactControlCenter will either silently or explicitly switch to the mv.impact.acquire.TInterfaceLayout.dilGenICam interface layout if possible and the user didn't say otherwise so if an application copies code from example code make sure your application is aware of the interface layout and sets it accordingly!

Some source code samples how to locate a certain mv.impact.acquire.Device also can be found in the detailed description of the class mv.impact.acquire.DeviceManager.

Note

Since version 2.38.0 there are multiple versions of the .NET API binaries for Impact Acquire! To find out which is the best choice for your application refer to Building, Linking And Running Applications Using Impact Acquire