Update 2/14/2017 – I am happy to announce that we have updated the SlowCheetah extension to work with Visual Studio 2017 and 2015. You can install the extension from the VS marketplace: https://marketplace.visualstudio.com/items?itemName=WillBuikMSFT.SlowCheetah-XMLTransforms
We are also in the process of adding support for additional project and file types. For the latest development news for the extension, check out the GitHub repo: https://github.com/sayedihashimi/slow-cheetah
Please let us know if you run into any issues by reporting them at the issue tracker on SlowCheetah’s GitHub page.
Note: if you installed the preview extension for Visual Studio 2015, please be sure to remove it before installing the new one to avoid conflicts.Shane Courtrille commented
So serious question here. If 8,000 votes can be completely ignored why is there even a visualstudio.uservoice.com? The SlowCheetah support that was promised resulted in a single preview release and no bug fixes or support. I assume the assumption is people should now be using VSTS/TFS Release Management but if that's the case then it's time for Microsoft to say so.
Good news – we are adopting a plan that is very close to what is proposed in this suggestion. We will adopt a semantic versioning scheme for Visual Studio starting with Visual Studio 2017, using the major / minor numbers, based on the standard enumerated at http://semver.org.
The RTM release will be numbered 15.0, with feature updates numbered sequentially 15.1, 15.2 etc. We use a five digit number to represent the specific build number of a particular component, and that will remain the best way to identify a specific single build of the product. So in Help / About, you’ll see something like 15.1 (build 26230.0).
We hope this will simplify things somewhat, and we’ll continue to further align with the semantic versioning model as we invest in our build systems.
Thanks so much for your feedback – we appreciate it!
Tim Sneath | Visual Studio Team