{"id":3708,"date":"2018-03-05T15:46:57","date_gmt":"2018-03-05T23:46:57","guid":{"rendered":"https:\/\/visualgdb.com\/w\/?p=3708"},"modified":"2018-03-05T15:56:20","modified_gmt":"2018-03-05T23:56:20","slug":"sharing-common-visualgdb-settings-with-team-settings-engine","status":"publish","type":"post","link":"https:\/\/visualgdb.com\/tutorials\/custom\/teamsettings\/","title":{"rendered":"Sharing Common VisualGDB Settings with Team Settings Engine"},"content":{"rendered":"

This tutorial shows how to simplify sharing common VisualGDB settings\u00a0across multiple development machines in your team using VisualGDB Team Settings (available in the Custom edition and higher). We will create\u00a0a basic project utilizing a cross-toolchain on a remote Linux machine, commit it to a git repository and open it from a different development machine, showing how to automatically import all shared settings and avoid manual setup.<\/p>\n

Before you begin, install VisualGDB 5.3 or later.<\/p>\n

    \n
  1. Start Visual Studio and open the VisualGDB Linux Project Wizard:\"01-prjname\"<\/a><\/li>\n
  2. On the first page select “Create a new project” -> “Application”:
    \n    \"02-app\"<\/a><\/li>\n
  3. Select the\u00a0Linux machine you want to use for building.\u00a0To demonstrate quick sharing of settings across different machines, we will\u00a0use\u00a0the ARM Linux cross-toolchain\u00a0that needs to be explicitly\u00a0selected on the\u00a0build machine. You can also\u00a0use any other toolchain on your Linux machine (or proceed with the default toolchain and use Team Settings to share other settings). Click “Specify toolchain manually by locating gdb executable”:\"03-newtc\"<\/a><\/li>\n
  4. Then locate the gdb executable from the toolchain:
    \n<\/a>    \"04-gdb\"<\/a><\/li>\n
  5. VisualGDB will let you confirm or edit the locations of specific tools\u00a0in the toolchain.\u00a0The settings will be saved under the %LOCALAPPDATA%\\VisualGDB directory so that you won’t need to reenter them next time you create another project.\u00a0We will\u00a0show how to easily share those settings via the Team Settings\u00a0Engine later in this tutorial:\"05-review\"<\/a><\/li>\n
  6. Click “Deploy the project to another Linux computer” and select the deployment machine and path:\"06-deploy\"<\/a><\/li>\n
  7. Finally proceed with the default source code disposition settings and click “Finish”:\"07-dirs\"<\/a><\/li>\n
  8. VisualGDB will create a basic project. Ensure you can build and debug it:\"08-debug\"<\/a><\/li>\n
  9. Commit the project to a Git repository and\u00a0clone it on a second development machine. Try opening it in Visual Studio. As we have not\u00a0configured settings sharing yet, VisualGDB will ask for the toolchain location:\"09-create\"<\/a>For convenience, this tutorial uses the blue\u00a0color theme on the first machine and the dark theme on the second one.<\/li>\n
  10. If you try to locate it manually, you would also need to create a new SSH connection:\"10-reenter\"<\/a>The Team Settings Engine allows avoiding those steps by automatically sharing common settings between different machines.<\/li>\n
  11. Get back to the first machine\u00a0and open Tools->VisualGDB->Manage Team Settings:\"11-teamset\"<\/a><\/li>\n
  12. Enable settings sharing and\u00a0pick a network folder accessible from both machines:
    \n    \"share\"<\/a>You can use Windows Security Settings to choose between read-only and read-write access for different users.\u00a0If the folder is shared in a read-only mode, VisualGDB will still apply the\u00a0shared settings, but won’t allow\u00a0changing them unless it confirms read-write access.<\/li>\n
  13. Go to the Remote Hosts page and share both the build machine\u00a0and the deployment machine connections. If you are using saved\u00a0passwords, you can\u00a0automatically share the password as well (note that this will make it available to\u00a0anyone with access to the shared\u00a0settings folder):
    \n    \"12-hosts\"<\/a><\/li>\n
  14. Open\u00a0the Host Settings page and share the\u00a0custom toolchain selected in the wizard while creating the project:\"13-settings\"<\/a><\/li>\n
  15. Go to the second machine and open VisualGDB\u00a0Team\u00a0Settings. Enable settings sharing and specify the same network folder:
    \n    \"14-import\"<\/a>Once you close the Team Settings window, VisualGDB will immediately import the shared remote\u00a0host settings and the toolchain definition.<\/li>\n
  16. Now you can open the project from the git repository again. The toolchain settings and the remote host settings will now be automatically located and VisualGDB will suggest regenerating the\u00a0MSBuild rule files:\"15-rebuild\"<\/a><\/li>\n
  17. Press “Yes” and you will be able to build and debug your project on the second machine without any further setup steps:\"16-debug2\"<\/a><\/li>\n
  18. Now we will\u00a0demonstrate how to share connection aliases<\/a> using VisualGDB Team Settings. Go back to the first machine, open the “Computer used for building and debugging” selector and\u00a0click “Define a new global alias”:\"17-alias\"<\/a><\/li>\n
  19. Enter the alias name and configure it to\u00a0resolve to the build machine used earlier:\"18-buildvm\"<\/a><\/li>\n
  20. The project will now refer to the alias rather than the build machine directly, allowing you to easily change it later without manually editing all related projects:
    \n    \"19-vm\"<\/a>We will now use the Team Settings window to share the newly created SSH host alias.\u00a0We will also demonstrate how to\u00a0store the shared\u00a0settings in your source control system.<\/li>\n
  21. Create a\u00a0new folder under your\u00a0source control checkout and configure VisualGDB to store the shared settings there:
    \n    \"20-newdir\"<\/a><\/li>\n
  22. As you are detaching VisualGDB from the current shared settings folder, it will ask if you want to automatically remove the\u00a0shared settings\u00a0available through it:
    \n    \"21-preserve\"<\/a>Click “Preserve” to keep them.<\/li>\n
  23. Go to the Host Aliases page and share the newly created alias:\"22-alias\"<\/a>Don’t forget to re-share remote hosts and toolchain definition after changing the shared settings folder.<\/li>\n
  24. Commit the folder to your source control system and check it out on the second machine. Then configure VisualGDB Team Settings to look for shared settings in that folder:\"23-newpath\"<\/a>VisualGDB will automatically\u00a0import the newly created alias.<\/li>\n
  25. As the shared settings are stored in\u00a0simple XML files, you can easily use the Source Control GUI to track\u00a0the related changes. E.g. try changing the alias\u00a0target to another machine:
    \n    \"24-newtarget\"<\/a><\/li>\n
  26. Then open the Changes view of the VS Team Explorer and see how\u00a0the change affected\u00a0the VisualGDBTeamSettings.xml file:\"25-git\"<\/a>Once you commit that file to your\u00a0repository\u00a0(and update it on all other development machines), VisualGDB will automatically pick up new settings from it, updating the alias on all machines using the same shared settings.<\/li>\n<\/ol>\n","protected":false},"excerpt":{"rendered":"

    This tutorial shows how to simplify sharing common VisualGDB settings\u00a0across multiple development machines in your team using VisualGDB Team Settings<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[10],"tags":[38,33,158],"_links":{"self":[{"href":"https:\/\/visualgdb.com\/w\/wp-json\/wp\/v2\/posts\/3708"}],"collection":[{"href":"https:\/\/visualgdb.com\/w\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/visualgdb.com\/w\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/visualgdb.com\/w\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/visualgdb.com\/w\/wp-json\/wp\/v2\/comments?post=3708"}],"version-history":[{"count":5,"href":"https:\/\/visualgdb.com\/w\/wp-json\/wp\/v2\/posts\/3708\/revisions"}],"predecessor-version":[{"id":3741,"href":"https:\/\/visualgdb.com\/w\/wp-json\/wp\/v2\/posts\/3708\/revisions\/3741"}],"wp:attachment":[{"href":"https:\/\/visualgdb.com\/w\/wp-json\/wp\/v2\/media?parent=3708"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/visualgdb.com\/w\/wp-json\/wp\/v2\/categories?post=3708"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/visualgdb.com\/w\/wp-json\/wp\/v2\/tags?post=3708"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}