Blazor Tip - Upgrade Bootstrap


 

The current Blazor templates ship with the Bootstrap version v5.1.0, the current version is v5.3.  It may not seem like a big difference, but it is nice to get the latest version when you start a new project. You could use NPM or Nuget to upgrade your bootstrap, but there is an easier way.  

We will be using the CDN link for our bootstrap.  This has several advantages that will help us.

1. Loads faster
2. Loads even faster if it is already cached in the browser.
3. Remove the download of the files from your server.
4. You can delete the old bootstrap files from your project.

There are a couple of simple steps to do this upgrade.


2. Find the "Include via CDN" link and copy it.
3. In the Blazor app replace this line:

    <link rel="stylesheet" href="bootstrap/bootstrap.min.css" />

with:

    <link href="https://cdn.jsdelivr.net/npm/bootstrap@5.3.3/dist/css/bootstrap.min.css" rel="stylesheet" integrity="sha384-QWTKZyjpPEjISv5WaRU9OFeRpok6YctnYmDr5pNlyT2bRjXh0JMhjY6hW+ALEwIH" crossorigin="anonymous">

Note: The location of the link will depend on which Blazor project you are creating.

4. Test to ensure everything looks good.
    a. upgrading from 5.2 to 5.3 causes the icons on the nav to move to the left.  To fix this you just need to add ps-3 to the nav link

        <NavLink class="nav-link ps-3" href="" Match="NavLinkMatch.All">

5.  Remove the old Bootstrap folder from under the wwwroot folder.


It needs to be noted that you should be careful when upgrading to any major version.  Most major versions have breaking changes within them.  Make sure you do your research first.


Summary

Doing this simple change can ensure you are starting your next project with the most current Bootstrap version and it will allow you to take advantage of the Bootstrap CDN saving your resources.

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 - Cool Blur Loading Page

Image
  I was working on a project and wanted an original way of showing the user the application was loading besides using the normal "Loading...." text.  I came across a website page and thought I could refactor that into what I was looking for. When my application starts, it displays a full-screen image with a count down while the page loads.  As a special effect, I want to unblur the image the closer it gets to the applicaiton finishing loading.  Once the teh count down is done, we pause for 1 sec, for effect, then proceed to the application.  I think it turned out pretty cool.  See the demo here . I used the server side Blazor project template in my example, but the code should work on any Blazor template. Template changes 1. Rename the original Index.razor page to "home".  Besure to change the routing at the top of the page as well.      @page "/home" 2. Create a new Index.razor page     a. Add routing      ...
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 "SearchB...
Read more