.Net Conf 2020 Day 3


 Summary

I learned my lesson from trying to attend too many sessions yesterday.  Today I am focusing on the Blazor sessions.


1. Application State in Blazor

  • Blazor Train on YouTube - Carl Franklin
    • It was nice to hear Carl again
    • Been a fan since early .Net Rocks
  • App State
    • Instances of objects stored in memory
    • SPAs are stateful
    • Scoped 
  • Create "State Bag" - User Scoped
    • 1 instance per user
    • Class for object reference
    • Use scope service
  • For application instance use Singleton
    • Web Assembly - not needed because there is 1 user
  • Class level
    • Transient
    • Multiple copies of the same data across pages
  • Implement a state bag
    • Cascading Component
    • Scoped Service
    • Hybrid Approach
      • Cascading Component with scope service
  • Add the Hybrid solution at the router level
    • It is like making an observable at the app level
  • In AppState service, he is handling events as opposed to just holding state
  • Saving Application-level state
    • Local Storage
      • 5 Meg limit
      • AppState Persistence Pattern
      • Do it in 1 location
    • On Server use the new function
      • Protected Local Storage (Server Side only)
    • You can check to see how much local storage you have left

2. Blazor Stability Testing Tool

  • Blazor is inherently testable because it is all C#
  • Tests
    • Unit
    • Integration
    • System
      • Ad for Telerik Test Studio
  • Unit test
    • Reg Green  Refactor
    • xUnit
  • bUnit
    • C# or Razor
    • Semantic HTML compare
    • How they find CSS classes it pretty cool
    • You can mock JSInterop
  • Telerik Test Studio
    • Has a test recorder for Blazor UI

3. Web Forms to Blazor

  • Making Blazor components from Win Form components
  • Current web forms only 4.8
  • Blazor Server-Side very similar to Web Forms 
    • Not the same
      • <%%>
      • View State
      • Postback
      • Only Windows
  • Used bUnit to validate that the markup was the same as a Web Form
  • Make sure your class libraries are .Net Standard
  • E-book
  • Look at CodeFactory to automate

4. Dynamic Applications with Blazor

  • Benefits
    • Extensibility
    • Parallel Development
    • Conventions
    • Encapsulation
    • Deployment
  • Difficult to create
    • Most use frameworks
      •  Batteries Included
        • Rails
        • Django
        • sprint
  • CMS => Dynamic system?  No
  • .Net Web frameworks
    • DNN
    • Orchard
    • Umbraco
  • Blazor - single-page application formwork
  • Oqtane
    • "Batteries included" Blazor framework
    • Includes
      • Multi-Tenant
      • Portal UI framework
      • Granular Permissions
      • Admin User Interface
      • Dynamic Routing
      • Modular Architecture
      • Customizable Themes
      • Headless API and repository
  • The session ended up being a demo of Oqtane.  I was hoping to see how to build dynamic pages

5. Building cross-platform apps with Electron.Net

  • Supports 
    • Windows
    • OSX
    • Linus
  • Electron.Net is a wrapper around normal Electron
    • CLI extension
    • Support .Net 5.0
  • Cool demo
    • Created ASp.Net COre web site
    • Add reference to Electronic .net NuGet
    • Have to install Electron.Net CLI
    • Run through command line in VS code
    • You have to attach to the running process to debug
    • You can even use 3rd party controls
  • Builds
    • Use Electronize
  • Should work with Blazor
  • GitHub Repro of demo

6. Build native and hybrid mobile apps with Mobile Blazor Bindings

  • This was a good overview of the mobile bindings
  • Definitely worth looking in to
  • Note that it is not ready for prime time
  • Mobile bindings
    • Author native UO using Blazor Engine
    • Host web content in a web view to run locally
    • Run natively on 
      • Android
      • iOS
      • macOS
      • Windows
    • Access all native functions on each platform


DotNetConf was a good set of sessions that cover a wide range of topics.  The 24 hour day was a little rough but some of the sessions were well worth it.  For day 3 I had to attend a smaller number of sessions but it did help me take in the information a lot better. 

     

                                            


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