I posted this same article to the Continous Integration forum but thought the SSDT forum might be appropriate as well...
I'm trying to setup some continuous integration for building an ISPAC file for both SQL Server 2014 and SQL Server 2016 from a single solution. I don't want to have to maintain two different versions of the solution nor do I want to have to keep changing the TargetServerVersion project property. I'm using SSDT for Visual Studio 2017. I've setup two configurations in Configuration Manager: one with a TargetServerVersion of 2014 and one for 2016.
When I call devenv from the "Develop command prompt" command-line and use the 2016 configuration, I get the window dialog box that states: You are about to change the TargetServerVersion property...Click Yes, No
There doesn't seem to be a way to automate this response. I admit my build knowledge is very limited so I could be missing something in what SSDT has to offer to help in my situation.
I've read numerous articles about how SSIS does not lend itself to CI very well and is a rather pain getting MSBUILD to automate the build process without VS/SSDT. At this point, I've resigned myself to having to install SSDT on the build server at least. But, now this issue of building multiple SQL Server version ISPAC files from the same solution via a command-line is my next hurdle.
Thanks in advance for your help.