Hello everyone and thank you for the feedback. We are actively investigating ways to improve how Visual Studio handles project content. This suggestion falls into that category. Unfortunately, we will not be able to address this feedback for the Visual Studio 2015 release. We will update the community when our plans in this area have gained more clarity.
Visual Studio – VS IDE Project and Build TeamAnonymous commented
1. Have the Visual Studio team publish in Github an API specification for what Visual Studio does with project files.
2. Ask for community feedback.
3. Use that as the basis for requirements for this new functilnality
This drives the Visual Studio team to build actual requirements and lay out a business case for spending $X on implementing it.
Hammer that out until it is ready to send out for a RFP.
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.Anonymous commented
5 years with not a solution from the Microsoft Visual Studio team. How many years will it take to get this changed?
Our commercial product team will either make the change within 1.5 years or close it out with a 'never to be done' status within that 1.5 years.
We'd lose many of the Fortune 1000 multinational customers we have if we left open customer requests and repeatedly stated 'we're considering it for a future version' to them.