Sharing Code and Resources (Part 2)

By Ashwin Venugopal -

 




Cleaning Up The Shared Files

Let's make sure the moved files have matching namespaces:

  • In the MyBlog.Shared project, change the namespace to MyBlog.Shared. Components on the following files-

Components/BootstrapFieldCssClassProvider.cs

Components/ CustomCssClassProvider.cs

  • Remove @using MyBlogServerSide.Components from the following files-

Pages/Admin/BlogPostEdit.razor Pages/Admin/BlogPostList.razor Pages/Admin/CategoryList.razor Pages/Admin/TagList.razor

  • In the MyBlog.Shared project, add the following namespaces to the _Imports.razor file-

@using MyBlog.Shared

@using MyBlog.Shared.Components

We have cleaned up a couple of new projects.

Adding The API

Perform the following steps:

  • In the MyBlogWebAssembly.Client project, open Program.cs and add the following-

builder.Services.AddScoped <IMyBlogApi>;

MyBlogApiClientSide >();

  • Add the following namespaces at the top of the file-

using MyBlog.Data;

using MyBlog.Data.Interfaces;

  • Delete the Pages/Index.razor file (since we will be getting that one from our shared library instead).

  • The same goes for Shared/NavMenu.razor. Delete that file as well.

  • Open App.Razor and, in the router component, add the following as an additional property-  

AdditionalAssemblies="new[] { typeof(MyBlog.Shared.Pages. Index).Assembly}"

  • This is telling the router to look for matches in the current project, but also in the MyBlog.Shared assembly.

  • Add the following namespaces to _Imports.razor-

@using MyBlog.Shared

@using MyBlog.Shared.Shared

  • In the MyBlogWebAssembly.Server project, open the Startup.cs file and replace services.AddControllersWithViews().

  • Set MyBlogWebAssembly.Server as the start-up project by right-clicking the project and selecting Set as Startup Project and pressing Ctrl + F5.

  • You should now see blogposts getting listed and you should be able to navigate to a blog post by clicking the link.

Conclusion

We now have the same Blazor components running in Blazor Server as well as Blazor WebAssembly.

















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