Programming DAQmx with or without Measurement Studio

[Chapashop]

I am trying to figure out if I can program my NI-DAQmx devices using NI-DAQmx API for .NET or should I use Measurement Studio.

At some point in the near future I will upgrade my VB6 apps to VB.net.  Over the last couple of years I have been developing VB6 apps to support newer DAQmx hardware using the NI-DAQmx C API library.  Previously when I was using my older USB DAQPad 6020E (and other older hardware) I was using the NI-DAQ Traditional drivers.  When I was programming the NI-DAQ Traditional drivers I was using Measurement Studio 6.x (MS6) as my interface.  Having MS6 made my programming job easier which I definitely realized when I did not have ActiveX controls in VB6 to control the DAQmx devices I had to control.  I went thru the documentation when I installed DAQmx and was able to figure the processes out.  It took me a while but the processes I started with 'Traditional' I was able to duplicate with the DAQmx C API.  I have a copy of MS7.1 Standard (which I am considering upgrading) and I am trying to figure out if I want to use Measurement Studio when I start developing apps in VB.net or could I just use the API. 

I am thinking that if the API for .NET is similar to my functions for C API maybe I could live without installing Measurement Studio.  I am a developer and my electronics understanding is not my primary strength so I think it takes me a while to figure stuff out that might be more apparent to someone who understands the hardware.  Having my code with Measurement Studio, and C API and having this forum I should be able to figure stuff out.

Thanks for any suggestions.

[David_Pratt]

Hey Chapashop,

The decision to utilize the GUI enhancements of MeasurementStudio or building everything in the .NET API is a personal decision on preference.  I really enjoy the use of MeasurementStudio in my programming environment, but the functionality of data acquisition can be fully utilized in either API.

[Chapashop]

I enjoyed having the MStudio activeX controls in VB6.  It made my development a lot easier.  I was somewhat spoiled by MSStudio for approximately 10 years of use with VB6.  When I used VB with the API functions for DAQmx it was definitely slow progress and difficult for me not knowing what I was doing.  But I resolved my issues and my apps work well.  I may dabble a little with the API and also with either my 7.1 that works with .NET or the trial of the latest version.

thanks, David

[David_Pratt]

Hey Chapashop,

Not a problem, good luck with your application development and let us know if you need anything else.