Skip to main content

.NET 7 | Web API | Azure Blob Storage | File Management | Example

This article will explain the communication between Web API(.NET 7) and Azure Blob Storage for managing files.

Azure Blob Storage:

Azure Blob Storage is a Microsoft Cloud Storage. Azure Blob Storage is used to manage the files for storing or reading.

Storage Account:
A Storage account gives us a unique namespace. Every file we save or store on Azure Storage must have an address, and that address is nothing but the unique name of our Storage Account name. The combination of the storage account name and Azure blob Storage endpoint forms the base address. For example, if our storage account is named as 'my-azure-account' then the base address will be like 'https://my-azure-account.blob.core.window.net'.

Containers:
The Containers are just like folders.

Blob:
The actual item or file we will store inside of the container.

Create Azure Blob Storage In Azure Portal:

(Step 1)First, we have to 'Sing-Up' in 'Microsoft Azure Portal', after completing 'Sing-Up' and then 'Sing-In' portal we can observe an azure portal like below. And then click on the 'Create A Resource' button.

(Step 2) Search like 'Storage Account' and then click on the 'Create' button.

(Step 3):
Fill out the 'Create A Storage Account' form.
  • Here in the 'Subscription' field make sure to select your subscription which may be paid or free. If you use paid subscription also the Microsoft won't charge for basic usage so it will be a benefit for those who are newly working with Azure Blob Storage.
  • Here the 'Resource Group' is like a folder which holds the azure services in our case Azure Blob Storage Service going to be stored in the defined 'Resource Group' name
  • Here 'Storage Account Name' field, here give a meaning full name because this name will be used to generate the subdomain URL for our Azure Blob Storage.
  • Here 'Region' you can leave the default or you choose the nearest location to host your server
  • Here 'Performance' & 'Redundancy' to default values.
(Step 4):
Now Click on the 'Review. button at the bottom, so that we can directly navigate to the 'Review' tab because all the remaining tabs can be skipped with default values. Now on the 'Review' tab click on the 'Create' button at the bottom
(Step 5)
Now click on the 'Go to resource' button
(Step 6):
Now in our Azure Blob Storage account, go to the 'Container' left side menu item, then click on '+ Container' button. Then in the create container form give your container name and in the 'Public Access Level' drops down give a value like 'Container(anonymous read access for containers)'.  Finally, click on the create button.
(Step 7):
We can observe our newly created container below.

Create A .NET 7 Web API Application:

Let's create the .NET 7 Web API application to implement our demo on Azure Blob Storage. The most recommended IDEs are Visual Studio 2022(V17.4.* supports .NET 7) or Visual Studio Code. In this demo, I'm using the Visual Studio Code editor.
dotnet new webapi -o name_of_your_project

Install Azure Blob Storage Package:

Let's install the Azure Blob Storage package.
.NET CLI Command
dotnet add package Azure.Storage.Blobs --version 12.14.1

Package Manager Command
NuGet\Install-Package Azure.Storage.Blobs -Version 12.14.1

Add Azure Storage ConnectionString:

Go to our Azure Storage Account, then go to the 'Security  + Network' menu on the left-hand side menu, then click on the 'Access Keys' then we can see 'Key1' & 'Key2' connection strings any one can be used into our API.

In the 'appsettings.Development.json' let's add the connection string.
appsettings.Development.json:
"ConnectionStrings": {
  "AzureStorage":"your azure storage connection string value"
}

Register 'BlobServiceClient':

In the 'Program.cs' file register the 'Azure.Storage.Blob.BlobServiceClient'.
Program.cs:
using Azure.Storage.Blobs;
builder.Services.AddScoped(_ =>
{
    return new BlobServiceClient(builder.Configuration.GetConnectionString("AzureStorage"));
});
  • Here for the 'BlobServiceClient' instance pass our connection string value as an input parameter.

Create A Service Like 'FileService':

To implement our core logic let's create the service files like 'IFileService.cs' & 'FileService.cs' in the 'Services' folder(new folder).
Services/IFileService.cs:
namespace dot7.blob.demo.Services;
public interface IFileService
{

}
Services/FileService.cs:
using Azure.Storage.Blobs;
namespace dot7.blob.demo.Services;
public class FileService: IFileService
{
    private readonly BlobServiceClient _blobServiceClient;
    public FileService(BlobServiceClient blobServiceClient)
    {
        _blobServiceClient = blobServiceClient;
    }
}
  • Here injected the 'Azure.Storage.Blobs.BlobServiceClient'.
