Blazing Trails with Blazor




There is anew way to build web applications using C# and .Net Core, it is called Blazor.Net.  It is an experimental technology that leverages the mono run time in a browser, via web assembly, while utilizing the Razor engine from Asp.Net.   This article is not to explain the details about Blazor but to reflex on why I am excited about it and my experiences learning and using it.

Here is a set of links that I have already gather to help me get started on the Blazor trail:


I have worked on the front end of web side for many years building business applications.  I would not say I know JaveScript and CSS, I can manage my way through them.  My strength is with C#, so when I heard I can “replace” JavaScript on the front end with C#, I got very excited.

Blazor still using CSS, HTML and JavaScript, but the core the frontend coding can now be done in C#.  What I like thus far about Blazor is the ease of wiring in events, it’s dependency injection and the code reuse it will allow me to use.

Blazor, like other web technologies that have come before it, only time will tell if it will be successful.  I just want to help spread the word.

I am planning a series of post to show real application implementation of common components and features.  I want to see how Blazor holds up with more then the traditional “Hello World” and “to-do” applications.

Upcoming articles:
  •           Multiple UI Layouts
  •           Log in Form
  •            File Upload
  •           View Media


It should be fun.



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