In the traditional approach, VISA.NET Shared Components are distributed solely as part of a vendor's installer for its VISA implementation. This approach necessitates the installation of the vendor's VISA library implementation on the CI server environment, even if communication with instruments is not required at this stage.

If a developed application is intended to work with various third-party VISA implementations, and no VISA libraries are installed, it would be beneficial if it could provide only a part of the functionality or report the necessity of the VISA library.

This is a simple example of an application bypassing those limitations by using the unofficial NuGet VISA.NET Shared Components distribution, Kelary.Ivi.Visa.

.NET Standard, introduced in 2016, marked a pivotal moment in the evolution of the .NET ecosystem. Since then, many versions of .NET have emerged, diminishing the relevance of the traditional .NET Framework for new projects.

Despite these advancements, VISA.NET remains tied to .NET Framework 2.0, with no indication from the IVI Foundation of plans to embrace modern technologies.

A notable challenge is VISA.NET's limited integration into projects with contemporary .NET runtimes. However, compatibility has improved since .NET Core 2, allowing referencing of .NET Framework assemblies in compatibility mode. This suggests potential usability of the VISA.NET library and .NET Framework implementations within a modern .NET runtime.

Another challenge arises as the modern .NET runtime no longer uses the GAC, which VISA.NET relies on. This issue is mitigated by preloading VISA.NET implementations.

In this repository, an experimental .NET 8 example application showcases potential VISA.NET usage with various vendors implementations. Despite progress, successful execution is not guaranteed, as the .NET runtime may lack support for all .NET Framework APIs. Basic functions have been tested with Rohde & Schwarz and Keysight implementations, but some functions may require further testing.

We look forward to the IVI Foundation moving the VISA.NET library from the .NET Framework to the .Net Standard, which will allow VISA.NET to become not only interchangeable, but also cross-platform.

In most cases, an application built with VISA.NET Shared Components version 5.5 will work with later implementations of Shared Components. For .NET 5+ projects, the Shared Components version must match those that the implementation depends on.

Below is a non-exhaustive list of vendor-specific VISA implementations with VISA.NET support.