Skip to content

Release Notes

This topic presents a summary of Nimbus 7 requirements, key features, and updates, as well as some known issues to be addressed in a future update.

Nimbus 7 includes an automatic project converter that will automatically update all relevant projects in the driver solution.

See the topic Converting Driver Projects From Earlier Versions of Nimbus for details.

  • Windows 10 or newer

  • Visual Studio 2022 or Visual Studio 2026

    Any of Community, Professional, or Enterprise editions are supported.

    For Visual Studio 2026, version 18.0.0 or later is required.

    For Visual Studio 2022, version 17.14.0 or later is required.

  • Microsoft .NET Framework 3.5

  • IVI Shared Components 3.0.3 (or newer)

  • IVI.NET Shared Components 3.0.1 (or newer)

  • .NET Framework targeting packs

    Installing Nimbus brings in the .NET Framework 4.8 targeting pack automatically, as a Visual Studio prerequisite of the extension. To target an earlier version, install that version’s targeting pack from the Visual Studio Installer under Individual components. Nimbus offers .NET Framework 4.6.2 and newer.

    No matching runtime is needed: .NET Framework 4.x updates in place, and the 4.x runtime on Windows runs anything built against an earlier 4.x.

  • A .NET SDK for each .NET version targeted — only if the IVI.NET driver targets .NET

    Visual Studio installs a single .NET SDK, the current one for that Visual Studio release, so that is the only .NET version Nimbus offers out of the box. Install the SDK for each additional version to be targeted. The SDK supplies both pieces needed: the targeting pack the driver compiles against, and the runtime that the generated unit test and console application projects run on, since those projects target the same frameworks as the driver. IVI.NET drivers may target .NET 6.0 or newer.

  • Node.js 22.12 or newer — only to build or preview the Starlight web site help output format locally. No other part of Nimbus requires it; nothing is required to serve the finished site, and nothing is required at all when GitHub builds it.

  • For drivers that use VISA for I/O communications, Nimbus 7 requires VISA Shared Components 8.0.0 and VISA.NET Shared Components 8.0.0.

    The VISA and VISA.NET Shared Components are typically installed by VISA vendor products, such as those from National Instruments or Keysight Technologies.

Nimbus includes a re-architected help generation pipeline built around Markdown templates and the Mustache template language. From a single set of templates and the help content authored in the Driver Designer, Nimbus can generate driver documentation in six output formats — a CHM file, a Microsoft Help Viewer file, Markdown, semantic HTML, MadCap Flare HTML, and a complete web site — for all three driver flavors (IVI-COM, IVI-C, and IVI.NET). The previous HTML-based template system remains fully supported.

The following table compares the two template systems.

Legacy HTML templatesMarkdown templates
Output formatsCHM and Microsoft Help ViewerCHM, Microsoft Help Viewer, Markdown, semantic HTML, MadCap Flare HTML, and a Starlight web site
AuthoringHTML, with $$TOKEN$$ substitutionMarkdown, with Mustache expressions and reusable partials
Size of the template set603 HTML files and 24 JavaScript files156 files, 119 of them Markdown
IVI.NET page file namesFreshly generated GUIDs, different on every buildReadable names that follow the API, and stable from build to build
F1 in Visual StudioThe front page onlyEvery documented type and member
Broken help linksNot detectedReported in the Error List, with navigation to the entity that owns the link
Help Viewer outputNot checkedEvery topic is verified to be indexable before the build completes
StylingFixedAuthor-supplied CSS

The practical gains are these.

  • Documentation can be published to the web, not only shipped as a file. One of the outputs is a complete documentation web site, which can be committed to a repository and built and hosted by GitHub Pages, or built locally and uploaded to any web host. Either way end users read the driver documentation in a browser, search it, and link to an individual function or property, with no CHM to download and no Help Viewer to install.
  • Templates are authored in Markdown. Help content is written in the Driver Designer as before, but customizing the templates that surround it no longer requires editing HTML and JavaScript by hand.
  • Links to help pages remain valid. Pages are named after the API they document rather than after a GUID, so a bookmark, an external link, or a cross-reference still resolves after the next build. Links created with Copy Help Link are resolved by identity and therefore survive renaming the target.
  • F1 reaches the whole API. Every documented type and member carries an F1 keyword, so F1 in the Visual Studio editor opens the page for the symbol under the cursor. IVI-C keywords are the prefixed names that appear in driver source, and IVI-COM keywords are the fully qualified names.
  • Documentation problems are reported during development. Broken and ambiguous help links, missing help content, and topics that Microsoft Help Viewer could not index are reported as driver design diagnostics, both live in Visual Studio and at build time, with configurable severity. A documentation standard can therefore be enforced in a continuous-integration build.
  • All six formats come from one source. The CHM, the Help Viewer file, and the web site are produced from the same content and cannot drift apart.

