LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Problems loading 32-bit .NET assembly when 64-bit assembly with the same name is in GAC

I have a 32-bit .NET assembly which opens fine on my colleague's PC using LV 2018 32-bit. However, if I try to open it using the same on my PC it fails with the following message:

mattbaker_0-1627471351381.png

 

My colleague's PC does not have the newer 3rd-party 64-bit software and assemblies installed and only has the older 32-bit ones.

 

I think this is due to having a 64-bit .NET assembly with the same name loaded into the GAC, but not certain. Could it be that LV is trying to automatically promote it to the latest version, but then fails as the later version is 64-bit. Has anyone else found a workaround for this?

I need to maintain software that uses the older 32-bit assembly before switching over to the newer 64-bit assembly which is automatically installed to the GAC as part of the BarTender 2021 install.

 

The 64-bit GAC assemblies load fine in the 64-bit version of LV as expected.

 

Also, any reason why LabVIEW appears to be showing 64-bit assemblies in a 32-bit environment?

mattbaker_0-1627471996957.png

 

gacutil -l

 

mattbaker_0-1627472396690.png

 

 



Using LV2018 32 bit

Highly recommended open source screen capture software (useful for bug reports).

https://getsharex.com/
0 Kudos
Message 1 of 2
(108 Views)

Also tried this after manually installing the 32-bit version to the GAC: https://zone.ni.com/reference/en-XX/help/371361R-01/lvhowto/net_specifying_assembly_version/

It seems to be attempting to use the version specified, but the load still fails.



Using LV2018 32 bit

Highly recommended open source screen capture software (useful for bug reports).

https://getsharex.com/
0 Kudos
Message 2 of 2
(89 Views)