Learn to use Visual Studio, Visual Studio Online, Application Insights and Team Foundation Server to decrease rework, increase transparency into your application and increase the rate at which you can ship high quality software throughout the application lifecycle
UPDATE June 11, 2012 - This blog post series has been updated by our new beginner's guide hosted here.
This blog post is part of the Beginner’s Guide series with the goal to get you productive fast.
This post walks you step-by-step to get your source code stored in your Team Foundation Services Preview account.
Click Not mapped.
When you click Not mapped, the Map dialog box is launched.
You’re going to select a folder on your local drive that will mirror the folders in source control. This is called your workspace. Choose a folder where you want to store your source-controlled files, for example: C:\Users\YourName\src.
There is more information available about setting up workspaces on MSDN. See Create and Work with Workspaces.
You can simply drag and drop files from Windows Explorer.
When you have the correct files ready, click Finish.
There is more information available about adding files to source control on MSDN. See Add Files to Version Control.
It will have a yellow + sign next to it.
Your folder and files are not actually checked in and available for other team members to work on until you right-click the folder and click Check In Pending Changes.
This will upload all of your files, and add them to your source repository in the cloud. Click Check In and you’re done.
Congratulations! Your source is now in the cloud, yet still accessible via the Visual Studio interface.
If you are new to Version Control and Source Control Explorer, or simply want to dig deeper, you’ll find extensive coverage on the MSDN website: Using Version Control.
Why not right click on the solution in Solution Explorer and select "Add Solution to Source Control..."
You're right that if you open the solution in VS, you can right click it to add to source control. If you go that route, you'll see a slightly different experience for creating your workspace mappings, but the end result will be a solution with pending adds in a mapped workspace.
One reason this method was shown is that it allows items that are not part of a solution to be added to source control. Using the "Add Solution to Source Control..." feature will not add items that are not referenced by the solution.
Program Manager |TFS Version Control
Will this keep source code change history so that it is available in cloud also?
Yes, the steps outlined above are the process to use to upload your source into our cloud hosted Team Foundation Server which provides source control features that you would expect (like History).
I was unable to add files dragging from windows explorer as indicated. I had to right click on the works apace and use the context menu to "add items to Folder...".
Due to some fumbling, I now have three projects in TFService. When I map files on the server to my workstation, only the first project shows. It does not matter what project I pick in "Connect to Team Project". BTW I am using this page because I have VS2010.
@Al - Is it possible that you already have the local files mapped in a workspace for one of the previously created projects? That could explain the behavior that you're seeing. To fix this, you'll probably need to delete the workspace in the project that you don't want to use. You can do this from the Manage Workspaces dialog that is accessible from Source Control Explorer (in the workspace picker). If that doesn't help, please contact me at mmitrik at microsoft.com