Full stack web development with c# and web assembly - Blazor.Net

Editor's Notes

• #6: Dot Net Anywhere : Dot Net Anywhere is a interpreted .NET Common Intermediate Language (CIL) runtime. Blazor.net: Blazor is a .NET web framework that runs in any browser. You author Blazor apps using C#/Razor and HTML. Blazor uses only the latest web standards. No plugins or transpilation needed. It runs in the browser on a real .NET runtime (Mono) implemented in WebAssembly that executes normal .NET assemblies. It works in older browsers too by falling back to an asm.js based .NET runtime. http://blog.stevensanderson.com/2017/11/05/blazor-on-mono/ https://blogs.msdn.microsoft.com/webdev/2018/02/06/blazor-experimental-project/
• #8: This allows us to take advantage of WebAssembly's performance and power and JavaScript's expressiveness and flexibility during development, even if you don't know how to write WebAssembly code. JavaScript is a powerful language but it has its disadvantages. Some are fixed by TypeScript. However, using C# for client-side web development is compelling for many people because of reasons like the following: C# is a very robust and feature-rich language that has proven to be successful for projects and teams of all sizes Existing C# code could be re-used ASP.NET Core is a powerful programming framework for server-side web development. Enabling C# on the client would allow teams to use a common technology stack on server and client. Source: https://developer.mozilla.org/en-US/docs/WebAssembly
• #9: There are several components that make up Mono: C# Compiler - Mono’s C# compiler is feature complete for C# 1.0, 2.0, 3.0, 4.0, 5.0 and 6.0 (ECMA). A good description of the feature of the various versions is available on Wikipedia. Mono Runtime - The runtime implements the ECMA Common Language Infrastructure (CLI). The runtime provides a Just-in-Time (JIT) compiler, an Ahead-of-Time compiler (AOT), a library loader, the garbage collector, a threading system and interoperability functionality. .NET Framework Class Library - The Mono platform provides a comprehensive set of classes that provide a solid foundation to build applications on. These classes are compatible with Microsoft’s .Net Framework classes. Mono Class Library - Mono also provides many classes that go above and beyond the Base Class Library provided by Microsoft. These provide additional functionality that are useful, especially in building Linux applications. Some examples are classes for Gtk+, Zip files, LDAP, OpenGL, Cairo, POSIX, etc. Source: https://www.mono-project.com/docs/about-mono/
• #11: Razor has its roots on the server where it is typically used to dynamically generate HTML. In Blazor, Razor is used on the client. To be more specific, the Razor engine runs during compilation to generate C# Code from Razor templates. Unlike former platforms like Silverlight, it does not bring its own rendering engine to paint pixels on the screen. Blazor uses the Browser’s DOM to display data. 
• #12: C# code running in WebAssembly cannot access the DOM directly. It has to go through JavaScript.  The C#-part of Blazor creates a Render Tree which is a tree of UI items. The render tree is passed from WebAssembly to the Rendering in the JavaScript-part of Blazor. It executes the corresponding DOM changes. Whenever the user interacts with the DOM (e.g. mouse click, enter text, etc.), the JavaScript-part of Blazor dispatches an event to C#. The event is processed by the C#-code of the web app. If the DOM changes, a Render Batch with all the UI tree differences (not the entire UI tree) is built in C# and given to a JavaScript Blazor method that applies the DOM changes. Because Blazor is using the regular browser DOM, all usual DOM mechanisms including CSS work keep working. Source: https://learn-blazor.com/getting-started/what-is-blazor/
• #13: You can get up and running with Blazor using either Visual Studio 2017 preview or VS Code. Regardless of which you choose you must first install the .NET Core 2.1 preview. VS Code Install blazor project template - new -i Microsoft.AspNetCore.Blazor.Templates
• #14: Blazor Project Type This is the project to select when you are interested in creating a client-side only application. There is no backing API included. Blazor (ASP.NET Core Hosted) This project is for full stack C# development. You get the same client-side project as with the Blazor only template, but with this template you also get an ASP.NET Core WebAPI project as well. ` Once you have selected the project template you want to have a play with, click OK and you should be looking at a new Blazor project ready to go. You can run the project straight away and you should see the basic start app after a few seconds. This project type allows developers to create reusable component libraries that can be shared between projects or packaged up as nuget packages. Currently this can't be added from the menus in Visual Studio, it can only be added using the CLI. In order to create a new Blazor Library project you need to have the latest templates installed.
• #16: What is a Component Like all modern front end frameworks Blazor has components at its core. Blazor uses a combination of C#, Razor and HTML to create components.  Types of Components Inline Code behind Class only
• #20: Blazor community resources includes Libraries, Samples, Tooling, Documentation