Tidy up - Unused Project and Nuget package reference using Visual Studio 2019

If you are a Developer/Architect using Visual Studio as IDE for your development activities, this blog post will be of your interest. During the Ignite 2021 conference, Microsoft released Visual Studio 2019 v16.9 and v16.10 Preview 1. As part of version 16.10 Preview 1, one of the cool features they introduced is to "Remove Unused References..." for any Projects and Nuget packages that are not in use. At the time of writing this blog post, we have Visual Studio Version 16.10.0 (official release) which includes this new feature.  As part of development, we generally get carried away and introduce new Nuget package references to your project and add new references to your Projects. By the end of development, you will not be 100% sure which are not being referenced and unused which means you will leave those unused project references in your application. Now you might be wondering what's the big deal in it since it doesn't harm. The advantage of removing unused project r

Azure Function in a Docker Container - Part 2

In my previous blog post, we looked at how to run Azure Function in a Docker Container locally using Docker desktop. In this blog post, we will see how to run the Azure Function container in Azure.

Steps to run Azure Function in Container

  • Create an Azure Function by choosing the right resource plan, resource group, a region with a storage account, and Application Insights for monitoring support. As part of the provisioning key things to support containerization, you need to choose the "Publish" option with "Docker Container" as shown below.




Choose the hosting options based on your requirements like App-service plan or Premium.


  • Once the Azure Function is provisioned navigate to the overview tab then you will be seeing a warning to configure container settings as shown below.
  • Clicking on "Configure container settings" provides options to choose container image from Image source like 
    • Azure Container Registry
    • Docker hub
    • Private Registry
  • For our demo, I have a container image in ACR and as part of configuring the container setting, it provides options to choose the image and its tag. Once the container is chosen, click on the Save option 

  • Now let's navigate to "Functions" will be able to see the Azure Function name along with the trigger type. In our demo, it's an HTTP trigger function of Azure Function v3.

  • Clicking on the Azure Function name will provide an option to test and run just like any other Azure Function code.

  • Now, let's test our Azure Function by browsing the function URL in the browser.


Comments

Popular posts from this blog

Tidy up - Unused Project and Nuget package reference using Visual Studio 2019

Swagger UI for Azure Function v2 & v3 APIs

Authenticate Azure Functions - API Keys