I have a scenario where I am using a visual studio 2010 database project to deploy changes to multiple database installations, but on certain ones I want to exclude a set of views from that copy. Is there a way using build configurations to exclude these views from being deployed?
Have you tried creating a composite project? I haven't implemented this scenario myself but it would seem you could:
Thus when deploying project1, the views would not be included and when deploying project2, the views as well as the core objects would be included.
Have a look at the following Microsoft link. In particular the section titled "Uses and Limitations of Composite Projects"