For details, see The Markdown Help Template System.

Nimbus can now write a company’s own implementation conventions into the body of every driver member, in place of the stub it generates. A code template is a ready-made body for a method or property (for IVI-C, a function or attribute), and a template set gathers a company’s templates for a driver flavor. When a driver’s template set marks a template as the default for a kind of member, every member of that kind added afterward gets the template’s body. Code templates are available for all three driver flavors (IVI-COM, IVI-C, and IVI.NET), including an IVI-C driver linked to an IVI.NET driver.

The practical gains are these.

  • Conventions go into every new member. Tracing, error handling, simulation, or any other code a company requires is written into each method, property, function, or attribute when it is added in the Driver Designer, when an instrument class is added, and when a driver is created, rather than being pasted over Nimbus’s stub by hand.
  • Existing members can be brought into line. Apply Code Template in the Driver Designer gives a member, a multiple selection, or a whole branch of the hierarchy a template’s body in one operation, with a preview of the result and a single Undo.
  • Templates are plain code. A template is an ordinary .cs or .cpp file, edited in Visual Studio with full coloring, and written into the body verbatim. There are no replacement tags to go stale when a member is renamed.
  • Nimbus’s generated code is kept. A template can keep Nimbus’s standard preamble, which Nimbus goes on maintaining as the member changes, and supply only the code that follows it, or it can supply the whole body.
  • Everyone on a driver gets the same code. The driver’s template set is copied into the driver project and kept under source control, so the defaults do not depend on what is installed on a developer’s machine.
  • Template sets are shared across drivers. A driver’s set can be saved to a machine catalog, where other drivers can switch to it, and the driver wizards and Tools -> Options choose the set a new driver starts with.

For details, see Using Code Templates.

The IVI Foundation has recently completed its work on updating the standards for IVI.NET drivers to include packaging of drivers in NuGet packages that can easily be distributed on feeds such as nuget.org. This greatly expands the usability, discoverability, and ease of distribution of IVI drivers and is the biggest step forward for IVI in many years.

Nimbus Driver Studio is the first, and only, tool that supports building NuGet-based IVI.NET drivers.

Windows desktop development has shifted massively away from .NET Framework to .NET Core. The IVI Foundation now supports targeting .NET Core 6.0 and greater so that .NET Core client applications can finally use IVI.NET drivers.

Nimbus Driver Studio is the first, and only, tool that supports building IVI.NET drivers that target .NET Core.

Multi-Targeting .NET with a Single Codebase

Section titled “Multi-Targeting .NET with a Single Codebase”

While the advantages of .NET Core-based IVI drivers is clear, it is paramount that Nimbus customers have an efficient way to maintain existing IVI.NET driver inventories. Correspondingly, end users must maintain their existing .NET Framework-based systems for many years to come. For these reasons, Nimbus now supports multi-targeting in IVI.NET driver projects. This means that the same Nimbus IVI.NET driver project customers have had for years can be used to generate the same .NET Framework driver (with the same MSI-based installer it has always had) as well as an independent .NET Core driver that targets .NET 6.0 or greater. All this can be done using a single driver source code base, which greatly simplifies long-term development and maintenance.

Nimbus Driver Studio is the first, and only, tool that supports building IVI.NET drivers that multi-target .NET Framework and .NET Core from a single code base.

Nimbus analyzes the driver design as it is edited in Visual Studio and again at build time, reporting issues such as broken help links and missing help content directly in the Error List. Each diagnostic has a configurable severity, so a given check can be treated as an error, a warning, or informational — or disable it — and enforce documentation standards in continuous-integration builds.