Now register our service file into the 'Program.cs'.
Program.cs:
builder.Services.AddScoped<IFileService, FileService>();

Create A API Controller Like 'FileController':

Let's create a new API controller like 'FileController'.
Controllers/FileController.cs:
using dot7.blob.demo.Services;
using Microsoft.AspNetCore.Mvc;
namespace dot7.blob.demo.Controllers;

[ApiController]
[Route("[controller]")]
public class FileController: ControllerBase
{
    private readonly IFileService _fileService;
    public FileController(IFileService fileService)
    {
        _fileService = fileService;
    }
}
  • Here injected our 'IFileService'.

Create File Upload Endpoint:

Let's create a payload model for our file upload like 'FileModel.cs' in the 'Models' folder.
Models/FileModel.cs:
namespace dot7.blob.demo.Models;
public class FileModel
{
    public IFormFile ImageFile { get; set; }
}
  • The 'Microsoft.AspNetCore.Http.IFormFile' type can read a stream of the file from the form data.
Let's add the logic for uploading the file to our Azure Blob Storage in our 'FileService'.
Services/IFileService.cs:
Task Upload(FileModel fileModel);
Services/FileService.cs:
public async Task Upload(FileModel fileModel)
{
	var blobContainer = _blobServiceClient.GetBlobContainerClient("mycontainer");

	var blobClient = blobContainer.GetBlobClient(fileModel.ImageFile.FileName);

	await blobClient.UploadAsync(fileModel.ImageFile.OpenReadStream());
}
  • (Line: 3) Create an instance for our azure blob container. Here we have to pass our container name to the 'GetBlobContainerClient' method.
  • (Line: 5) Create the instance of the blob with the name, so this blob instance(any file) we are going to upload to our Azure cloud.
  • (Line: 7) Here 'UploadAsync' method saves our file to the Azure Cloud.
Now let's add the file upload endpoint in our controller.
Controllers/FileController.cs:
[Route("upload")]
[HttpPost]
public async Task<IActionResult> Upload([FromForm]FileModel model)
{
	if (model.ImageFile != null)
	{
		await  _fileService.Upload(model);
	}
	return Ok();
}

Add File Read Endpoint:

Let's implement the logic for reading the file from Azure Blob Storage.
Services/IFileService.cs:
Task<Stream> Get(string imageName);
Services/FileService.cs:
public async Task<Stream> Get(string imageName)
{
	var blobContainer = _blobServiceClient.GetBlobContainerClient("mycontainer");

	var blobClient = blobContainer.GetBlobClient(imageName);
	var downloadContent = await blobClient.DownloadAsync();
	return downloadContent.Value.Content;
}
  • (Line: 3) Create the container instance by using our Azure Blob Storage container name.
  • (Line: 5) Crate the blob instance from the container instance.
  • (Line: 6&7) Download the stream of the blob(file).
Let's implement the endpoint to read the file.
Controllers/FileController.cs:
[Route("get")]
[HttpGet]
public async Task<IActionResult> Get(string fileName)
{
	var imgStream = await _fileService.Get(fileName);
	string fileType = "jpeg";
	if (fileName.Contains("png"))
	{
		fileType = "png";
	}
	return File(imgStream, $"image/{fileType}");
}
  • (Line: 11) Using the 'File' method we return our blob stream as a response.

Add File Download Endpoint:

Let's add the file download endpoint as below.
Controllers/FileController.cs:
[Route("download")]
[HttpGet]
public async Task<IActionResult> GetDownload(string fileName)
{
	var imgStream = await _fileService.Get(fileName);
	string fileType = "jpeg";
	if (fileName.Contains("png"))
	{
		fileType = "png";
	}
	return File(imgStream, $"image/{fileType}",$"blobfile.{fileType}");
}
  • Here download endpoint is almost similar to our read endpoint only change we used the overloaded 'File' method that takes the name of the file to download.

Support Me!
Buy Me A Coffee PayPal Me

video Session:

Wrapping Up:

