Support Database Projects Referenced as Same Database in SSDT
Currently, when comparing an SSDT project using SQL Compare, it only loads the base project. If the project references another project as the same database (the standard workaround to the circular reference problem), the objects in the referenced project will not be compared. This can lead to changes being missed and deployments failing.
It would be nice if SQL Compare could follow the reference back and include the objects from the referenced database in the compare as well.