This table provides an overview of the different options you have for creating a NI-DAQ application, based on your language of preference (Visual Basic 6.0, Visual Basic.NET, Visual C#, or Visual C++ (MFC)), using NI-DAQmx or Traditional NI-DAQ (Legacy), and whether you have Measurement Studio or not. You can follow the links on the table itself or use the links at the bottom of the page for more information about the options.
|Measurement Studio for Visual Studio 2003/2005/2008||Measurement Studio Support for Visual Studio 6.0||Visual Studio only|
(without Measurement Studio)
|Visual Basic 6.0||Traditional NI-DAQ (Legacy)||N/A||Optimal||Yes|
|Visual Basic .NET||Traditional NI-DAQ (Legacy)||Possible||N/A||Possible|
|Visual C++ 6.0||Traditional NI-DAQ (Legacy)||N/A||Yes||Yes|
|Visual C++ MFC||Traditional NI-DAQ (Legacy)||Yes*||N/A||Yes|
|Visual C#||Traditional NI-DAQ (Legacy)||Possible||N/A||Possible|
*MFC C++ libraries available for Visual Studio 2005 and 2003 only.
OPTIMAL: Project wizards, code generation and configuration tools are provided to accelerate DAQ application development.
YES: Native components are provided for this purpose and shipping examples are included.
NO: The component is not designed for this environment and its use in that environment is not supported by NI. Click on the link for more information.
POSSIBLE: The component was not designed to work natively in that environment, but it is possible to use these components in the required environment by using wrappers or manual configuration. For example, you can use Runtime Callable Wrappers for accessing ActiveX controls in C# or Visual Basic.NET or by manually setting up a Visual C++ project to use C import libraries. Refer to the link for more information.
N/A: The Measurement Studio package does not provide support for the language of choice. Refer to the link for more information.
NI-DAQmx replaced Traditional NI-DAQ (Legacy) in 2003. NI strongly recommends using NI-DAQmx for new applications.