[BUG] Wrong version number in config.installation_history?

[ghauan]

Environment

• SQL Server Version: SQL Server 2019 CU32
• Windows Version: Windows Server 2016
• Component: Installer (Full Edition)
• Performance Monitor Version: 1.2.0

Describe the Bug

In the Full version, it looks like the config.installation_history table is not capturing the correct value under Installer Version (column: installer_version).

Specifically, the installer_version column shows 1.0.0.0, but I expected it to reflect the current Performance Monitor version (1.2.0).

(Note: I understand installer_version might be intended to represent the installer’s own version rather than the Performance Monitor version, if so, would it not also be benefitial with a column showing the version of Performance Monitor?)

Steps to Reproduce

1. Install/upgrade Performance Monitor (Full Edition) using the installer.
2. Open SSMS and query config.installation_history.
3. Check the most recent row and review the value in installer_version.

Expected Behavior

After installing/upgrading to Performance Monitor 1.2.0, the latest row in config.installation_history should show the expected version value under installer_version (or otherwise clearly reflect the correct version that column is intended to store).

Actual Behavior

The latest row in config.installation_history shows installer_version = 1.0.0.0 even after installing/upgrading to Performance Monitor 1.2.0.

Error Messages

Screenshots

Additional Context

• Did this work before? If so, what changed? Unknown / not sure yet.
• Are there any relevant SQL Server configuration settings? N/A / Unknown.
• Is SQL Server Agent running? (Yes / No)
• Are you monitoring Azure SQL DB, Azure MI, or AWS RDS? No.

IMPORTANT: If you're going to contribute code, please read the contributing guide first.

[erikdarlingdata]

Good catch! The root cause is straightforward — the version numbers in the installer's .csproj file are hardcoded to 1.0.0.0 and haven't been updated with releases:

<Version>1.0.0</Version>
<AssemblyVersion>1.0.0.0</AssemblyVersion>
<FileVersion>1.0.0.0</FileVersion>
<InformationalVersion>1.0.0</InformationalVersion>

The installer_version column in config.installation_history gets populated from AssemblyVersion, which is still 1.0.0.0. We'll update these to match the actual release version going forward.

There is also an installer_info_version column in the table that stores the InformationalVersion, which has the same problem — it's stuck at 1.0.0.