NationalInstrumnets.UI.Internal.WaveformPlotElement threw an exception

[Steve_InMA]

Thanks for the article, but I don't think this is related to what we're seeing.  We're using Measurement Studio 2012, Version 12.0.0.318.   That's what Visual Stodio 2010 reports. 

The NI dlls I'm building with are: 

NationalInstruments.Analysis.Professional.dll V12.0.40.318

NationalInstruments.Common.dll V12.0.40.253

NationalInstruments.Common.Native.dll V12.0.40.253

NationalInstruments.UI.Design.dll V12.0.40.318

NationalInstruments.UI.dll V12.0.40.318

NationalInstruments.UI.Styles3D.dll V12.0.40.318

NationalInstruments.UI.WindowsForms.dll V12.0.40.318

I believe these are all from MStudio 2012, correct? 

I may be totally off track so feel free to correct me if I am, but it seems what's happening is that the NI dlls we are using do not play well with the C++ runtime that came installed on the Win 8 machine and that the Win 8 machine will not allow me to install a previous version of the C++ runtime (which is what vcredist_x86.exe tries to do). 

I agree that what we are seeing has to do with differing versions of the C++ runtime.  Will the NI dlls above run with the C++ runtime that comes on a Win 8 machine? 

I have limited access to the only Win 8 machine we have but I will try to get the full text of the error message for you.

-Steve

[Steve_InMA]

Daniel, 

I'm attaching the full text of the exception. 

-Steve

[Daniel-E]

Steve, 

When you get the chance, could you find out what version of the C++ Runtime you have on the Windows 8 machine? You should be able to find out by going to Control Panel > Programs and Features, and looking for things that say "Microsoft C++ Runtime".  That might help us narrow down whether the problem is compatibility with NI DLLs or something else. I suspect the DLL's would be compatible with newer versions of the runtime, but it's something I can research further once I know what version we're looking at.

[Daniel-E]

Steve,

Another thing we can try is getting a fusion log, which will give us a bit more information about what exactly is failing to load. Here's a page on how to use the fusion log utility: https://decibel.ni.com/content/people/nickb/blog/2009/06/16/using-fusion-logs-to-debug-net-assembly-...

And to be clear, we'll be doing this on the runtime (Win8) machine.

Also, I realized that I never asked whether the Windows 8 machine was 32-bit or 64-bit. Could you clarify that for me? It might help with the troubleshooting process.

Thanks!

[AlbertJ]

Hi All,

along the same lines...

I am deploying a asoftware that uses a lot of NI components (measurement studio 2010).  When  use visual studio to build a "SETUP" wizard project what options should I check or what files should I include so that the program runs right the first time.

Currently I nned to send the "vcredist_x86.exe" file along with the "setup.exe" file and ask the user installing the software to run both executables otherwise I get the error related to this thread.

I should also mention that the program is being installed in W7 machines.

Thank you for your help.

[Daniel-E]

AlbertJ,

When you build the project, what CPU are you targeting for? Also, for both the development system and runtime system, are they 32-bit Windows or 64-bit? 

These issues usually arise from the proper merge modules not being included in the build--for many modules, there is a 32-bit and 64-bit version, and if the wrong version is included in the build, the project may not run properly on the target system. 

Also, if your project uses network shared variables, this KnowledgeBase article might be applicable: http://digital.ni.com/public.nsf/allkb/F24E24F4A681689A862577F9006754EC?OpenDocument

[Steve_InMA]

Thanks Daniel, 

I will do this... as soon as the machine comes back.

The only Win 8 machine we have is off site for a while.  It should be back in about 1.5 weeks.  When its back I'll forward the info you asked for.  Sorry for the delay on this.

-Steve

[AlbertJ]

Hi Daniel,

My Platform Target is x86.

The development computer system and the target computer system are both 32 bit.

Thank you for looking into this.

[Daniel-E]

Steve--sounds good to me. Just let us know once you have that information and we can look into it further.

Albert--The vcredist_x86.exe should just install the latest version of the C++ Runtime. Is it necessary for you to run this file every time you install a new deployed build on a machine, or only the first time you deploy onto a specific machine? I would expect that once the C++ runtime files have been installed for a machine, vcredist_x86 would not need to be run again. Is this the behavior you're seeing?

Also, you should be able to include that executable as part of the installer when you build it in Visual Studio. Here's an article from Microsoft on that process: http://support.microsoft.com/kb/307353

I hope this helps, let me know if you need any more assistance!

[AlbertJ]

Hi Daniel,

You are right only the first time.  For instance if I did this when installing software A, I would not do this when installing software B.  The problem is that if you unistall software A, then somehow the "vcredist_x86.exe" gets unstalled as well.  Our temporary solution is to have the "vcredist_x86.exe" in a public server and ask the end user to run that file if they see the error mentioned on this thread.