Join GitHub today
Add Windows SDK 16299 to VS2019 image #770
So VS 2019 is "stable" and 16299 is the latest stable version? 18362 is a preview version? So why would we put the preview in the stable channel? I don't think I mind having 18362 as an option, not the only option. If I am not ready to take a dependency on preview parts, that puts me in a bad situation, no?
@alepauly thanks for merging... keep in mind that adding support for 18362 which would be a good call as well doesn't really solve the root issue. Libraries need to be able to build based on older UWP SDK's because if I build for 18362 then any downstream app that consumes my library would only be able to target back to 18362. When a library builds for 16299 (which is where netstandard2.0 support was added) it allows app developers to target minimum support for that version and build for a newer version. Which of course is helpful on account of the fact that a lot of Enterprises are slow to adopt updates.
referenced this pull request
May 14, 2019
@glennawatson - We normally roll out new images every three weeks. These changes will make it in the images we start rolling out next week, so assuming no delays you'll see them in all Azure DevOps orgs during the week of May 27. It takes about a week from image generation for images to reach all orgs.
@dansiegel - thanks for the info, we'll keep that in mind when we're ready to add 18362.