It does not make sense to set some settings to a specific value for a specific solution and take other from the visual studio instance.
This could lead to problems.
My solution would be to introduce a checkbox in the settings dialog to override the visual studio options.
When this checkbox is set, the visual studio options are copied to the settings dialog and you can change them there.
But you can't mix and match between options and settings anymore. So if you want then the settings are fixed for a specific solution and if you don't care you can still use the visual studio options.
The migration path would be to detect if settings are present and if so enable this option and fill the other values from the visual studio options. Maybe a notification should indicate that all settings are now solution specific because some solution settings where found.
It does not make sense to set some settings to a specific value for a specific solution and take other from the visual studio instance. This could lead to problems.
My solution would be to introduce a checkbox in the settings dialog to override the visual studio options. When this checkbox is set, the visual studio options are copied to the settings dialog and you can change them there. But you can't mix and match between options and settings anymore. So if you want then the settings are fixed for a specific solution and if you don't care you can still use the visual studio options.
The migration path would be to detect if settings are present and if so enable this option and fill the other values from the visual studio options. Maybe a notification should indicate that all settings are now solution specific because some solution settings where found.