Measurement Studio for .NET Languages

cancel
Showing results for 
Search instead for 
Did you mean: 

manual integration of MS2010 and VS2010 not working

Solved!
Go to solution

Hi,

This is a beginner question, but I'm having some trouble getting Visual Studio 2010 to integrate with Measurement Studio 2010. I tried following the instructions to manually integrate MS in VS from the following page:

 

http://digital.ni.com/public.nsf/allkb/ACFFB3E03B97D0A8862575ED0058A7B1

 

and was able to do the first step of running devenv/setup on the VS command prompt. However, when I tried to do the second step of choosing an NI assembly to add to the toolbox, the only thing in the Assemblies/Current folder is NationalInstruments.Common.Native.dll, which Visual Studio rejects with the error message of not being a .NET module.

 

I am not sure what I should be seeing in the Assemblies/Current folder, or how to make this second step work. 

 

Any thoughts/suggestions would be much appreciated.

 

Thanks,

Ana

 

 

0 Kudos
Message 1 of 3
(5,798 Views)
Solution
Accepted by topic author malagon

Hey Ana,

 

Measurement Studio 2010 supports Visual Studio 2010 integration, so it shouldn't be necessary to do the manual integration.

 

When you run the installer for Measurement Studio, you will get to a screen which allows you to select the features you wish to install. You'll see a "Support for Visual Studio 2010" heading; make sure that you click the little disk button next to it and select to install that feature. If you expand the category, you'll also see that .NET Framework 4.0 Language Support is a sub-category, and within that category you'll see Visual Studio Integration. Make sure all of these elements are selected to be installed (should see a little disk icon with a white background).

 

I suspect that what happened is Measurement Studio was installed without Visual Studio support or .NET Framework language support--that would explain why Measurement Studio wasn't properly integrated, and why you weren't seeing the .NET assemblies in that folder. I think running the installer again and verifying these settings should resolve the issue. Let us know if you need any more assistance!

0 Kudos
Message 2 of 3
(5,787 Views)

Thanks very much! That worked perfectly.

0 Kudos
Message 3 of 3
(5,779 Views)