I have recently moved away from Publishing database changes with my ASP.NET MVC Web project (mostly because the auto-generated differential sql script didn't offer any customization options which I needed to make it work).

What I did was create a database project in the same VS2013 solution - this would offer a lot more options. My plan now is to have my website project depend on the database project (to get the right build order) and then publish the freshly built dacpac along with the website - all in one single publishing action.

However, I always get an error message when I try to publish the website and after hours of searching I am still unable to resolve it. The error I get during the website publishing is:

Web deployment task failed. (Could not deploy package.
Internal Error. The database platform service with type Microsoft.Data.Tools.Schema.Sql.SqlAzureV12DatabaseSchemaProvider is not valid. You must make sure the service is loaded, or you must provide the full type name of a valid database platform service.
Internal Error. The database platform service with type Microsoft.Data.Tools.Schema.Sql.SqlAzureV12DatabaseSchemaProvider is not valid. You must make sure the service is loaded, or you must provide the full type name of a valid database platform service.

  Weitere Informationen unter: http://go.microsoft.com/fwlink/?LinkId=221672#ERROR_EXECUTING_METHOD.) 

Interestingly, if I publish the database project instead of the web project then it will work fine. But it does temporarily leave my site in a broken state so I'd prefer not to publish db and website separately like this.

I have already installed the latest versions of SSDT (for both VS2012 and VS2013), I have installed CU6 for SQL Server 2014 and also updated SQL Server 2014 to SP1 but nothing has changed. Is there really something wrong with my client tools or is my approach to publishing the dacpac wrong altogether?

Hi,

  Thank you for your question.

  I am trying to involve someone familiar with this topic to further look at this issue. In the meantime, please have a check on the below link and check if it helps.
  http://eliot-jones.com/2014/08/dacpac-error-visual-studio-2013
  http://blogs.msdn.com/b/azuresqldbsupport/archive/2015/04/08/bacpac-could-not-load-schema-model-from-package.aspx
 
Regards,
Nithin Rathnakar

Thanks for the links. I checked them but I wasn't able to solve the error.

Are you deploying against a Azure SQL Database v11 or v12 database? 

I'm using A V12 database that I upgraded from V11. I also selected V12 in the Database project's properties.

Not sure if this info is helpful, but today I set up the Windows 10 Technical Preview as dual boot and installed VS2015 RC. I then proceeded to install the Azure SDK for VS2015 and tried to deploy the project but I got exactly the same error message.

I have not installed SSMS under Windows 10 though and I couldn't find any version of SSDT for VS2015 either.

I'm getting the same error, running Windows 8.1 with Visual Studio 2013 Ultimate, and an ASP.NET project, trying to deploy to Azure. I have scoured the internet, and can't seem to find an answer to this problem, please help!

Thanks!

Joseph

I'm using SQL Server 2014 and deploying to Azure SQL Server v12.