I'm using the Watlow F4T drivers to control a thermal chamber. Watlow provides LabVIEW drivers and at their heart is a .NET .dll. My application runs just fine in the development environment. I created a build spec and it builds just fine. I can run the .exe in simulate mode (bypasses the Watlow drivers) with no problem. When I run the .exe with the Watlow drivers, the .exe crashes with an unknown exception. It's clearly related to the Watlow drivers (runs fine in sim mode).
In the build spec, I put the .dll in the "Always Included" category. Are there other caveats with .NET when building executables?
LV2016, 32 bit
The driver i downloaded is not .dll based.
But I'm using LV2012. Not sure about LV2015/2016. Maybe they are different.
I downloaded the latest driver for a look-see. I don't have LabVIEW access at the moment but I can see that the package does not contain a custom .NET dll in the zip. If there are .NET calls as you say then can you indicate what assembly they are statically linked to?
Is the driver joezhang downloaded the driver we are talking about, or did you download a different one?
I'm using LV2016, so it uses CLR 4.0 and thus up to .NET 4.5. I'm not able to tell if the Watlow drivers point to an earlier .NET version. The link does say that assemblies pointing to earlier versions may not work with CLR 4.0.
I'm having the same issue. I can run the driver just fine in the labview environment but when I build the application, it crashed.
I tried to move their dll to the exe but that didn't help.
Was this issue resolved? If so, could you provide a quick overview of the solution?
I ran out of time trying to figure it out so I switched to Modbus. I plan to revisit soon but can't say when.