{"id":21723,"date":"2019-04-05T10:31:32","date_gmt":"2019-04-05T17:31:32","guid":{"rendered":"https:\/\/devblogs.microsoft.com\/aspnet\/?p=21723"},"modified":"2019-04-05T10:31:32","modified_gmt":"2019-04-05T17:31:32","slug":"web-and-azure-tool-updates-in-visual-studio-2019","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/dotnet\/web-and-azure-tool-updates-in-visual-studio-2019\/","title":{"rendered":"Web and Azure Tool Updates in Visual Studio 2019"},"content":{"rendered":"

Hopefully by now you\u2019ve seen that Visual Studio 2019 is now generally available<\/a>. As you would expect, we\u2019ve added improvements for web and Azure development. As a starting point, Visual Studio 2019 comes with a new experience for getting started with your code<\/a> and we updated the experience for creating ASP.NET and ASP.NET Core projects to match:<\/p>\n

\"\"<\/p>\n

If you are publishing your application to Azure, you can now configure Azure App Service to use Azure Storage and Azure SQL Database instances, right from the publish profile summary page, without leaving Visual Studio. This means that for any existing web application running in App Service, you can add SQL and Storage, it is no longer limited to creation time only.<\/p>\n

\"\"<\/p>\n

By clicking the \u201cAdd\u201d button you get to select between Azure Storage and Azure SQL Database (more Azure services to be supported in the future):<\/p>\n

\"\"<\/p>\n

and then you get to choose between using an existing instance of Azure Storage that you provisioned in the past or provisioning a new one right then and there:<\/p>\n

\"\"<\/p>\n

When you configure your Azure App Service through the publish profile as demonstrated above, Visual Studio will update the Azure App Service application settings to include the connection strings you have configured (e.g. in this case azgist). It will also apply hidden tags to the instances in Azure about how they are configured to work together so that this information is not lost and can be re-discovered later by other instances of Visual Studio.<\/p>\n

For a 30 minute overview of developing with Azure in Visual Studio, check out the session we gave as part of the launch<\/a>:<\/p>\n

\"\"<\/a><\/p>\n

Send us your feedback<\/h2>\n

As always, we welcome your feedback. Tell us what you like and what you don\u2019t like, tell us which features you are missing and which parts of the workflow work or don\u2019t work for you. You can do this by submitting issues to Developer Community or contacting us via Twitter.<\/p>\n","protected":false},"excerpt":{"rendered":"

Hopefully by now you\u2019ve seen that [Visual Studio 2019 is now generally available][1]. As you would expect, we\u2019ve added improvements for web and Azure development. As a starting point, Visual Studio 2019 comes with [a new experience for getting started with your code][2] and we updated the experience for creating ASP.NET and ASP.NET Core projects to match:<\/p>\n","protected":false},"author":127,"featured_media":58792,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[197],"tags":[],"class_list":["post-21723","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-aspnet"],"acf":[],"blog_post_summary":"

Hopefully by now you\u2019ve seen that [Visual Studio 2019 is now generally available][1]. As you would expect, we\u2019ve added improvements for web and Azure development. As a starting point, Visual Studio 2019 comes with [a new experience for getting started with your code][2] and we updated the experience for creating ASP.NET and ASP.NET Core projects to match:<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/posts\/21723","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/users\/127"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/comments?post=21723"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/posts\/21723\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/media\/58792"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/media?parent=21723"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/categories?post=21723"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/tags?post=21723"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}