Developing XBOX Kinect Applications in LabVIEW

• Loading .NET 4.0 Assemblies in LabVIEW

Since LabVIEW 2011 and earlier versions of LabVIEW do not automatically support .Net 4.0, it needs to be added manually.

Method: Create a text file LabVIEW.exe.config in the location where the Labview.exe file is located. The file name must be LabVIEW.exe.config and saved in ANSI format. Add the following information to the file. Note that the version number v4.0.30319 is your actual .Net version. You can use the highest version number in C:WindowsMicrosoft.NETFramework to find it.

="true">

.NET 4.0 namespcase @ Assemblies References in LabVIEW

A. Most .net assembly references are done by placing a .net constructor in the flowchart, then selecting assembly, then selecting Objects and the corresponding Constructor.

B. Place a .NET Contrainer on the front panel, then Insert .NET Control (select Assembly first, then Controls). Unfortunately, LabVIEW only supports a very small number of WPF Controls.

C. Place the .NET property and method nodes directly, then select class, ->.net, ->browse, -> assembly, -> Objects.

For example: System.windows.media.imaging.writebtiamp is in presentationcore (4.0.0)

•  WPF References in LabVIEW

Unfortunately, LabVIEW does not support WPF Controls. The disadvantages are: the interface and code development cannot be separated; many beautiful and powerful components in WPF cannot be used. Taking the Kinect project as an example, you cannot use System.windows.media.image Control, and you must use the Picture Control provided by Labview, which greatly reduces efficiency.