Managing State (Part 2)

By Ashwin Venugopal -

 





Implementing Browser Storage

The web browser offers various methods for storing data, each with different handling based on the type utilized. Local storage is limited to the specific browser window being used by the individual. Even if the user refreshes the page or exits the web browser entirely, the data will remain intact.

The information is also accessible across different tabs. Session storage is limited to the specific browser tab. If you refresh the tab, the data remains, but closing the tab will result in loss of the data. SessionsStorage can be considered safer because it minimizes the potential issues that could arise from multiple tabs altering the same stored values.

To be able to access the browser storage, we need to use JavaScript. In .NET 5, Microsoft rolled out Protected browser storage, leveraging data protection features in ASP.NET Core, although it is not accessible in WebAssembly. Nevertheless, we can utilize an open source library named Blazored.LocalStorage, which is compatible with both Blazor Server and Blazor WebAssembly.

Creating An Interface

First, we need an interface that can read and write to storage:

  • In the MyBlog.Shared project, right-click on the project name and select Add|New Folder. Name the folder Interfaces.

  • Select the new folder and create a new class by pressing Shift+ F2, and name the file IBrowserStorage.cs.

  • Replace the content in the file with a code.

Now we have an interface containing get, set, and delete methods.

Implementing Blazor Server

For Blazor Server, we will use protected browser storage:

  • Right-click on the MyBlogServerSide project and select Add|New folder. Name the folder Services.

  • Select the folder and press Shift+ F2. Name the file MyBlogProtectedBrowserStorage.cs.

  • Open the new file and add the following using statements-

using Microsoft.AspNetCore.Components.Server.

ProtectedBrowserStorage;

using MyBlog.Shared.Interfaces;

using System.Threading.Tasks;

  • Replace the class.

  • In Startup.cs, add the following namespaces-

using MyBlog.Shared.Interfaces;

using MyBlogServerSide.Services;

  • Add the following at the bottom of the ConfigureServices method-

services.AddScoped<IBrowserStorage , MyBlogProtectedBrowserStorage> () ;

  • Protected browser storage will use JavaScript to get the information, and we can only do those calls from OnAfterRenderAsync or OnAfterRender, but there is another way. The reason for JavaScript not working in places other than the OnAfterRender methods is the pre-rendering feature of Blazor Server.

  • Open Pages/_host.chtml and change the render mode from <component type= “typeof (App)” render-mode= “ServerPrerendered” /> to <component type= “typeof (App)” render-mode= “Server” />. This will make it possible for us to call JavaScript outside of the OnAfterRender methods.

We are configuring Blazor to return an instance of MyBlogProtectedBrowserStorage when we inject IBrowserStorage.

Conclusion

We have successfully implemented Blazor servers and Browser storage.

















Comments

Post a Comment

Popular posts from this blog

Information Protection Scanner: Resolve Issues with Information Protection Scanner Deployment

By Ashwin Venugopal -
Image
  About If you are experiencing problems with the Microsoft Purview Information Protection scanner, check the health of your deployment by utilizing the Start-ScannerDiagnosticsPowerShell cmdlet to start the scanner diagnostic tool. The diagnostics tool checks the following details and then creates a log files with the results: Whether the database is up to date. Whether network URLs are accessible. Whether there's a valid authentication token and policy can be acquired. Whether the profile is defined in the Azure portal. Whether offline/online configuration exists and can be acquired. Whether the rules configured are valid.  The Start-ScannerDiagnostics command does not perform a comprehensive check of prerequisites. If you encounter problems with the scanner, you need to verify that your system meets the scanner's requirements, and that your scanner's configuration and installation are finished.  Verify Scanning Details Per Scanner Node and Repository Run the Get-ScanSt...
Read more

How AMI Store & Restore Works?

By Ashwin Venugopal -
Image
  CreateStoreImageTask The CreateStoreImageTask API stores an AMI as a single object in an S3 bucket. The API initiates a task that collects all the data from the AMI and its associated snapshots, subsequently using an S3 multipart upload to store this data in an S3 object. It gathers all elements of the AMI, including most of the non-Region-specific metadata and all EBS snapshots included in the AMI, and consolidates them into a single object in S3. During the upload process, the data is compressed to minimize the space utilized in S3, which means that the S3 object could be smaller than the total sizes of the snapshots in the AMI. If the account making this API call has access to AMI and snapshot tags, they will be retained. The S3 object shares the same ID as the AMI, except it has a .bin extension. Additionally, the S3 metadata tags for the object include the AMI name, AMI description, AMI registration date, AMI owner account, and a timestamp indicating when the store operation...
Read more

Create A Store Image Task

By Ashwin Venugopal -
Image
  Introduction When you save an AMI in an S3 bucket, a task for storing the image is initiated. This store image task allows you to track the progress and result of the procedure. Securing your AMIs It is crucial to verify that the S3 bucket is set up with adequate security to protect the content of the AMI and that this security is upheld for the entire duration that the AMI objects are stored in the bucket. If this cannot be achieved, it is advisable to refrain from using these APIs. Make sure that public access to the S3 bucket is prohibited. It is suggested to activate Server-side encryption for the S3 buckets where you keep the AMIs, even though it’s not mandatory. When AMI snapshots are transferred to the S3 object, they are sent over TLS connections. It is possible to save AMIs that contain encrypted snapshots; however, the snapshots will be decrypted during the storing process. Identify the source AMI used to create a new Amazon EC2 AMI You can determine the AMI that was us...
Read more