Can not call assembly "NationalInstruments.UI.Styles3D"

[Youngkey 168]

I got problem while I install my program. I developed a program with Measurement Studio 7.1 and C# in Visual Studio.NET. I made install program with Visual Studio.NET too. My program is installed successfully, but if I run it, I got message "Can not access assembly or components of the assembley 'NationalInstruments.UI.Styles3D.' I verified that the installation program copied 'NationalInstruments.UI.Styles3D.dll' into installed directory. The detailed information indicates that this error may be related LedStyle.

I have been developing several programs with Measurement Studio and distributed successfuly. This time I firstly used MS.NET waveformgraph instead of activeX waveformgraph. I also tried MS.NET Indicators. Other than that, everything is the same.

I included CWUI_OCX.msm and NIMeasDLL.msm in the project.

I would like to listen to your comments.

[Youngkey 168]

In addition, I installed VS.NET and MS.NET in the target computer, and now the installed program works. I think it means I have some merge modules to include. Or the installation of merge moudle was not successful. Please let me know, which merge module should I add. As I discussed, I already added CWUI_OCX.msm and NIMesaDll.msm.

[Elton Wells]

You do not need to use CWUI_OCX.msm if you are only installing the Measurement Studio .NET assemblies. CWUI_OCX.msm contains the Measurement Studio UI ActiveX controls, and none of the Measurement Studio .NET libraries depend on the UI ActiveX controls.

I suspect that the problem is that your installer is missing the VC and VC++ runtime merge modules. This was a bug in the Measurement Studio UI merge module in Measurement Studio 7.1. For more information, see the Knowledge Base article "FileNotFoundException When Deploying Measurement Studio .NET Applications that use User Interface c... Please try the workaround that is documented in this article and see if it resolves the issue.

- Elton

[Elton Wells]

Assuming that the problem is related to what I described in my previous post, it would have worked in this case because VS.NET installs the VC and VC++ runtimes.

- Elton