− Glimpse into the future of application development − Seeing the web in action as the platform − “Native” programming languages running in your browser − Sneak Peek: Single-Page Applications with .NET − Demos ☺ − WebAssembly/mono-wasm/ Blazor Deep Dive − Future-proof tutorial (WebAssembly is stable, but mono-wasm/Blazor aren’t) − Flash, Silverlight, Java Applets or other Plugins .NET auf dem Weg, den Browser zu erobern?
1. Modern Business Applications & the Web 2. WebAssembly: Native Bytecode for the Web 3. Mono & WebAssembly: .NET Comes to the Browser 4. Blazor: Single-Page Apps Come to C# .NET auf dem Weg, den Browser zu erobern?
Frontend Technologies • HTML5 • CSS • JavaScript Modern Web APIs • WebAssembly • Web Audio API • Gamepad API • Media Capture and Streams • Web Bluetooth API Single-Page Web Applications • Angular • React • Vue Backend Technologies • .NET Core • Node.js .NET auf dem Weg, den Browser zu erobern?
− Native operating systems & platforms get less important for users − Windows, Linux, macOS, Android, iOS: a mixture of everything, anywhere − Desktop is still important: not everything is mobile − Software developers need to care about & target ubiquitous systems − Depending on the actual audience, on the actual use cases − The Web has proven to be a universal platform − Modern browsers are power horses – more or less like an operating system .NET auf dem Weg, den Browser zu erobern?
.NET auf dem Weg, den Browser zu erobern? Compiler Parser JIT Web APIs (DOM, IndexedDB, File Storage etc.) Browser JavaScript (.js) HTML (.html) Inline JS JS Runtime
− Low-Level Bytecode for the Web − High execution speed − Fast, efficient, portable − Readable and debuggable − Uses existing sandboxing tools − Part of the open, backwards- compatible web .NET auf dem Weg, den Browser zu erobern?
− Implemented in all major browsers (2017+) − Evergreen browsers (Chrome 57, Edge 16, Firefox 52 (not yet in ESR), Safari 11) − Desktop and mobile − Feature parity with asm.js was the goal − Native technology (i.e. no plug-ins!) − Idea: Bring all programming languages to the browser − Targeted at languages such as C, C++ or Rust (= languages without garbage collection) − Achieves superior performance for some use cases − Addition to JavaScript (not a replacement!) − JavaScript glue code is still required to load a WebAssembly − Currently, JavaScript counterpart is required for accessing the DOM .NET auf dem Weg, den Browser zu erobern?
− After v1 (the MVP), the consortium keeps working on new features − Threads (already in Chrome 70) − Garbage Collection − Reference Types − Direct DOM access − Many more things… − https://github.com/WebAssembly/design/blob/master/FutureFeatures.md − BTW: WASM also works on the server − e.g. WASM loader for Node.js − https://github.com/wasm-tool/node-loader .NET auf dem Weg, den Browser zu erobern?
.NET auf dem Weg, den Browser zu erobern? Compiler Parser JIT Web APIs (DOM, IndexedDb, File Storage etc.) Browser JavaScript (.js) HTML (.html) Inline JS JS Runtime WebAssembly (.wasm)
− Re-use existing code by targeting WebAssembly, embedded in larger JavaScript/HTML application − Anything from simple helper libraries, to compute-oriented task offload − Main application frame & logic in WebAssembly, UI in JavaScript/ HTML/CSS − Entire code base in WebAssembly − With a tiny bit of loading and Web API – bridging JavaScript .NET auf dem Weg, den Browser zu erobern?
− Baremetal: WebAssembly Studio − Playing around with WASM in the browser − C/C++ tools & compilers − Binaryen: compiler and toolchain infrastructure library for WebAssembly, written in C++ − LLVM: The modern C/C++ compiler toolchain − Emscripten: LLVM-to-JavaScript-or-WASM compiler − Tools cross-compiling from major languages − Cheerp (from C++) − TeaVM (from Java) − Rust − mono-wasm (from C#) .NET auf dem Weg, den Browser zu erobern? C / C++ Source code .wasm module HTML doc JS glue code Emscripten +
− Mono is Microsoft’s strategy for cross-platform client applications − Xamarin is based on Mono, Unity as well − Support for .NET Standard − Mono team is working on tooling to compile Mono/.NET code to WASM − Two approaches − JIT – for fast development cycles, including live reload (part of mono-master) − AOT – for optimized runtime deployment & execution (aka mono-wasm) .NET auf dem Weg, den Browser zu erobern?
using System; public class Hello { public static void Main(string[] args) { Yell("Hack"); } public static void Yell(string text) { Console.WriteLine($"{text.ToUpperInvariant()}!!!"); } } .NET auf dem Weg, den Browser zu erobern?
<br/>document.addEventListener('WebAssemblyContentLoaded', () => {<br/>const klass = MonoClass('', 'Hello');<br/>const method = MonoMethod(klass, 'Yell', true);<br/>MonoInvoke(0, method, ['Hallo']);<br/>});<br/> .NET auf dem Weg, den Browser zu erobern?
− Blazor is an experimental Single Page Application (SPA) framework based on .NET − Blazor projects run 100% in the browser − On top of a WASM build of the Mono .NET runtime * − Compiled .NET assemblies are loaded into the browser and JIT compiled * − Uses Razor/.cshtml templates for rendering HTML/CSS − Uses C# for writing application logic .NET auf dem Weg, den Browser zu erobern? * as of December 12, 2018
https://blazor.net/docs/get-started.html dotnet new -i Microsoft.AspNetCore.Blazor.Templates dotnet new blazor -o BlazorApp1 cd BlazorApp1 dotnet run .NET auf dem Weg, den Browser zu erobern? LIVE DEMO
.NET auf dem Weg, den Browser zu erobern? Compiler Parser JIT Web APIs (DOM, IndexedDb, File Storage etc.) Browser blazor.js Blazor page (.html) JS Runtime mono.wasm mono.js mscorlib.dll etc. myapp.dll * as of December 12, 2018
− It is NOT about running any .NET Code just in the browser − We still have a sandbox − Various .NET Standard APIs will just not work in the browser − It is NOT a way to port Razor/MVC/server-side web applications to an SPA − It is NOT a way to bring XAML/WPF/Xamarin into the browser − You may want to look at the Ooui.WASM open source project for this − It is NOT production-ready − Therefore, it is NOT suitable for real-world applications (yet?) .NET auf dem Weg, den Browser zu erobern?
• Package the web application as a native application using Electron or Cordova • Add a manifest to the web application to enhance it as a downloadable and offline-capable PWA .NET auf dem Weg, den Browser zu erobern?
Sun Temple – Unreal Demo http://s3.amazonaws.com/mozilla-games/tmp/2017-02-21- SunTemple/SunTemple.html .NET auf dem Weg, den Browser zu erobern? LIVE DEMO
− The Web is still the Web − You need to know HTML, CSS and JavaScript. Period. − Progressive Web Apps − Emerging technologies enable more “app-like” feeling and behaviors of Web apps − including offline capabilities − WebAssembly − Brings any programming language and sandbox-aware framework to the browser − May pave the way to write business applications without large JavaScript parts – some day… maybe − Blazor − Experimental SPA Framework by the ASP.NET Core team, very early stages – do not use in production! − Shows possibilities of WebAssembly with .NET/possible future UI framework? .NET auf dem Weg, den Browser zu erobern?
phoenixhawk
akiroom
rynsuke
smt7174
oracle4engineer
kei_s
rdlabo
hygradme
h1kita
coconala_engineer
colopl
moritamasami
ouchi2501
reverentgeek
jeffersonlam
zakiyama
matthewcrist
eitanlees
frogandcode
erikaheidi
jnunemaker
jonrohan
addyosmani
cromwellryan
orderedlist