Custom docker image tags during Publish<\/h2>\n
You can now customize the \u201cImage tag\u201d for Docker containers when publishing them to a container registry. The value can either be automatically generated by Visual Studio every time you publish (the previous behavior), or it be manually changed if you need a consistent tag (e.g. \u201clatest\u201d):<\/p>\n
Visual Studio now provides the option to deploy and run Azure Functions projects as zip files<\/a>:<\/p>\n Run-From-Zip<\/a> is a runtime feature that allows ‘mounting’ a zip file and running directly from it. Your App runs directly over the ‘mounted’ zip file, which completely takes over your\u00a0wwwrootfolder (which becomes read-only).\u00a0 Using run from Zip offers the following benefits:<\/p>\n After you publish your Azure Functions project using Visual Studio, you can manage the application settings from the publish summary:<\/p>\n <\/p>\n That’s a feature we added back in update 15.5 of Visual Studio 2017. Since then you gave us feedback that a very common task is to copy the local value of a setting to the remove environment. So now in update 15.8 of Visual Studio 2017 that’s as easy as clicking a button:<\/p>\n When publishing to Azure App Service, Visual Studio asks you to either create a new App Service or re-use an existing one. If you choose to create a new App Service to host your application, Visual Studio now offers you the ability to also provision and configure Application Insights:<\/p>\n All you need to do is pick the region you would like Application Insights to be provisioned in and Visual Studio will make sure it\u2019s configured to pick up telemetry events and metrics from the new App Service. If you wish to add custom events and metrics follow this guide<\/a>. Of course, you can always set the field to \u201cNone\u201d and Visual Studio will not provision nor configure Application Insights on your behalf.<\/p>\n A feature that ASP.NET Framework projects were missing compared to ASP.NET Core was support for storing application secrets (e.g. connection strings, API keys, etc.) in a file outside of source control unique to each user. Now, with .NET Framework 4.7.1<\/a> and Visual Studio 15.8 it\u2019s as simple as right clicking on the project in Solution Explorer and selecting \u201cManage User Secrets\u201d:<\/p>\n Visual Studio will take care of the rest including downloading the necessary NuGet packages, updating the web.config file, creating the secrets file on disk and finally opening it for you to edit:<\/p>\n More info on how to edit this file here<\/a>.<\/p>\n Note:<\/strong> Only available for projects targeting .NET Framework 4.7.1 or higher, if you can\u2019t see the menu item make sure you have the 4.7.1 targeting pack installed<\/a> and that the project is actually targeting 4.7.1, you can change it from project properties:<\/p>\n We added a new menu item under Build | ASP.NET Compilation | Optimize Build Performance for Solution:<\/p>\n ASP.NET compiles its views at runtime, which means your ASP.NET project carries with it a copy of the compiler. However, on a developer machine when the copy of the compiler doesn’t match Visual Studio’s copy, your build performance is impacted on the order of 1-3 seconds per incremental build. This feature will update your project’s copy of the compiler to match Visual Studio’s which should speed up your incremental builds.<\/p>\n This is applicable to ASP.NET Framework projects only, it does not apply to ASP.NET Core.<\/p>\n The dialog for new ASP.NET Core projects now shows you the author and source for the selected template:<\/p>\n![\"Screenshot](\"https:\/\/devblogs.microsoft.com\/wp-content\/uploads\/sites\/16\/2019\/02\/15.png\")
<\/a><\/p>\nZip push deployment & run from zip for Azure Functions<\/h2>\n
<\/a><\/p>\n\n
Managing Azure Functions application settings<\/h2>\n
<\/a><\/p>\n<\/a><\/p>\nEnabling Application Insights as part of publishing to Azure App Service<\/h2>\n
<\/a><\/p>\nManaging user secrets in ASP.NET Framework projects (targeting .NET 4.7.1 or higher)<\/h2>\n
<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\nOptimizing build performance for solutions containing ASP.NET Framework projects<\/h2>\n
<\/a><\/p>\nAuthor and source information for ASP.NET Core templates<\/h2>\n