Love this idea, but could you also consider correcting the current functionality issue ie: right now I was in Team Explorer - Home Workspace #2, clicked Source Control Explorer (SCE), SCE opens into Workspace #1. Same thing happens if opening SCE from the view menu.
It's not a big deal, but I sometimes forget to make sure I'm in the correct workspace before I do a get latest, and sometimes I don't want to get latest on another workspace. The current solution is in Workspace #2, so I just assume that SCE will also open into #2, rather than what it did last time.
I use VS 2015 Professional and constantly switching between TFS and Git solutions weekly. After deciding long ago to use Araxis as my file comparison / merge tool, I was really surprised when the Git source control in VS didn't support 3rd party compare tools. Not every Git user is cheap and uses freeware. Araxis is well worth the money, and can only hope that VS with Git will one day support it.
We have a lot of investment taking place on our code review platform that will enable iterative code reviews, and we will initially bring that functionality to Git (via pull requests). Improving iterative code reviews for TFVC is still on our backlog, but it is not in our 6 month plan, so we are resetting the status.
I use Copernic Desktop Search (CDS) or exactly this purpose. While the professional version is cheap, they also have a free version too. Way better then windows search and goolge desktop search. Additionally, you can index emails, office documents, PDFs and others. You do need to add a few extensions like *.cs and *.sql for CDS to support, but once you're setup, it's done.
What you're asking for is a product I believe is outside the scope of Visual Studio.
Thank you for using Visual Studio and for your commitment to improving it. We are actively evaluating whether we will be able to bring this suggestion into the product for .NET developers for the System.NullReferenceException in a future release.
We have recently made an improvement, similar to this suggestion, for debugging C++ Access Violations in Visual Studio 2015 Update 1.
Read about it here: http://blogs.msdn.com/b/visualstudioalm/archive/2015/10/29/improvement-to-debugging-c-access-violations-in-visual-studio-2015-update-1.aspx
We encourage you to continue to comment on and vote for this UserVoice item to share any additional feedback that you have for this suggestion.
Visual Studio Diagnostics