Blazor Web Assembly Latest release

With the latest release of Blazor Web Assembly 3.2.0 Preview 3.0 they have made great strides in getting the Blazor web assembly version production ready.

The official GA release is for May 2020 and there will be at least 3 more preview release between now and the GA release. 

See the ASP.Net Blog post for the latest instructions on how to install and run the latest preview.

What's in this preview:

1. .Net Standard 2.1
2. Standalone and hosted models
3. IL trimming
4. Web Sockets
5. .Net SignalR Client
6. Static Web assets
7. Authentication and authorization
8. Progress Web Application template
9. Localization and Globalization
10. External Configuration files
11. Debugging
12 Compression

.Net Standard 2.1


You can now use .Net Standard 2.1 Library projects in your Blazor web assembly projects

Standalone and Hosted models


These 2 hosting model s are back.  These were available when the web assembly model was first released but remover be the initial release.  Here is my initial post on hosting


IL Trimming


This is part of the compression work being done to make the initial download of files smaller.

Web Sockets / SignallR Client


This support was added to enable SignalR support in the web assembly model

.Net Static Web Assest


They added the MVC static page support to the web assembly model since in the standalone hosting model is just a static web site.

Authentication and Authorization 


Now with the web assembly template, you can add authentication and authorization to your application.  It works just like the server side Blazor application.

It will support Authorized Views, roles and the other security features.  In this preview it only supports "User Individual Accounts".  With a command line template you can create an application you can support Active Directory security as well.

With the GA release the rest of the .net core security models will be supported.   Here is my post about server side authentication and authorization


Progressive Web Applications

This is really cool.  Now there is a new template that will allow you to create a PWA project.  It works just like creating a standard Web Assembly project.

I will be creating a much deeper blog post on creating a PWA.


Localization and Globalization

This is another pretty cool feature that was added.  Globalization is the formatting and parsing of dates and currencies.  With this feature,  the web assembly application will automatically use the browsers setting.  

Localization is the translation of display strings into another language.  It does this using the standard .net core localization.  You defined the strings in standard resource files and in the start class you set the location of the setup files.


External Configuration files


Now with the web assembly application you can use external configuration files and have multiple configuration files such as dev, stage and production.  This brings the web assembly application on par with the other .net core applications.


Debugging


This is on par with the PWA template as the coolist feature added.  You can now debug right in Visual Studio or VS Code.  You no longer have to use the browser to debug.  You can use Visual Studio to set break points and inspect variable values.  This is the first phase of added debugging to the web assembly.  The team still has more debugging features to add but this is a great step forward.

Compression

They are continuing to decrease the downloadable size of the files.  They have it at about 1.8 M.  Their goal is to reach 1.5M by GA.


Piggy back on ASP.Net Blog and the Asp.Net Community Stand-up

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