Blazor UI Component Library


 I was reviewing some sample code the other day and I noticed that the index.html file had a lot of linked CSS files.  This got me thinking:

"Question: If UI components are in separate assemblies and use CSS isolation, would you still need to include the CSS file?"


The short answer is NO.  if you use CSS isolation, you don't need to include the CSS files.

We can go from this:

<link href="ComponentLibCSS.styles.css" rel="stylesheet" />

<link href="/_content/Assembly1/styles.css" rel="stylesheet" />

<link href="/_content/Assembly2/styles.css" rel="stylesheet" />

<link href="/_content/Assembly3/styles.css" rel="stylesheet" />

<link href="/_content/Assembly4/styles.css" rel="stylesheet" />

To just this:

<link href="ComponentLibCSS.styles.css" rel="stylesheet" />


A key point to remember for this you must be on .Net 5 or greater.  That is when CSS isolation was released.


Proof - Component Library

I am one to prove things to myself.  I have created a couple of projects to validate my thinking.

The first one is the basic Blazor web assembly project.  I have removed the counter page for simplicity.  Within this solution, I have a Razor component UI library that I add as a project dependency to the web assembly project.

The trick to building this was that the UI Component library must be a Razor Component Library project type.  Believe it or not, that was harder to figure out than I had expected it to be :-)



When the user clicks on the "Fetch Data" navigation link, there is a "loading spinner" that is a component in the component library.

The spinner is made up of HTML and CSS.  There is a 2-second delay in the fetching of the data, just to allow the user to see the spinner.

This worked very nicely.  I did not have to include any additional CSS files for the component library.





Proof - Nuget Package


The component library working, led me to ask the same question but for a NuGet package.

Again the short answer was Yes it would work.

To prove this, I cloned the web assembly project but not the component library.  I took the component library and built a local Nuget package.

With the NuGet package in hand, I added it to the cloned web assembly project and sure enough, everything ran as before.  I found this very impressive.

I have included all the source code I used to validate this.  This may have been obvious to most, but I wanted to prove it.  Besides you can never go wrong building Blazor Applications.




Comments

Post a Comment

Popular posts from this blog

Yes, Blazor Server can scale!

Image
From the very beginning of the release of Blazor Server naysayers have incorrectly stated that Blazor Server can not scale.  They usually state that the limit is 5,000 concurrent users. There are several misconceptions and wrong assumptions about their statement.  Let's break it down and get a better understanding of Blazor server-side scaling. What is the "limit" for users When Microsoft talks about the need to scale an application, what they are saying is that when a normal response for any concurrent user is taking longer than 200 ms, the system is not performant and needs to scale. We will accept that definition: If any normal user response is taking longer than 200 ms, the system needs to scale for concurrent users. By a normal response, we are referring to a page get, a post, etc.  Large database access requests would not be included in this measurement. What is scaling There are 2 common ways to scale, scale, out horizontally, and scale-up, up vertically. In our di
Read more

Blazor new and improved Search Box

 Back in March, I posted a new Blazor data grid with a search box ( see post ).  Since then I have found a new and improved search box that I wanted to implement.  The search part is implemented the same.  What I added was the ability for the user to narrow down the search by selecting which field they wanted to search on.  This will help the user find what they are looking for and in a large collection, the search will end up being faster. The goal of making the change was to make the search box a new component and have it handle the UI functionality part. Prep Work Here is the prep work I did before adding the search box: Started with the source code from the post listed above. Upgraded the project to .Net 5 Upgraded the Nuget packages that were out of date. Ensured every build and run. Change to a Component I wanted to create a component for the search box so I could use it in other applications.   1. Create a Folder under UIControls called "SearchBox" 2. Created a new raz
Read more

Blazor Wizard Step Component

Image
 I like using step wizards in my applications, sign-up forms, shopping cart checkout, and complex data entry, but I had not been able to find a wizard step indicator that I liked so I built this one. As it turned out, it was not as hard as I thought it would have been.  There are a couple of key parts you have to keep in mind when using a step wizard, such as: 1. What step am I on? 2. Should the "Prev" / "Next" buttons be enabled or disabled on this step? 3. What kind of visual clues do I show the user? I will walk you through how we answer these questions in this sample project.   HTML The main container has a div that holds the progress divs, one div for each "step" of your process.  Below that we have our "Prev" and "Next" buttons We will need to wire in the on-click events for the two buttons.  The buttons will need to be able to be disabled and enabled via CSS class settings.           <div class="container">       
Read more