![]() ![]() In Visual Studio, choose File > Open Project, and navigate to and open the solution. In File Explorer, move the folder that contains your solution into the parent folder. If the link says Not mapped, see Create and work with workspaces for information about mapping your workspace. Select the link at the top of the window next to Local Path to open the parent folder in Windows File Explorer. To find out more about naming local folders, see Optimize your folder names. 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. To add an existing solution to version control, move all the solution files into your workspace, and then add them in Visual Studio.Ĭhoose View > Other Windows > Source Control Explorer. Place existing solutions and code projects under version control Switch to the Team Explorer window and select Check in to check in the project to source control. Right-click the solution name in Solution Explorer, and select Add Solution to Source Control from the context menu. Once the project is created, view it in Solution Explorer, which you can open by pressing Ctrl+Alt+L. On the Additional information screen, change any settings as needed, and then select Create. Leave the rest of the settings as they are, and select Next. Under Location, specify the path to a local working folder, such as c:\code\SiteApp\Main\, in the workspace you created when you set up your dev machine. On the Configure your new project screen, under Project name, enter a name for the project. On the Create a new project screen, select the type of code project you want to create, and then select Next. Select File > New Project, or press Ctrl+Shift+N. In Visual Studio, connect to your Azure DevOps project. You can create a new Visual Studio 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. Create a new code project and solution under version control Conversely, files you save in a server workspace add and check in without showing as pending changes. When you use a local workspace, new files are automatically detected as pending changes. These procedures apply only when you use a local workspace. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |