.net objects in code, DLL and portability

[kretinga]

Hi

Does any one know if there would be any portability issues when converting LabVIEW code containing .NET objects into DLL? The DLLs would be distributed most likely across Windows 7 and 10 desktops. For example, do the targets need to have specific run time engine of .NET? I am not familiar with .NET but I would imagine that if I would like use .NET methods I would need to make sure that targets have the minimum version which is stated in MSDN?

[ikaiser · Accepted solution]

Hello kretinga,

I can only answer your questions partially:

• .NET is downwards compatible up to a certain degree. Functions introduced or changed in an newer version will not work with an older version.
• .NET is installed with Windows by default. E.g. .NET 3.5 is installed on Windows 7, 4.5 on 8, 4.6...4.7.2 on Windows 10. See this table for detailed information: .NET Framework versions and dependencies
• The "minimum" version you are aiming for is either 3.5 (as pre-installed with Windows 7, and available up to current Windows 10 v1809), or 4.7.2, as this is pre-installed with Windows 10 1089 and available down to Windows 7.

Does this answer your question a bit?

[kretinga]

Thank you, this has been very helpful 

[ikaiser]

Thank you for reporting back. Good to know I could help 🙂