.NET Assembly and ULx library

[User_01_LB]

Hello,

Since I started using LabVIEW and the ULx for NI LabVIEW library, I have always received the same warning when I load my own VIs that use blocks from this library.

The warning is as follows:

Load warning summary

And when I look at the details, all my blocks that I use are searched for in one folder but are in another one.

Load and Save Warning List

It's not a big issue; I attempted a Mass Compile by pointing to the vi.lib/ULx folder, but it does not appear to have made any difference. If I understand correctly, this is a version issue, where this library was designed with an older version of LabVIEW?

Do you have any idea how I could remove these warnings? Or do you know if it's possible to prevent this pop-up from appearing every time I open my VI?

Thank you and have a great day!

[ZYOng]

Try saving this as a "<project-name>.lvproj.config" to the same directory as your lvproj.

<?xml version="1.0" encoding="utf-8"?>
<configuration>
  <runtime>
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">

      <!-- Force exactly 2.30.0.0 -->
      <dependentAssembly>
        <assemblyIdentity name="ULx_LV"
                          publicKeyToken="null"
                          culture="neutral" />
        <!-- If any other version is requested, redirect to 2.30.0.0 -->
        <bindingRedirect oldVersion="0.0.0.0-65535.65535.65535.65535"
                         newVersion="2.30.0.0" />
        <!-- Tell .NET where to find it -->
        <codeBase version="2.30.0.0"
                  href="file:///C:/Program Files (x86)/National%20Instruments/LabVIEW%202024/vi.lib/ULx/ULx_LV.dll" />
      </dependentAssembly>

    </assemblyBinding>
  </runtime>
</configuration>

Reference: Specifying Which Version of a .NET Assembly to Use

[User_01_LB]

Hi ZYOng, thank you for the reply !

Unfortunately this solution did not work. Another approach that could maybe work is to locally modify the VIs from vi.lib and save them in the project folder ?

I don't know how to do that as I don't have the permission to modify the LLB, but create a local copy on my computer would be a solution that would solve this issue, right ?

Thanks

[rolfk]

The LabVIEW version is not likely the real problem. But the fact that it was created in a 32-bit LabVIEW version and you are loading it from a 64-bit LabVIEW version.

(C:\Program Files (x86)\.. in the expected path and C:\Program Files\.. in the found path.