Hi,
If the framework changes, VisualGDB won’t replace the entire file list overriding your changes. Instead it will add the new sources to the project, keeping the “does not build” flag for the old ones.
If the new source files only contain functions/methods used by the old ones, the linker will automatically eliminate them (as long as other files are excluded), so you won’t need to update this manually.
Long term, we will solve this by fully supporting the Advanced CMake Project Subsystem for embedded projects – the frameworks will be converted to separate CMake targets and you will be able to fine-tune the references by editing the CMake files, although this will be added after the upcoming v5.4.