SQL Server 2022 version 16 about reportingservicestools HOT 7 OPEN

@Petebro-MSFT is looking into it

from reportingservicestools.

Not as-is but if you change the end of Libraries/library.ps1 from
/// <summary> /// SQL Server vNext /// </summary> SQLServervNext = 15
to
/// <summary> /// SQL Server vNext /// </summary> SQLServervNext = 16

or add another entry for SQL 2022 if you need this to manage 2016, 2019 (both seem to use 15) and 2022 which uses 16 it seems to work fine

from reportingservicestools.

Unfortunately Powershell does not allow you to patch in a new ENUM over the one they put in for Microsoft.ReportingServicesTools.SqlServerVersion, so we're SOL until a kind maintainer takes pity and updates here. See additional tickets here that haven't gotten traction either: #394

For now, the only thing I can come up with is cloning a version of this repo down, adding the missing enum type, and installing the module from local instead of github / powershell package stores. Kinda sucks for automation purposes, but we haven't had much luck getting the change made here in almost a year...

from reportingservicestools.

Made a PR to try and get some attention from an MS dev, maybe we can get this fixed finally.

from reportingservicestools.

They merged it! But looks like the build is outdated / needs fixed. @Petebro-MSFT mentioned taking a look at that, so hopefully we'll get a new version here soon!

from reportingservicestools.

@jtarquino any chance we can get 0.0.9.0 released to Powershell Gallery? It looks like the build usually did that in past successful ones, but we didn't get a good build through it yet even though its tagged appropriately to do so, etc.

from reportingservicestools.