VS Publish dialog Update Database dialog disabled

VS Publish dialog Update Database dialog disabled

Rate This
  • Comments 3

If you have tried out our new Web Publish experience in Visual Studio you may have noticed that the Update Database checkbox is disabled. See the image below.

image

The intended behavior of this checkbox is to enable you to incrementally publish your database schema from the source (the connection string in web.config) to the destination (whatever connection string is in the text box). The difference between an incremental publish and a typical publish is that for incremental publishes only changes are transferred from source to destination. With a full publish the first time that you publish your DB schema everything is created, and the next time that you try to publish you will receive an error because it tries to re-create existing DB objects.

The functionality of the Update database checkbox leverages an MSDeploy provider. We were hoping to complete that provider and give it to hosters in time for the release but we were unable to do so. We are working on completing the provider and partnering with hosters to install these in time for the launch of Visual Studio 2012 RTM.

Note: If you are using VS 2012 RC the checkbox is not disabled. It will work if you publish to localhost but it will not work for any remote scenarios.

In the mean time if you need to publish your DB schema you can use the Package/Publish SQL tab (caution: the DB publishing here is not incremental). If you are going to use the PP/Sql tab to publish to SQL Azure then there are some special considerations that you will need to take. You can learn more about those by visiting http://msdn.microsoft.com/en-us/library/dd465343.aspx and searching for “Azure” on that page.

If you have any questions please feel free to directly reach out to me at sayedha(at){MicrosoftDOTCom}.


Thanks,
Sayed Ibrahim Hashimi @SayedIHashimi

Cross posted to: http://sedodream.com/2012/06/07/VSPublishDialogUpdateDatabaseDialogDisabled.aspx

Leave a Comment
  • Please add 5 and 2 and type the answer here:
  • Post
  • Ugh, this is a case of when tooling goes wrong. Visual Studio is becoming a monster of special case dialogs, most of which are really geared towards only Microsoft technology, as in SQL Server, Azure, ASP.NET MCV, WebMatrix. It get's to a point where we need to actively study all the new stuff Microsoft puts out there, just to make sure we understand the tools.

    Can you guys focus on stability for the next releases please?

  • am testing tonight locally, I hope it goes well

  • I assume things will work fine for the DBcontext, as discussed the normal connection is greyed. So I am only using the normal one for aspmembership so a simple sql compare should fix it for my remote server

Page 1 of 1 (3 items)