.Net 5.0 Blazor Goodness

 


With the release of .Net 5.0 quickly approaching it is time to take a look and see what kind of goodies are include for Blazor.

.Net 5.0 is aimed at unifying the .Net platform by commuting all the different aspects of the platform into a single release set.  But they have including a lot of upgrades and new features for Blazor.  To see these new features you have to be using at least Visual Studio 2019 16.8 Preview 3 and have .Net 5.0 install on your machine.

Here are the new features that I have found exciting.  See the linked source code to see them in action.

  1. CSS isolation
  2. Input Radio Component
  3. UI Focus Support
  4. File Input Component
  5. On-toggle Event Support 


CSS Isolation


With this feature, you can now include separate style sheets that are scoped just for your components.  This will allow you to provide the styling you want for your component libraries or just your individual component.

This is implemented by convention.  You provide a CSS file named the same as your component razor file.

You put all your styles in this file and they only have the scope of your component.  You can control the styling of child components by using the ::deep CSS selector

example: 
MyComponet.razor would have a MyComponet.razor.CSS style file for it.  In the solution explorer, it even places the style sheet under the component file.


Makes things clean and simple.


Input Radio Component

They have added an InputRadio control and the InputRadio Group control.  These work like the InputText control.  You can data bind the control with the @bind-value and they support integrated validation.


    <InputRadioGroup @bind-Value="survey.OpinionAboutBlazor">
        @foreach (var opinion in opinions)
            {
            <div class="form-check">
                <InputRadio class="form-check-input" id="@opinion.id" Value="@opinion.id" />
                <label class="form-check-label" for="@opinion.id">@opinion.label</label>
            </div>
            }
    </InputRadioGroup>

This new control fits in with the other input controls on the EditForm component and adds consistency to the form.

 UI Focus Support


This feature might not sound like much but after having to use JSInterOp to just set the first control on a page to have focus, this is great to see. 

To use this, you have to set an element reference to the control you want to set focus on and then after render call a method to set the focus:

          ElementReference textText;  

          public async Task Focus(ElementReference textInput)
         {
              await textInput.FocusAsync();
          }

I was not able to get it to set focus on an InputText control, for that I would still have to use the JSInterOp.  Hopefully, they will resolve that use case as well.


File Input Component


I am glad to see this control added, but it was one of the first control I made and drew a lot of attention on this blog.  But it is always nice to have a good file input control built-in. 

It can handle single or multiple files uploaded.  It works with Server-Side or Web Assembly Clients.  

The use of it is what you would have expected:

      <InputFile OnChange="OnInputFileChange" multiple />

      async Task OnInputFileChange(InputFileChangeEventArgs e)
      {
         var imageFiles = e.GetMultipleFiles();
      }

This is a nice addition to the built-in controls.

On-toggle Event Support


The On toggle event will allow you to better use the HTML <details></details> tags.  To use it, you add a flag and toggle the flag on the details click:

        <details id="details-toggle" @ontoggle="OnToggleRun">
            <summary>Summary</summary>
            <p>Detailed content</p>
       </details>

        @if (detailsExpanded)
        {
            <p>Read the details carefully!</p>
            <img src="/blazorCode.png" width="300" height="300" />
        }

        @code {

               bool detailsExpanded;
               string message { get; set; }

               void OnToggleRun()
              {
                   detailsExpanded = !detailsExpanded;
              }
        }

This may seem simple, but it is a nice UI element to use.

Other Enhancements


There are a lot of good enhances across the board in .Net 5.0.  Please check out the ASP.Net Blog for all the details.  

Here is a quick summary:

  • Lots of Web Assembly Performance enhancements
  • Inputs support aria-invalid by default
  • Influencing HTML head attributes
  • Protected Local Storage
  • Component Virtualization
  • Web Assembly Pre-rendering
  • Browser Compatibility for Web Assembly
  • JavaScript isolation and object reference
  • Custom validation class attributes



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