Make sure this folder is checked in before you proceed. In Source Control Explorer, navigate to the folder where you want to place your files. You can also manually add files to version control.
In the Promote Candidate Changes dialog box, make sure only files that you want to check in are selected, and then choose Promote. On the Pending Changes page, in the Excluded Changes section, select the Detected link. In Visual Studio, in Team Explorer, choose Pending Changes. Move your files and folders into this folder.
In Source Control Explorer, navigate to the folder where you want to add the files or folders.Ĭhoose the link next to Local Path to open the target folder in Windows Explorer (File Explorer in Windows 8). If you are using a local workspace, then new files are automatically detected by the Pending Changes page. Files saved when working in a server workspace will add and check in without showing as a pending These steps only apply when using a local workspace.
However, you can also add files that are not referenced by your code projects. When you use Solution Explorer to add a file to your code project, the system automatically adds it to version control. When you're ready, submit your pending changes. For more information, see Check in your work to the team's codebase. If your team will need these files, make sure they are selected and then choose Promote to move them into the Included Changes section of the Pending Changes page. The files in listed in this dialog box are not referenced by any code projects in your solution. The Promote Candidate Changes dialog box appears. In Team Explorer, the Pending Changes page appears.Īre there any Detected items shown in the Excluded Changes section? In Solution Explorer, select the solution, open its context menu, and then choose Check In. In Solution Explorer (Keyboard: Ctrl + Alt + L), select the solution, open its context menu, and then choose Add Solution to Source Control. In Visual Studio, choose File, Open, Project/Solution, and then use the Open Project dialog box to open the solution. Move the folder that contains your solution into the parent folder.
What do I do if the link text is "Not Mapped"? Why is this a good parent folder?Ĭhoose the link next to Local Path to open the parent folder in Windows Explorer (File Explorer in Windows 8). In Source Control Explorer, navigate to a logical parent folder for your solution, such as $/SiteApp/Main, where SiteApp is the name of your project. Use the following procedure instead.Ĭhoose View, Other Windows, Source Control Explorer. To add an existing solution to version control, move all the solution files into your workspace, and then add them.Īvoid using the Add Solution to Source Control dialog box to upload your solution into version control. Place an existing solution and code projects under version control In Solution Explorer, open the context menu of the solution you created or modified and then choose Check In to submit your pending changes. Make sure the Create directory for solution and Add to source control check boxes are selected.Ĭhoose OK to create the code project, which you can then view in Solution Explorer (Keyboard: Ctrl + Alt + L). In the Location list, specify the path to a good local working folder (such as c:\code\SiteApp\Main\) in the workspace you created when you set up your dev machine. If the Solution list appears, make sure Create new solution is selected. In the Name box, specify the name of the code project. Select the type of code project that you want to create.
In Visual Studio, if you have not already done so, connect to the project.Ĭhoose File, New, Project (Keyboard: Ctrl + Shift + N). You can simultaneously create a new project and add it to version control so that you and your team can immediately enjoy all the benefits of version control beginning from the first line of code you write. Before you add files to version control, you should first set up the workspace on your dev machine Create a new code project and solution under version control