Forum Discussion

Everseeker's avatar
Everseeker
Contributor
9 years ago
Solved

Attempting TFS Source control... not doing well though.

OK. I have some projects. They have been living on my computer, all nice and happy.

Today, I was asked/told that I would be needing to get them into TFS for version control...

OK, cool... I know that TC does versioning... uh oh... GIT, Subversion, etc... NOT TFS. So I go and look at google.

In among a lot of stuff that involves a total marriage between TFS & TC (NOT yet... baby steps!) I found a really nice tutorial on YouTube that was perfect... https://www.youtube.com/watch?v=6l-32lhkTMk I mean, it was for TFS 2008/TC7.5, but it should not be Toooo different, Right?

So, I downloaded the MSSCCI package for 2013/32 bit and installed it... Then opened the Source Control plugin page, FULLY expecting to see TFS.

I was not rewarded (Stop giggling, I thought it would work)

So, I decided to try "The other way"

Went into Visual Studio, browsed thru the TFS Source until I found the teams data and created a local copy. Added a new folder, made a copy of my current project tree, and commited the entire thing to the great sky-server...

Then opened TC and pointed it to the new local folder.

It worked... saw my Project Suite and all my tests, right where they should be.

Ran one

Awww heck.

getting pestered with a ton of dire warnings that everything is write protected...

Oh yeah, CHECK OUT... (DId that from within Visual Studio again)

Now everything works. Just need to check in/ check out with Visual Studio

 

Ummm.... So, that's were I am. It is SERIOUSLY non-optimal. HOW do I go about correctly/fully integrating TFS & TC, so I can perform the needed manipulations without having to flip open Visual Studio all the time?

 

 

 

3 Replies

Sort By
    • Everseeker's avatar
      Everseeker
      Contributor
      9 years ago

      OK, Accepting your comment as the solution because of the link you provided...

      When I read thru that in detail, I ... REALIZED... that the SCC Api choice in the source control dropdown

      WAS

      the MSSCC plug in... D'oh!

       

      Picked it and most of my troubles faded away.

      (Excpet for the NEW problem... every time I open TC, I have to re-specify the path to the source... and my company stuck it like 9 layers down.... sigh. But that's a minor thing...)