TFS Source Control: No Commands Available

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:

Source Control Explorer - No Commands Available

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

New Project - No Add to Source Control

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.

Source Control Plug-In Selection dialog

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

47 Comments

  1. Paul B
    Posted June 16, 2006 at 4:55 pm | Permalink

    Thank you for turning my support task into a 10 second chuckle.

  2. Posted July 18, 2006 at 10:41 am | Permalink

    Great&Thank you! I think I’ve saved a lot of time.Greetings from Germany.Adam

  3. Allen B
    Posted July 25, 2006 at 7:27 pm | Permalink

    Saved me a lot of time - thanks

  4. garrettrs
    Posted August 22, 2006 at 2:31 pm | Permalink

    You saved me and someone else a lot of time. Thanks

  5. MikeS
    Posted August 28, 2006 at 11:43 pm | Permalink

    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!

  6. Grant
    Posted August 29, 2006 at 1:32 am | Permalink

    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

  7. JoeZ
    Posted September 13, 2006 at 7:40 pm | Permalink

    Thanks! You saved me from making the same call.

  8. Tgb
    Posted September 18, 2006 at 9:39 pm | Permalink

    Thanks that was an easy fix…

  9. US Collingwood Footy Fan
    Posted October 24, 2006 at 4:22 pm | Permalink

    Thanks mate! This post saved me a ton of time.

  10. PeterNZ
    Posted October 26, 2006 at 2:25 am | Permalink

    Thnaks mate! A real "Duh!" problem!!!CheersPeter

  11. AGP
    Posted November 7, 2006 at 12:37 pm | Permalink

    Thanks , this is really useful

  12. JayFleming
    Posted December 4, 2006 at 9:27 am | Permalink

    Thanks for that, saved me wasting time hunting down the problem…

  13. Bill
    Posted December 5, 2006 at 9:59 pm | Permalink

    You are the man, saved me LOTS of time!

  14. Nat
    Posted December 14, 2006 at 9:38 am | Permalink

    Thanks, you saved me lots of time.

  15. N'urk
    Posted January 12, 2007 at 9:57 am | Permalink

    Great! Thank you for this message, it’s really helpfull!+5!

  16. Arul
    Posted January 18, 2007 at 10:15 am | Permalink

    Thanks for this post, It saved my time

  17. Posted January 22, 2007 at 10:24 pm | Permalink

    Thanks.. simple solution to a simple but not-so-obvious problem.

  18. blu
    Posted January 24, 2007 at 2:38 pm | Permalink

    thanks

  19. kgkidd
    Posted February 6, 2007 at 6:06 pm | Permalink

    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 :-)

  20. Fred McFred
    Posted March 3, 2007 at 12:42 pm | Permalink

    I thought I had a major setup problem on my hands. Google sent me here, from here to tools to options to happy days!

  21. Ram Manthena
    Posted March 7, 2007 at 5:10 pm | Permalink

    Awesome. You saved so much time for lot of folks like me.

  22. wael
    Posted March 13, 2007 at 9:00 pm | Permalink

    Thanx alot alot and alot

  23. Anubhav Jain
    Posted March 14, 2007 at 7:03 pm | Permalink

    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.

  24. Posted March 20, 2007 at 2:39 pm | Permalink

    Thanks for saving my morning!

  25. MattMcde
    Posted May 3, 2007 at 1:45 pm | Permalink

    Thank you, this saved me a lot of time!

  26. Posted May 8, 2007 at 2:35 pm | Permalink

    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… :-)

  27. Posted May 25, 2007 at 11:32 pm | Permalink

    Thank you. Re-installed VS a couple of times trying to fix this ; ) Should have Googled a bit 1st.

  28. Rafael
    Posted May 30, 2007 at 1:02 pm | Permalink

    I also have to thank you very much for the time-saver post! Thanks and congratulations!

  29. Christina
    Posted June 6, 2007 at 4:21 pm | Permalink

    You are my savior! i tried installing and uninstalling so many times and consulting TFS expert to no avail. Ur post saved me!

  30. Sivas
    Posted June 21, 2007 at 12:51 am | Permalink

    Brilliant! Thanks. Just as for others, you saved me a lot of time.

  31. Matthew Hall
    Posted July 11, 2007 at 2:49 pm | Permalink

    Nicely written and great screen shots. I appreciate the time you took to publish this information, you saved my sanity!

  32. Renat
    Posted August 8, 2007 at 11:04 am | Permalink

    Big thanx from Ekaterinburg, Russia! You save me from re-installing VS :)

  33. Posted August 13, 2007 at 2:10 pm | Permalink

    Many thanks! I know you wrote this over a year ago, but we hit it just now. You saved us hair pulling.

  34. Pramay
    Posted September 4, 2007 at 6:01 am | Permalink

    Many Thanks !! You saved me a lot of time

  35. J Aberdeen
    Posted September 7, 2007 at 12:57 pm | Permalink

    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!

  36. Anita
    Posted September 14, 2007 at 7:26 pm | Permalink

    Excellent. Good job and thank you

  37. Praseeth
    Posted October 3, 2007 at 10:15 am | Permalink

    Thanks Mate..you saved my day :-)

  38. JMB
    Posted November 1, 2007 at 7:25 am | Permalink

    Thanks. You solved my problem.

  39. Alvin Yong
    Posted November 12, 2007 at 10:29 am | Permalink

    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.

  40. swanand raikar
    Posted November 21, 2007 at 4:35 pm | Permalink

    Big problem small solutions…Thanks a lot…:).

  41. Vincent Chen
    Posted November 27, 2007 at 2:10 am | Permalink

    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!!!

  42. dacken
    Posted December 13, 2007 at 8:24 pm | Permalink

    I’ve already selected TFS as the source control plugin, bug “no commands available” still there :(

  43. Jay
    Posted December 22, 2007 at 1:50 am | Permalink

    Thanks.That was quick. We thought of reinstalling the entire VS. Saved me lot of time.

  44. Gabriel
    Posted January 29, 2008 at 9:22 am | Permalink

    Thank you.
    Quick solution.
    Saved me a few hours.

  45. Ajit
    Posted March 3, 2008 at 10:11 pm | Permalink

    Thanks a lot

  46. Posted May 16, 2008 at 5:06 am | Permalink

    Thanks, this was great and helped me a ton!

  47. julian lynch
    Posted May 28, 2008 at 1:30 pm | Permalink

    Thanks, I was tearing my hair out before reading your post.

Post a Comment

Your email is never published nor shared. Required fields are marked *

*
*