NIbbuchanan

We had issues with DLLs in vi.lib if CLF included vi.lib as part of the path when deploying those VIs to Linux RT. We found that putting the DLL in...

I think the problem we ran into with DLLs in vi.lib is that the CLF doesn't use \DLL Path, but instead C:\Program Files\National Instruments\LabVIEW 2021\vi.lib\DLL Path. Our build process syncs...

@eyesonvis - This is also related to https://github.com/ni/grpc-labview/issues/75 in case you want to link them together.

@gregr-ni I did some testing with dll paths and here's what I found: **if I put the dll in vi.lib\gRPC\LabVIEW gRPC Library\Libraries\labview_grpc_server64.dll** - Built windows exe and DLL copied to...

I would say instead of LV returning an error or warning the user, the write should just wait internally in the DLL until the other thread is done writing and...

Thanks for the update John! Very exciting to hear this may finally be fixed. A few comments: 1. Since the change would affect low-level VIs and doesn't impact the connector...

Sounds good, thanks for investigating this! I think the DLL_Main constructor makes the most sense. Thanks!