- #WHAT YEAR WAS WINPCSIGN BASIC 14.0 FULL VERSION#
- #WHAT YEAR WAS WINPCSIGN BASIC 14.0 UPDATE#
- #WHAT YEAR WAS WINPCSIGN BASIC 14.0 FULL#
The old syntax was one that didn’t have both a from and a to-part and was a simple version string like 16.0. Since minor version numbers are supported in version ranges in Visual Studio 2019, it means that the old syntax for specifying versions should no longer be used.
#WHAT YEAR WAS WINPCSIGN BASIC 14.0 UPDATE#
To do that, I would update the version range to be something like [14.0, 16.1) to express that from version 16.1 and beyond the extension isn’t supported. Now I must make sure my extension cannot be installed in that version to avoid the two similar features from colliding. Finally, they release the feature as part of an update to Visual Studio 2019. Let’s imagine that I wrote an extension with a feature that users have been asking the Visual Studio team to build into the official product. As of this writing, the are no updates released for Visual Studio 2019, but we will be able to write version ranges like [16.1, 17.0). In Visual Studio 2019 we can finally start using the minor version and forget about the build number. Why not just write 15.1 instead of 3? In Visual Studio 2017 and earlier, this was due to an implementation detail and we therefore had to keep a 0 as the minor version and write out the long build number. To do that, the version range must reflect the build number of version 15.1 and could look like [3, 17.0).
#WHAT YEAR WAS WINPCSIGN BASIC 14.0 FULL#
Get the version numbers from this full list of Visual Studio versions and replace the minor version with 0 if you need to use it in an extension’s version range.Īn extension can use an API introduced in version 15.1 but should make sure it can’t be installed on older versions to avoid runtime errors.
#WHAT YEAR WAS WINPCSIGN BASIC 14.0 FULL VERSION#
When an update to Visual Studio 2017 is shipped, it maintains its major and minor version, but the build and revision numbers change.įor instance, the full version of Visual Studio 2017 version 15.1 was 3.0. This version range syntax was introduced in Visual Studio 2015 (version 14.0). The entire version range [14.0, 17.0) therefore means from, and including version 14.0 – up to, but not including version 17.0. It can be read like up to, but not including version 17.0. A parenthesis means edge exclusive and will therefore not include the 17.0 version number. The last part is called the to-part and consists of the version number 17.0 followed by a parenthesis. You can read it like from and including version 14.0. Let’s call this the from-part of the version range. It starts with a square bracket meaning edge inclusive which is then followed by 14.0. In an extension that supports version 14.0, 15.0 and 16.0 of Visual Studio, express the version range like this [14.0, 17.0). Whether or not it made things less confusing in the end is up to you to decide. The real reason for skipping 13.0 was the believe that it would be confused with Visual Studio 2013 which was the current latest version at the time. That’s what I always thought, but then I started asking around and it turns out I was wrong. You may be wondering why version 13.0 was skipped or attribute it to being an unlucky number in some cultures. Version 113.0 in the year 2213 will be the closest match. If Visual Studio continues to follow a release cadence of roughly every 2 years, then there will never again be a version that matches its name. Here’s a list of versions and names to illustrate how coincidental it was: Version The fact that version 10.0 of Visual Studio was released in 2010 was coincidental, and made it seem like the version number followed the year of its release and therefore its name. The 10 th version of Visual Studio was released in the year 2010 and was given the name Visual Studio 2010. Let’s start by separating the version of Visual Studio from its name which can be a bit confusing. The syntax with mismatching braces may initially seem a bit odd and what exactly do those numbers refer to? Let’s unravel the mystery of the Visual Studio version ranges. A version range looks like this [14.0, 17.0) and specifies the minimum and maximum version of Visual Studio as well as if the edges are included or excluded. Extension authors use visual Studio version ranges to specify what versions of Visual Studio their extensions support.