What are the essential DLLs for .NET Framework 4

[JamesT_Geo]

Hi,

I am wondering what the essential DLLs are for a .NET application (Framework 4). I have found the following: ni4882.dll, gpibconf.dll,  ni488config.dll, and ni488ci-2.6.0f0.dll.

Are there any more that are needed?  Is there a list of installed libraries and their functions available?

Following from this: Is it possible to include these as part of a VS2010 C# installer and have the DLLs used correctly (I'm trying to avoid overwriting legacy - 2005 vintage - NI drivers on a test system) - without the need to install the divers using NIs installer (which, I believe, would overwrite an old gpibconf.dll and cause a VB6 based legacy system to fail)?

Any help appreciated,

Thanks,

James T

[Pete.Dunc]

Hi James,

I am a little confused about what exactly you are trying to achieve.  It seems like you are making reference to the DLLs in the GPIB driver set and would like to include those in an installer, to allow you to then make C# .NET calls to the driver set.

In general it is not possible to have multiple versions of the same driver operational on a single machine.  This is due to the likelihood of conflicts between the versions.  I am not sure if this extends to the DLL calls within Measurement Studio, but typically having multiple versions is not possible.

Please let me know if I have misunderstood your question or if there is anything else I can help with.

[JamesT_Geo]

Hi Peter,

Thanks.

Yes, that answers the second part of my query.

I'm writng a VS2010 .NET application using the latest drivers and the .NET 488.2 libraries. This is to replace a legacy VB6 based system which uses the gpibconf.dll (2005 version). I can see that I cannot install the latest Measurement studio over the existing legacy system as that needs to function correctly until the .NET version is ready. There is only ONE computer connected to the devices so it must be used for both the old legacy software and the new software being tested.

Because of this I'll clone the existing system with HyperOS and then update the clone with the latest Measurement studio so the original is left as it was and can run the legacy software as needed. I can then use the clone to test and develop the .NET system.

Thanks for your clarification of this.

James