Hopefully, I think this article delivered some useful information of approaches to consuming Azure Blob Storage in .Net7 Web API. I love to have your feedback, suggestions, and better techniques in the comment section below.

Follow Me:

Comments

  1. I can't see your third YouTube video is private

    ReplyDelete
  2. How can you return the % progress from the blobclient.UploadAsync?

    ReplyDelete

Post a Comment

Popular posts from this blog

.NET6 Web API CRUD Operation With Entity Framework Core

In this article, we are going to do a small demo on AspNetCore 6 Web API CRUD operations. What Is Web API: Web API is a framework for building HTTP services that can be accessed from any client like browser, mobile devices, desktop apps. In simple terminology API(Application Programming Interface) means an interface module that contains a programming function that can be requested via HTTP calls to save or fetch the data for their respective clients. Some of the key characteristics of API: Supports HTTP verbs like 'GET', 'POST', 'PUT', 'DELETE', etc. Supports default responses like 'XML' and 'JSON'. Also can define custom responses. Supports self-hosting or individual hosting, so that all different kinds of apps can consume it. Authentication and Authorization are easy to implement. The ideal platform to build REST full services. Create A .NET6 Web API Application: Let's create a .Net6 Web API sample application to accomplish our

Angular 14 Reactive Forms Example

In this article, we will explore the Angular(14) reactive forms with an example. Reactive Forms: Angular reactive forms support model-driven techniques to handle the form's input values. The reactive forms state is immutable, any form filed change creates a new state for the form. Reactive forms are built around observable streams, where form inputs and values are provided as streams of input values, which can be accessed synchronously. Some key notations that involve in reactive forms are like: FormControl - each input element in the form is 'FormControl'. The 'FormControl' tracks the value and validation status of form fields. FormGroup - Track the value and validate the state of the group of 'FormControl'. FormBuilder - Angular service which can be used to create the 'FormGroup' or FormControl instance quickly. Form Array - That can hold infinite form control, this helps to create dynamic forms. Create An Angular(14) Application: Let'

Part-1 Angular JWT Authentication Using HTTP Only Cookie[Angular V13]

In this article, we are going to implement a sample angular application authentication using HTTP only cookie that contains a JWT token. HTTP Only JWT Cookie: In a SPA(Single Page Application) Authentication JWT token either can be stored in browser 'LocalStorage' or in 'Cookie'. Storing JWT token inside of the cookie then the cookie should be HTTP Only. The HTTP-Only cookie nature is that it will be only accessible by the server application. Client apps like javascript-based apps can't access the HTTP-Only cookie. So if we use authentication with HTTP only JWT cookie then we no need to implement custom logic like adding authorization header or storing token data, etc at our client application. Because once the user authenticated cookie will be automatically sent to the server by the browser on every API call. Authentication API: To implement JWT cookie authentication we need to set up an API. For that, I had created a mock authentication API(Using the NestJS Se

Unit Testing Asp.NetCore Web API Using xUnit[.NET6]

In this article, we are going to write test cases to an Asp.NetCore Web API(.NET6) application using the xUnit. xUnit For .NET: The xUnit for .Net is a free, open-source, community-focused unit testing tool for .NET applications. By default .Net also provides a xUnit project template to implement test cases. Unit test cases build upon the 'AAA' formula that means 'Arrange', 'Act' and 'Assert' Arrange - Declaring variables, objects, instantiating mocks, etc. Act - Calling or invoking the method that needs to be tested. Assert - The assert ensures that code behaves as expected means yielding expected output. Create An API And Unit Test Projects: Let's create a .Net6 Web API and xUnit sample applications to accomplish our demo. We can use either Visual Studio 2022 or Visual Studio Code(using .NET CLI commands) to create any.Net6 application. For this demo, I'm using the 'Visual Studio Code'(using the .NET CLI command) editor. Create a fo

A Small Guide On NestJS Queues

NestJS Application Queues helps to deal with application scaling and performance challenges. When To Use Queues?: API request that mostly involves in time taking operations like CPU bound operation, doing them synchronously which will result in thread blocking. So to avoid these issues, it is an appropriate way to make the CPU-bound operation separate background job.  In nestjs one of the best solutions for these kinds of tasks is to implement the Queues. For queueing mechanism in the nestjs application most recommended library is '@nestjs/bull'(Bull is nodejs queue library). The 'Bull' depends on Redis cache for data storage like a job. So in this queueing technique, we will create services like 'Producer' and 'Consumer'. The 'Producer' is used to push our jobs into the Redis stores. The consumer will read those jobs(eg: CPU Bound Operations) and process them. So by using this queues technique user requests processed very fastly because actually

