v3.0.5 — fix perpetual update-available nag (read version from assembly)

Fixed — perpetual "update available" dialog after every install

PluginUpdateChecker.CurrentVersion was a hardcoded constant ("1.12.13") that nobody bumped through v1.12.14..v1.12.22. The update notifier compared the GitHub-release tag against the stale constant on every VS open, so the dialog kept firing even immediately after installing the latest VSIX.

Now the current version is read at runtime via AssemblyInformationalVersionAttribute (falling back to AssemblyName.Version). Properties/AssemblyInfo.cs is kept in sync with source.extension.vsixmanifest <Identity Version="..."/> and there's no drift.

Manifest version: v1.12.23.

Note: API line numbers

While verifying this release we ran a line-accuracy audit against o360.madfoat.com on multiple projects:

• LargeTestProject (.NET): 59/63 findings reported the correct line; 4 were off by +1, +1, +27, -2.
• WebGoat.NET: 69/75 findings reported the correct line; 6 were off by +1, +2, +3, +3, +14, +20.

These are upstream rules-engine issues — the plugin navigates faithfully to whatever line the server reports. The "wrong line is highlighted" reports tracked back to a mix of one plugin bug (fixed in v3.0.4) and several API line-offset issues (need to be filed against the rules engine).

Install

Download OffensiveVS360-v3.0.5.vsix below, close all Visual Studio instances, and double-click to install (or use Tools > Extensions > Install from VSIX...). Restart Visual Studio when prompted.

Targets: Visual Studio 2022 (Community / Professional / Enterprise), .NET Framework 4.7.2+.