Measurement Studio for .NET Languages

cancel
Showing results for 
Search instead for 
Did you mean: 

MS support for Windows 7?

Solved!
Go to solution

Any ideas when NI will come out with a version of Measurement Studio that supports Windows 7?

 

I tried creating a simple form with a gauge on the newest Measurement Studio version, and it runs great on XP/Vista but fails immediately on Windows 7.

0 Kudos
Message 1 of 6
(5,301 Views)

The current beta of Measurement Studio officially supports Windows 7.  You can sign up for it here.  

 

However, what you are seeing is unexpected.  I am currently using Measurement Studio 8.6.1 on Windows 7 without any trouble.  Can you give more information or a sample project replicating what you're seeing?  Are you deploying this application to Windows 7 and seeing the errors, or are you developing on Windows 7 and getting the errors?  What version of Visual Studio are you using?  How does it fail - unhandled exceptions or some other crash?

 

Thanks,

 

NickB

National Instruments  

0 Kudos
Message 2 of 6
(5,295 Views)

Nick,

 

My development machine is currently running XP Pro, with Measurement Studio 8.6 on Visual Studio 2010.

 

 

To replicate the problem:

 

Create a Windows form using .NET Framework 3.5 (Windows 7 officially supports 3.5 and 4.0, but I have not been able to upgrade to 4.0 yet).

 

Drag and drop an NI Gauge from the toolbox.

 

Build the application, then deploy the application and associated libraries to a Windows 7 Ultimate machine.

 

When the application is started, I get the error "The application was unable to start correctly."

 

If I compile the same form without the NI Gauge, it runs perfectly.

 

The target machine (Windows 7) has .NET 3.5 installed (natively) but does not have any development software (MS, VS, etc).

 

Thanks!

 

-Steven

0 Kudos
Message 3 of 6
(5,274 Views)

Hey Steven - 

 

It'll take me a day or so to replicate your test situation, but in the meantime, have you ensured your deployment contains the dependencies defined by the Measurement Studio help topic "Measurement Studio .NET Merge Modules" or "Measurement Studio .NET XCOPY Deployment Files" - depending on your deployment scenario?  

 

Also -  are you able to determine which assembly is unable to load correctly?  Using the Fusion Log Viewer tool may be a good way to narrow down where the error is occurring.  Check out my (admittedly rough) blog post concerning this tool.  Even if it doesn't immediately solve this issue, it's a good tool to have in your back pocket.

 

I'll get back to you when I have more information,

 

NickB

National Instruments  

0 Kudos
Message 4 of 6
(5,270 Views)
Solution
Accepted by topic author shansen

Hey Steven,

 

Today I installed VS2010 Beta on an XP SP3 machine, created a setup project from an application containing a gauge and targeting the 3.5 framework, deployed that to a clean Windows 7 machine, and everything worked like a charm.  I did need to add additional components to the setup project according to the help file I pointed you to in my last post.  In the following screenshot, I have all the dependencies that were installed along with my application.  Give that help documentation a good read, and then let me know if things still aren't working for you.

 

NickB09-18, 13_31_45.png 

 

Thanks!

 

NickB

National Instruments  

0 Kudos
Message 5 of 6
(5,247 Views)

Well, now that you've demonstrated that it does work, I feel like I jumped the gun...

 

I won't have access to a clean Windows 7 machine for a few days, but when I have some time, i'll sit down and try to duplicate my problem again.

 

I did deploy the merge modules as I always have in the past, but it's possible that I made a mistake somewhere else.

 

Thanks for the help!

0 Kudos
Message 6 of 6
(5,236 Views)