For details, see Driver Design Diagnostics.

  • When creating a new driver project, the option to Place solution and project in the same directory must always be chosen. Attempting to manage a Nimbus driver solution with the .sln file inside the driver project folder (or any other Nimbus project folder) could lead to unpredictable results.

  • When a driver solution is opened, there are a variety of asynchronous operations that Visual Studio performs. One important operation is NuGet restore, which populates the project with all of the critical binaries and targets it needs to operate. If Driver Designer operations are attempted before the NuGet restore completes, then strange errors such as Undefined type Int32 could result.

    In practice, this is rarely an issue, as the NuGet restore typically completes within the first few seconds of opening a solution. The status of the NuGet restore appears in the Output Window.

  • IVI-COM and IVI-C help and setup projects show “broken reference” annotations (yellow warning triangles) on the icon for their project references to the driver project. These references are required for these projects to operate, and the references are indeed intact, but MSBuild currently has a bug that manifests when any custom SDK-style project references a native (C++) project. The same driver project references appear normal in IVI.NET help and setup projects.

    These warning annotations are benign and can safely be ignored.

  • Merging of IVI.NET repeated capabilities is not currently supported in this release. All other aspects of IVI.NET repeated capabilities are fully implemented in this release.

  • Building a driver setup project from within Visual Studio fails. Setup projects must currently be built from the command line using the MSBuild command.

  • Removing nested collection-style repeated capabilities from the driver project leaves behind a driver source file and a unit test source file. These can safely be removed manually to complete the operation.

    Pacific MindWorks is working to resolve this issue in a future release.

  • A re-architected help generation pipeline based on Markdown and Mustache templates, able to generate driver help in six output formats — including a complete web site — for IVI-COM, IVI-C, and IVI.NET drivers. The previous HTML-based template system remains fully supported. New help projects use the Markdown templates by default; the legacy HTML templates remain available from the driver wizards and under Tools -> Options.
  • Driver documentation published straight to GitHub Pages. The web site output ships a workflow that GitHub runs to build and host the site, so committing it to a repository is the whole deployment — nothing to install, and nothing to build locally. Sites may be published publicly or, on GitHub Enterprise Cloud, restricted to people with access to the repository. The web site output also ships a Cloudflare configuration already named after the driver, so the site can instead be deployed to Cloudflare with Wrangler.
  • Substantially faster driver solution creation. The wizards that create a driver and its help, setup, unit test, and console application projects are dramatically quicker.
  • Substantially faster IVI.NET driver loading and editing. Opening a driver is dramatically quicker, and every edit in the Driver Designer is faster as well, since each edit validates and saves the driver.
  • Driver design diagnostics that report issues such as broken help links and missing help content, both live in Visual Studio and at build time, with per-diagnostic configurable severity.
  • F1 help for driver APIs. Generated help now carries an F1 keyword for every documented type and member, so pressing F1 in the Visual Studio editor opens the page for the symbol under the cursor.
  • Readable, stable help page file names for IVI.NET drivers, replacing the generated GUIDs used previously. Links and bookmarks to a driver’s help pages now survive a rebuild.
  • Help template selection when creating a new driver. The Projects page of the IVI-C, IVI-COM, and IVI.NET driver wizards now offers a Help template setting for the help project it creates, defaulting to the preferred template configured under Tools -> Options. Previously the template could be chosen only when adding a help project to an existing solution.
  • Documentation comments in the generated IVI-C header file. Each attribute and function declaration is now preceded by a comment block giving its summary, and, for attributes, the repeated capability it belongs to, its type, its access, and its generated accessor functions. Function comments describe every parameter and mark its direction as [Input], [Output], or [Input/Output], and enumerated types list their defined values. Function declarations are also formatted one parameter per line.
  • Customizable IVI-C driver version information. The version resource of an IVI-C driver DLL is now built from a Version.h header that Nimbus generates from a Version.h.ntt text template in the driver project, in the same way the driver header is generated from its template. Editing the template lets a driver take values such as its product name and version from elsewhere, for instance from a header shared by every component of a larger product. See Customizing the Driver Version Information.
  • Code templates, which put a company’s own implementation conventions into the bodies of new driver members in place of the stubs Nimbus generates. A driver’s template set chooses a default template for each kind of member, and Apply Code Template in the Driver Designer gives existing members a template’s body. Template sets are shared through a machine catalog, and the driver wizards and Tools -> Options choose the set a new driver starts with. Nimbus ships no templates, so drivers that do not use a template set are unaffected.
  • Support for building IVI.NET drivers that target .NET 10.
  • IVI.NET and VISA.NET package versions pinned to each Nimbus release. A new IVI.NET driver now references the package versions that release of Nimbus was built and tested against, rather than whatever the package feed reported as latest when the driver was created. The Nimbus class library sources compiled into the driver therefore always build against the API they were tested with. Newer packages can still be adopted through NuGet.
  • The full exception behind a failed Driver Designer edit is now written to the Visual Studio activity log, in addition to the error message that is displayed. Visual Studio keeps the activity log when it is started with devenv /Log.
  • Fixed a failure to install Nimbus on Visual Studio 2026 version 18.8 and newer, where a Visual Studio component that Nimbus listed as a prerequisite had been removed from the Visual Studio installer catalog.
  • Fixed an IOException that could occur when backing up a driver solution, by excluding the Visual Studio .vs cache directory from the backup.
  • Fixed handling of generic method parameter names in the IVI.NET Driver Designer.
  • Fixed an issue where building more than one driver in a single MSBuild invocation, such as a solution containing two drivers, applied the first driver’s design to every project that followed. Depending on the driver types involved, the build either failed during help generation or produced help, generated source, and setup constants for the wrong driver.
  • Fixed an issue where a C++ application project could not be added to a solution that contained only an IVI-C driver. The command reported that C++ application projects can be generated only for IVI-COM and IVI-C drivers, which is what it was being asked to do.
  • Fixed an issue in the Driver Designer and Setup Designer where an active search was lost on leaving the designer and returning to it. The search box came back empty while the tree was still filtered, and because the box already looked empty, clearing it did nothing — the only way back to an unfiltered tree was to run another search and then clear that one. The search box now restores the active search and re-runs it.
  • Fixed an issue where the IVI.NET driver wizard selected no .NET target framework on machines without the .NET 6 SDK, such as a new Visual Studio 2026 installation, and then reported that a target framework was required. The wizard now selects the newest installed .NET version and lists versions newest first.
  • Fixed an error that prevented the simulation editor in the Driver Designer from displaying.
  • Fixed an issue where new IVI.NET driver solutions built the help and setup projects in every solution configuration. As in IVI-C and IVI-COM solutions, they now build only in Release configurations.
  • Fixed an issue where F2 did not rename the selected node in the Driver Designer tree.
  • Fixed an issue where the Back and Forward buttons in the Driver Designer and Setup Designer toolbars appeared as text without icons.
  • Fixed “Failed to apply changes to workspace” and “Failed to find symbol” errors when renaming a repeated capability in a multi-targeted IVI.NET driver.
  • Fixed an IVI.NET repeated capability rename that left its IVI-C branch with the old name or a “2” suffix.
  • Fixed an IVI.NET repeated capability rename that did not rename its identifier parameters, such as probeName.
  • Fixed an error adding an IVI-C instrument class or IviLxiSync support in the Driver Settings Editor.
  • Fixed an NU1010 restore failure in a multi-targeted IVI.NET driver opened before its packages were restored.
  • Fixed a “Could not resolve IVI.NET type reference” error when linking an IVI-C driver to an IVI.NET driver with an instrument class.
  • Nimbus now supports Visual Studio 2026.
  • Fixed a bug in the IVI-COM converter where the MATLAB-related attributes were not getting removed.
  • Fix a couple of NREs in the IVI.NET converter where the converter was not checking the actual driver type.
  • Fix a converter bug where an IVI.NET driver was not checked for before trying to create assembly resolvers.
  • Fix a bug in the IVI.NET converter where the converter was not removing the usage of DrvierFrameworkVersionShortName from the 64-bit code in Setup.wxs.
  • Fixed an issue in the IVI-COM and IVI-C converters where the properties now defined in Directory.Build.props were not getting removed from the various projects.
  • Fix an issue with the definition of IVIC_ERROR_BASE that would cause error squiggles to appear on usages of the macro.
  • Fixed an exception that was thrown in some situations when converting drivers to Nimbus 7.
  • Fixed a bug in the repeated capability editor where some of the editing buttons were disabled.
  • Nimbus 7 brings support for NuGet-based IVI.NET Core drivers recently introduced by the IVI Foundation.