I have a database project in Visual Studio 2012 with SSDT (the last of these letters). In a database project, I have a schema called " UNITTEST " that contains many stored procedures that create, destroy, and provide other helper functions for unit tests. We do this because it gives us the ability to control our test data centrally, and not inside each unit test. Now that everything is fine and everything, however, I do not want to publish this scheme or any objects inside this scheme for production.
So my question is .. Is there a way to stop SSDT / VS2012 from including a UNITTEST schema in deploying a build assembly script?
I think there should be a way to do this depending on the configuration settings of the solution and the publication of profiles. If my configuration is set to Release, then I want the build to work a little differently.
The styles are very new to me. I found this question: build-different-scripts-depending-on-build-configuration , but I cannot get an answer to fulfill my problem. This question also does not help, although it is very similar: bind-the-deploy-and-publish-destination .
Does anyone else manage something like that? Other developers in my team just modify the published script to remove these objects, but I do NOTHING manual work, there must be a solution! :)
Thanks everyone!