0
votes

I'm trying to build a SSIS 2016 project, that's been configured with the Project Deployment model in a VSTS build with the intent to deploy the .ispac file onto a SQL Server VM hosted in Azure.

Using MSBuild to build the project file returns the following error:

The default XML namespace of the project must be the MSBuild XML namespace. 
If the project is authored in the MSBuild 2003 format, please add xmlns="http://schemas.microsoft.com/developer/msbuild/2003" to the  element. 
If the project has been authored in the old 1.0 or 1.2 format, please convert it to MSBuild 2003 format.

I found a blog post here describing the same issue

https://speaksql.wordpress.com/2013/06/07/a-journey-to-db-deployment-automaton-ssis-build-using-msbuild/

However, the solution depends on installed SQL Server Data Tools into a build agent.

Is there a method where I can use a VSTS Hosted agent, and not have to create an on-premises agent with SSDT installed?

3
Please vote here if you think it's about time for MSBuild to support SSxS projects: developercommunity.visualstudio.com/idea/523612/…Nahuel Prieto

3 Answers

1
votes

Just released new Extension for VSTS/TFS

https://github.com/ToxicGlobe/VSTS-SSIS-Extension

It build Visual Studio project, containing packages and parameters to a project deployment file (.ispac)

https://marketplace.visualstudio.com/items?itemName=TG.VSTS-SSIS

1
votes

For similar scenario i used devenv.exe

Tool : C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\devenv.exe

Arguments : .\Code\Database\NameOfSolution.sln /build $(BuildConfiguration)

devenv.exe /build does not require ssdt to installed on build agent