Closed dkiehl-zz closed 4 years ago
Latest platform is in the latest app - if that is 16.0 - then that is what it is. I think 17.0 insider builds also have 16.0 platform - don't think about it.
The essence here is, that we do NOT release platforms. We release a platform together with an app - and we always reference the application version number.
Send me the information about the hotfix you are talking about?
16.1 on prem is
Get-BCArtifactUrl -type OnPrem -version '16.1' -country w1
Application version number 16.1.12629.12805 (stamped inside the database) Platform version number 16.0.12630.12758 (version number of the service tier exe file)
I don't know why the headlines in the article is different, but these are the actual version numbers and with artifacts you always go for the application version number.
So if you need some 16.2 - grab latest 16.2 - and the platform in there is what you are looking for.
The above is still giving you platform 16.0 (not 16.1). The issue that was resolved with 16.1 is not resolved.
Download the DVD in the article - unpack and check the exe file - 16.0.12630.12758. If it is fixed in the DVD, then it is fixed in the artifacts - that isn't anything I have control over.
And again - even if you download 17.x insider build - platform exe files are 16.0.x.y
Trying to build a new container with the latest 16.3 app and platform available but I am getting 16.3 for the app, and 16.0 for the platform.
Trying using the -includePlatform option on Download-Artifacts but it didn't make a difference.
There is a hotfix that was released in platform 16.2 that I need in my container but am having no luck.
Any suggestions?