This one is absolutely on our list to give to you, but we don’t have any timelines yet.
Until we deliver this feature, you can still work with work items in Excel using one of these workarounds
1. Start the excel export from Visual Studio (any version) in case you have a VS installation up and running.
2. Download the Office Integration (https://www.microsoft.com/en-us/download/details.aspx?id=49992) and start the Excel integration from Excel
Visit msdn for more info: https://msdn.microsoft.com/Library/vs/alm/work/office/bulk-add-modify-work-items-excel
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
Please stop marking things as progressing when they do NOT address the request.
1,379 votes43 comments · Visual Studio IDE » Version Control (Git/TFVC) · Flag idea as inappropriate… · Admin →
This is a great idea! We completely understand how auto-switching SCC providers would help increase your productivity. Although we plan to make this available to you in the near future, we are still in the planning process and may reach out for your feedback as we start to define how tackle this problem. We will check back as soon as possible with any updates to this request. Allison Buchholtz-Au: VS Program Manager
Hello supporters of this suggestion
We are considering the possibility of a solution to this issue for a future release of Visual Studio.
One possibility under discussion is that the default folders would not be created until they are first used, giving users the opportunity to specify their own location at that moment, and have it stored in the (existing) preferences location.
Feedback on the thread below is welcome,
Program Manager, Visual Studio IDE Team