How LabView searches for .NET assemblies?

[pericles]

I believe, that you are right speaking about MSVCR90: though we discuss the behaviour of NET assembly and not the DLL the first error I receive in the Test Stand is the cresh message from LabView pointing to the MVSCR90. It appears BEFORE the VI loads any assembly at all. I searched for MVSCR90 on the computer and found a lot of them: a gread deal is situated in the C:\Windows, but there is a MSVCR90.dll among NI moduls, in RT Images. The version of this DLL corresponds to that in the error message. Does it mean I (the admin) have to deinstall RT Image module? 

[Jo_Winkler]

Hi pericles,

in my opinion the MVSCR90.dll usually belongs to the vc90.crt manifest.

The location: C:\WINDOWS\WinSxS\x86_Microsoft.VC90.CRT…

I don't know, why there are a lot of them on your system.

I'm also confused, why there is one in a RT Image... it makes no sense to me...

It could be a solution to register that "broken" MVSCR90.dll file with the "GACutil.exe".

(with the manifest vc90.crt)

http://msdn.microsoft.com/de-de/library/ex0ss12c%28v=VS.100%29.aspx

But you have to be an admin, to register files with GACutil.exe. (it´s the same, like putting

.net assemblies in the GAC)

I hope your admin can do that for you.

regards

[pericles]

Hi,

as far as I'm not an admin I have to explain the admin what and why to do. I think it is important to find out which MSVCR90.DLL is the proper one and why LabView takes the false (if it is a reason for the error). There are 2 versions of Microsoft Visual C++ studio (2009 and 2010) - maybe it is a reason that 2 MVSCR are on the computer.I asked a NI engineer and I'm waiting for an answer. Thank you in any case for your ideas 🙂