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
Yep, really needed.
<thread> is not supported in /clr files with VS 2017 but <atomic> does seem to be.
I just compiled a .cpp file with /clr with #include <atomic> and it built! Mind you, I didn't actually use anything from there yet but it didn't even compile before.
Thanks for raising and voting for this suggestion.
At this point, we’d like to dive further into the specific needs your scenarios will have from the API. If you can spend a few minutes to answer the questions on this survey, we’d greatly appreciate it! Your answers will help us plan and prioritize the work required.
Program Manager, Visual Studio IDE
This would be excellent. We use Perforce for SCC and would love to have the CodeLens level of information and integration available during development.
Yes please! I'd add a vote if I had any left. +1
I'm going to un-vote my own suggestions as I missed this one:
So, go vote for that since it's got more votes already.
We could pony up thousands of dollars for Incredibuild or Electric Cloud but this should just be built-in like distcc with XCode.