Install And Release

Install Surfaces

Use one of these installed-user surfaces:

• VS Code Marketplace listing under svelderrainruiz.vi-history-suite
• code --install-extension svelderrainruiz.vi-history-suite
• exact released VSIX from the matching GitHub release
• packaged bundled docs through VI History: Open Documentation or the history-panel Open docs action

Current runtime contract for this build:

• Windows defaults to local LabVIEWCLI when the persisted provider is absent
• run VI History: Set Up Comparison Runtime from the Command Palette before expecting vihs to resolve
• choose or change provider, LabVIEW year, and bitness with vihs
• if VS Code was already open when vihs or the generated settings CLI changed settings, reload or restart only if stale facts remain
• run vihs --validate before the first compare on a fresh machine
• opening documentation or selecting the extension does not start Git history work, GitHub authorization, LabVIEW, or LabVIEWCLI
• if Docker is selected, confirm docker info works in the same session that runs VS Code

LabVIEW support matrix and short installed-user guides:

• README
• First-run guide
• Troubleshooting guide

First-time Marketplace, first-run, and source-evaluation feedback is collected in the public onboarding tracker: issue #12.

Useful feedback includes the install surface, extension version, VS Code version, first command or action attempted, and the first stale link, unexpected prompt, or blocked step.

Release Procedure Summary

Use the Marketplace listing for everyday installs or the exact released VSIX when you need the retained tagged build.

Quick verification flow:

1. install the extension from the Marketplace, with code --install-extension, or from the exact released VSIX
2. open or restart VS Code once after installation
3. run VI History: Set Up Comparison Runtime from the Command Palette
4. open an integrated terminal and run vihs
5. choose or confirm the provider, LabVIEW year, and bitness
6. run vihs --validate
7. if VS Code was already open when vihs or the generated settings CLI changed settings, reload or restart the window only if stale facts remain
8. open VI History on the selected VI inside a trusted Git workspace; eligibility is evaluated for that file
9. select exactly two retained revisions with the commit checkboxes
10. review the explicit compare preflight section and choose Compare
11. use Open docs if you need the version-matched installed guide