Anyone have any "lessons learned" from changing from 32-bit to 64-bit LabVIEW?

[Jay14159265]

I found it easy to switch back and fourth between 32 and 64 bit LabVIEW on the same code base and machine when developing. If you are using the same code repo the LabVIEW IDE will compile the code to either 32 or 64 bit for use in that particular IDE. If you switch from 32 bit to 64 it can take a bit to re-compile, depending on project size, but it does this in 'the background' so you will sometimes run your main VI and noting will work for a bit because its re-compiling the entire repo. 

[altenbach]

Long ago when everything was still 32bit, I create 32bit and 64bit versions of my fortran dll.

Using an conditional disable structure, I create N copies for parallel calling on first run (if they don't exist), then call the dll via filename input.

[LVNinja]

Recently one of my programs (made on LV 2020 32 bits) stopped working when the deparment upgrated to Win 11. It uses a Measurement Computing USB daq and another USB/RS232 converter. 

I recompiled the code for LV 64, reinstalled Measurement Computing driver and upgraded the USB/RS232 driver. 

I also had problem in making the EXE find the dll (in the 32 bit the DLL was under the folder Support). 

The work around solution was to  move the dll to the same location as the exe file. 

I'm not sure if this is because of Win 11 or any configuration on the exe generation, but that's the only way I made it work.