I have a set of visual studio 2010 database projects that are dependent on each other. I can build the project with the lowest level of script, and then after that build my child scripts separately. When I try to upgrade them to the visual studio of 2013, creating child projects puts the entire schema from the parent element inside the child script. Is there any way to avoid this behavior? Or is there a better template to support this type of customization?
source
share