Thank you all for your continued feedback.
In response to some recent feedback, we are happy to share that the SlowCheetah extension is officially supported by Microsoft and the Visual Studio team. Part of the reasoning behind moving it under the Microsoft repository on GitHub was to be able to maintain the extension moving forward. We understand many of you would love to see this integrated in the product. This idea is still under consideration and we will share the decision as soon as we can. We thank you for your patience.
Thanks for the typo catch! We did intend to say the NuGet and VSIX name had been changed to Microsoft.VisualStudio.SlowCheetah.
Is SlowCheetah an officially supported extension by Microsoft?
@Anonymous, the explanation is quite simple: for .NET vNext a future Visual Studio versions, Microsoft intends to replace the XML-based configuration system (and replace MSBuild too), and to use JSON config files for new projects in the future. Sure, they will be supported in the future, but not developed further.
This, combined with the fact that the SlowCheetah author was promoted to some management position in Microsoft, explains why config transforms are not built-in in VS2015.
A similar config transform should exist and should be built-in in the new JSON-based configuration system that will replaced the current XML config files in .NET.
MSBuild, csproj and XML .configs will become obsolete in the future, but the core problem solevd by Slow Cheetah remains.
Indeed this would be a very useful feature.
We all know that Microsoft wants to change the config file format in .NET vNext (replacing XML with JSON or environment variables), but for thousand of existing projects what is currently offered by SlowCheetah extension is very useful.
SlowCheetah was implemented by a Microsoft employee which is now a Senior Program Manager, and announced that is no longer has time to maintain it.. :(Tudor Turcu supported this idea ·
Slow Cheetah should be incorporated in Visual Studio - config transforms for any XML file would be very useful in a lot of situations.
The progress bar is again visible in the Update 4 for VS 2013 (they made it much thicker again so no it's possible to see the progress without a loupe)