Today we had an issue at a client site while setting up Team Foundation Server. They had Visual Studio Professional edition installed and TFS installed in a domain.
The particular user we were using was setup within a group that was a member of the Team Foundation Server Adminstrators group and they were able to create new Team Projects.
When it came to opening / creating a solution in Source Control, none of the source control options showed up. For example:

In Source Control Explorer, all the context menus said “No Commands Available” and everything was greyed out.

When creating a new project / solution, the Add solution to Source Control was missing.
The Solution
After a sheepish call for help to Mitch, we discovered that the current source control plug-in was set to None instead of Visual Studio Team Foundation Server.
So the fix for this is to go to Tools | Options | Source Control | Plug-In Selections and select Visual Studio Team Foundation Server. Select OK then try Source Control Explorer again.

Now you should have access to the correct context menus and source control check-in policies.

47 Comments
Thank you for turning my support task into a 10 second chuckle.
Great&Thank you! I think I’ve saved a lot of time.Greetings from Germany.Adam
Saved me a lot of time - thanks
You saved me and someone else a lot of time. Thanks
Hi Grant,Thanks for the tip - very useful. Now another question: same setup (dev with VS Professional - member of TFS admin group + TFS in the domain). How to enable profiling?Thanks!
MikeS - I believe you only get Static Code Analyze/Profiliing/Unit Testing with "Visual Studio Team Edition for Software Developers", not with the base Visual Studio Professional.See this for more info.http://msdn.microsoft.com/vstudio/teamsystem/products/compare/default.aspx
Thanks! You saved me from making the same call.
Thanks that was an easy fix…
Thanks mate! This post saved me a ton of time.
Thnaks mate! A real "Duh!" problem!!!CheersPeter
Thanks , this is really useful
Thanks for that, saved me wasting time hunting down the problem…
You are the man, saved me LOTS of time!
Thanks, you saved me lots of time.
Great! Thank you for this message, it’s really helpfull!+5!
Thanks for this post, It saved my time
Thanks.. simple solution to a simple but not-so-obvious problem.
thanks
I guess the praise shall go on and on. I wish I had found this posting days ago. What a simple fix (if you know what you’re doing
I thought I had a major setup problem on my hands. Google sent me here, from here to tools to options to happy days!
Awesome. You saved so much time for lot of folks like me.
Thanx alot alot and alot
Thanks a bunch, you saved few of us a good bit of grief. It is a shame Microsoft not make this obvious in any of their support docs.
Thanks for saving my morning!
Thank you, this saved me a lot of time!
Another "Thank you." We’ve got a couple of MCS’s on our project, so maybe I’ll ask them to forward the idea that the underlying command processor message might, check, and instead, say "No Source Control Plug-In selected." Might be a good reason why that wouldn’t work, but maybe not. Can’t hurt to ask…
Thank you. Re-installed VS a couple of times trying to fix this ; ) Should have Googled a bit 1st.
I also have to thank you very much for the time-saver post! Thanks and congratulations!
You are my savior! i tried installing and uninstalling so many times and consulting TFS expert to no avail. Ur post saved me!
Brilliant! Thanks. Just as for others, you saved me a lot of time.
Nicely written and great screen shots. I appreciate the time you took to publish this information, you saved my sanity!
Big thanx from Ekaterinburg, Russia! You save me from re-installing VS
Many thanks! I know you wrote this over a year ago, but we hit it just now. You saved us hair pulling.
Many Thanks !! You saved me a lot of time
Maybe we can get the TFS developers team to set the default to Team Foundation Server since it seems to be a very common problem.Thanks Grant!
Excellent. Good job and thank you
Thanks Mate..you saved my day
Thanks. You solved my problem.
Thanks Grant. You saved me wasting time finding the solution. You’d think that when you select Connect to Team Foundation Server, you’d want to use TFS as your source control choice.
Big problem small solutions…Thanks a lot…:).
Thanks for this good and right to the point answer!
So I would not get lost in the TFS.
Really saving me a lot of time!!!
I’ve already selected TFS as the source control plugin, bug “no commands available” still there
Thanks.That was quick. We thought of reinstalling the entire VS. Saved me lot of time.
Thank you.
Quick solution.
Saved me a few hours.
Thanks a lot
Thanks, this was great and helped me a ton!
Thanks, I was tearing my hair out before reading your post.