.NET DLL location

[jyang72211]

Within the vi, a .NET DLL is used.  How do I verify what DLL is used and its location?  I want to make sure that I am using the correct DLL.  When I right-click on the .net reference and browse, I only get what is available within the DLL. 

[D-Cubed]

Hi jyang72211,

How are you accessing the .NET DLL?  Are you creating a constructor node then choosing a .NET class?  If you have the name of the .NET class you're using, e.g. "Microsoft.WindowsMobile.DirectX.Direct3D.BaseTexture," then you can look up the DLL which contains it by searching for it on http://msdn.microsoft.com/en-us/library/ . I have attached a picture of where to locate the name of the DLL on the above website.

Best Regards,

[jyang72211]

Yes, I am using a constructor node to access the DLL.  The DLL is made by someone else on the team.  We have to place that DLL in specified location.  I just want to know where that location is, since that DLL is at mulitple places.  The DLL is not a built in Microsoft DLL. 

[zou]

Take a look Global Assembly Cache (GAC):

https://www.ni.com/docs/en-US/bundle/labview/page/using-net-assemblies-with-labview.html

Check C:\Windows\assembly

and C:\C:\WINDOWS\Microsoft.NET\assembly

See if you can find your dll.

[jcoreyw1969]

I'm wondering if you found a method of finding exactly to which dll file an existing constructor node points.

[jcoreyw1969]

If he found his dll in the GAC, how does he know that's actually the file that the constructor node is using?

[D-Cubed]

There is no way to extract the exact file your constructor is using unless you chose the DLL by browsing to it from a known location.  Is the main problem here conflicting versions of a DLL having a single name?

Regards,

[jcoreyw1969]

Yes. Unfortunately I have several versions of a dll from Agilent and for some reason I also have duplicates that reside in several locations on the C: drive. To make matters worse, I run common code (from a server) on several PCs, but the dll file is not on the server, it's on each PC's C: drive.

So it's not a big deal. I was just trying to figure out on one of those PCs which version and actual copy of the dll was being used. I should probably move the dll to the server.

Thanks,

Corey