Measurement Studio for .NET Languages

cancel
Showing results for 
Search instead for 
Did you mean: 

NationalInstrumnets.UI.Internal.WaveformPlotElement threw an exception

Solved!
Go to solution

Frank,

 

I have a few quick quick questions:

 

1. Is this error occurring while attempting to build your assembly on your development machine or while attempting to use it (either on the same machine or the target machine)?

 

2. Are you using the AnyCPU setting to build your 64bit assembly or are you explicitly choosing 64bit?

 

3. What is the bitness of your processor/OS?

Kirk L. | Applications Engineer | National Instruments
0 Kudos
Message 31 of 36
(1,513 Views)

Hi Kirk

 

Thanks for your interest.

 

- The error is when the application is run on a standard PC under Win7 (no other NI products or development); runs fine on my development environment from which I removed all NI products (inc. the GAC) and re-installed MS2013 on.

 

- orignally I only used AnyCPU. I have since tried specific build of x86 which I got working on the destination PC and x64 which I could not get to work on destination PC with either version of the NI.Common.Native.

 

- Build machine is Win8.1 x64, destination PC is Win7-SP1 x64

 

Cheers

Frank

 

0 Kudos
Message 32 of 36
(1,509 Views)

Frank,

 

Just to check: Can you run the x64 assembly on the development machine?

Kirk L. | Applications Engineer | National Instruments
0 Kudos
Message 33 of 36
(1,491 Views)

Hi Kirk

 

Yes, when I build x64 the program runs correctly under VS2012 and standalone. When I examine standalone running image with procexp.exe it indicates "Image: 64-bit" and the NI.Common.Native is from the GAC_64 (ref attach). As a side note, I'll go quiet next week with off site training but still very much need to resolve this on my return.

 

Thanks

Frank

0 Kudos
Message 34 of 36
(1,486 Views)

Frank,

 

I would recommend running Dependency Walker on your assembly on both the development and target machines; I'd be interested to see if there's any difference. Perhaps your assembly is referencing the proper x64 dependency on your development machine but not on the deployment machine?

Kirk L. | Applications Engineer | National Instruments
Message 35 of 36
(1,473 Views)

Hi Kirk

 

Good call - thanks. Was missing msvcr100.dll.

 

Once added everything runs without errors.

 

Thanks again

Frank

0 Kudos
Message 36 of 36
(1,447 Views)