LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

1386 error with Dotnet 2.0 DLL config file doesn't work

thank-you so much!

 

I attached a simple project which includes the .net constructor and first method enough to trigger the error.

I've also attached the fuslogvw.exe file, it seems to highlight a problem with

C:\Program Files (x86)\National Instruments\Shared\LabVIEW Run-Time\2014\NationalInstruments.LabVIEW140.dll

I checked that file it's present & compatible with x86 & x64.

mmm...

 

 

 

0 Kudos
Message 11 of 15
(872 Views)

Your attachment is missing the example VI "SAS_Reset".

0 Kudos
Message 12 of 15
(862 Views)

I created a very, very simple example that doesn't create an error in the TopCon constructor. I'm not sure what API you are using but perhaps you could start with this base and then attach a faulty use case?

Message 13 of 15
(857 Views)

I created a very, very simple example that doesn't create an error in the Topcon constructor. I'm not sure what API you are using but perhaps you could start with this base and then attach a faulty use case?

Message 14 of 15
(856 Views)

Tony,  Thank-you so-much!

 

Having a working demo to compare with my faulty program helped to clarify what is working & what isn't.

What I think I'vew figured out is that the problem is due to not correctly including the DLLs in the project files and build properties.

I think the DLLs need to have been added to the Builds/MyProject/data folder during the build and if it's done that way the .exe file has the correct path to find them. This is described here:

https://forums.ni.com/t5/LabVIEW/How-do-I-include-a-dll-in-a-build-specification-and-or-installer/td...

 

Adding them retrospectively to the .exe folder or windows/system32 as is recommended elsewhere for labview & other platforms doesn't seem to work in this case for some reason.

0 Kudos
Message 15 of 15
(833 Views)