Our Cookie Policy

Echofavor and carefully selected third parties use cookies on this site to improve performance, for analytics and to show you offers tailored to your interests on our site and third party sites. By continuing to use our site, you consent to our use of cookies. Privacy Policy

Life is memorable. Share your experience. Help others. Return the favor. Terms Of Use    Privacy Policy    About    FAQ    Help   Contact Us  
As an Amazon Associate and affiliate with other third parties, Echofavor earn from qualifying purchases and display advertisements.
0.0868184

(Collection)Blazor Articles

  • mcchu28
  • 197 views


Sep. 17, 2018 - .NET in the browser (Michael Desmond)

  • 80 views
Here are my notes based on this article:

The Web Assembly- based .NET runtime needs improvement:
  • smaller download sizes
  • better runtime performance
  • support for .NET Standard 2.0
  • IL linker needs to scrub more unused code
  • support for Ahead-of-Time compilation
Blazor component model:
  • template-based components
  • forms and validation
  • handling more event types
  • support for Visual Studio Code




Sep. 17, 2018 - C# in the Browser with Blazor (Jonathan Miller)

  • 90 views
Here are my notes on this article:

  • bring C# into any browser that supports WebAssembly without a plug-in
  • make C# language a full-stack development tool
  • Blazor apps access Web services using HTTP REST APIs
  • WebAssembly (WASM) is a binary format that can be loaded and run directly in the browser and is currently supported by all the major browsers
  • The Mono team is working hard on a version of the .NET runtime that runs in WASM
  • The @ sign signals code and variables
  • The button tag has its onclick method bound
  • Variables and methods are defined inside the @functions block
  • Talks about publishing the Blazor Application using Publish to Folder option




Sep. 17, 2018 - Never Mind JavaScript, Here's Blazor (Dino Esposito)

  • 98 views
Here are my notes from this article:

  • about a decade ago, Silverlight as a separated browser plug-in was taking off in the web development world
  • then HTML5 came out and did not support technologies like Silverlight
  • That gives a big boost to JavaScript and today frameworks like Angular, React and Vue are very popular
  • Then comes Blazor enabled by WebAssembly (WASM) to bring .NET, specifically C# to client-side web development
  • One can use Razor tag helpers to extend the HTML syntax
  • Blazor is still largely in development
  • A bridge is needed to convert the .NET runtime to WASM. Blazor relies extensively on work done by Xamarin to bring its Mono framework to WASM.
  • at this moment Blazor polyfill was temporarily not working with Internet Explorer.
  • client-side Blazor is a .NET Standard 2.0 console application which uses Blazor.Build and Blazor.Browser
  • routing - @page notation
  • href - canpoint to name of another component
  • component fields are defined in @functions section
  • when event originates programmatically such as a timer, you need to call method StateHasChanged to force the browser renderer to refresh the view


  

Copyright © Echofavor 2021. All Rights Reserved. Powered by Echofavor
Copyright © Echofavor 2021. All Rights Reserved.
Powered by Echofavor