Usage Of CancellationToken In Asp.Net Core Applications

When To Use CancellationToken?: In a web application request abortion or orphan, requests are quite common. On users disconnected by network interruption or navigating between multiple pages before proper response or closing of the browser, tabs make the request aborted or orphan. An orphan request can't deliver a response to the client, but it will execute all steps(like database calls, HTTP calls, etc) at the server. Complete execution of an orphan request at the server might not be a problem generally if at all requests need to work on time taking a job at the server in those cases might be nice to terminate the execution immediately. So CancellationToken can be used to terminate a request execution at the server immediately once the request is aborted or orphan. Here we are going to see some sample code snippets about implementing a CancellationToken for Entity FrameworkCore, Dapper ORM, and HttpClient calls in Asp.NetCore MVC application. Note: The sample codes I will show in

Blazor WebAssembly Custom Authentication From Scratch

In this article, we are going to explore and implement custom authentication from the scratch. In this sample, we will use JWT authentication for user authentication. Main Building Blocks Of Blazor WebAssembly Authentication: The core concepts of blazor webassembly authentication are: AuthenticationStateProvider Service AuthorizeView Component Task<AuthenticationState> Cascading Property CascadingAuthenticationState Component AuthorizeRouteView Component AuthenticationStateProvider Service - this provider holds the authentication information about the login user. The 'GetAuthenticationStateAsync()' method in the Authentication state provider returns user AuthenticationState. The 'NotifyAuthenticationStateChaged()' to notify the latest user information within the components which using this AuthenticationStateProvider. AuthorizeView Component - displays different content depending on the user authorization state. This component uses the AuthenticationStateProvider

How Response Caching Works In Asp.Net Core

What Is Response Caching?: Response Caching means storing of response output and using stored response until it's under it's the expiration time. Response Caching approach cuts down some requests to the server and also reduces some workload on the server. Response Caching Headers: Response Caching carried out by the few Http based headers information between client and server. Main Response Caching Headers are like below Cache-Control Pragma Vary Cache-Control Header: Cache-Control header is the main header type for the response caching. Cache-Control will be decorated with the following directives. public - this directive indicates any cache may store the response. private - this directive allows to store response with respect to a single user and can't be stored with shared cache stores. max-age - this directive represents a time to hold a response in the cache. no-cache - this directive represents no storing of response and always fetch the fr

Angular 14 State Management CRUD Example With NgRx(14)

In this article, we are going to implement the Angular(14) state management CRUD example with NgRx(14) NgRx Store For State Management: In an angular application to share consistent data between multiple components, we use NgRx state management. Using NgRx state helps to avoid unwanted API calls, easy to maintain consistent data, etc. The main building blocks for the NgRx store are: Actions - NgRx actions represents event to trigger the reducers to save the data into the stores. Reducer - Reducer's pure function, which is used to create a new state on data change. Store - The store is the model or entity that holds the data. Selector - Selector to fetch the slices of data from the store to angular components. Effects - Effects deals with external network calls like API. The effect gets executed based the action performed Ngrx State Management flow: The angular component needs data for binding.  So angular component calls an action that is responsible for invoking the API call.  Aft

Angular 14 Crud Example

In this article, we will implement CRUD operation in the Angular 14 application. Angular: Angular is a framework that can be used to build a single-page application. Angular applications are built with components that make our code simple and clean. Angular components compose of 3 files like TypeScript File(*.ts), Html File(*.html), CSS File(*.cs) Components typescript file and HTML file support 2-way binding which means data flow is bi-directional Component typescript file listens for all HTML events from the HTML file. Create Angular(14) Application: Let's create an Angular(14) application to begin our sample. Make sure to install the Angular CLI tool into our local machine because it provides easy CLI commands to play with the angular application. Command To Install Angular CLI npm install -g @angular/cli Run the below command to create the angular application. Command To Create Angular Application ng new name_of_your_app Note: While creating the app, you will see a noti