Hi,
Thanks for reporting this. We have rechecked the VS2015 setting exporting logic and it indeed looks like it skips the custom language service settings (such as VisualGDB) by default. As fully fixing this would require a relatively large investigation/change on our side, we would instead suggest using one of the workarounds below:
- First of all, you can change the values via registry (HKEY_CURRENT_USER\SOFTWARE\Microsoft\VisualStudio\14.0\ApplicationPrivateSettings\TextEditor\C/C++ (VisualGDB))
- Alternatively, if you are using the VisualGDB’s team settings engine, we could extend it to share the common Clang IntelliSense settings
Let us know if you would like us to extend the team settings engine to handle this.