A Gentle Introduction to Blazor
- 1. A Gentle Introduction to Blazor IF YOU DEVELOP IN .NET YOU NEED TO KNOW ABOUT BLAZOR
- 3. Agenda 1. What is Blazor? Is JavaScript dead? Another Silverlight? 2. Blazor Server vs Blazor WebAssembly 3. Performance 4. Reusable Components and Javascript Interop 5. Future of Blazor 6. Community and other resources
- 4. 1.What is Blazor? .NE T Angular Go Nod e PHP TypeScrip t Reac t Vue Javascript Runtime Java
- 6. 1.What is Blazor? Single page application Framework for building interactive Web UI apps using c# 1. .NET Ecosystem 2. Full Stack Developer 3. Performance almost native 4. Visual Studio, VS Code 5. Dlls, Nugets 6. Same Sandbox that Javascript 7. If you used ASP.NET Web Forms or MVC you will love Blazor
- 8. 1.Another Silverlight? 1. WebAssembly : 4th web standard language together with HTML, CSS and JS 2. No Plugins 3. Same sandbox as JS. 4. It just works
- 9. 2. Blazor Server vs Blazor WebAssembly
- 10. 2. Blazor WebAssembly 1. Runs directly in WA on the client 2. Download everything to the browser, HTML, CSS, JS, .NET dlls and the .NET Runtime 3. No server needed Azure Storage Static Website
- 11. 2. Blazor WebAssembly 1. Runs on the client 2. Performance almost native 3. Offline support 4. No server needed 5. All modern browsers support it 1. Runs on the client 2. Limited to the browser capabilities 3. Bigger file download and loading time 4. No secrets can be stored in the application 5. Old browsers version do not support WA 😀😀😀 🤔🤔🤔
- 12. 2. Blazor Server 1. ASP.Net Core Server with the Blazor App,it contains the .NET Core runtime and the communication with the UI happens using Signal R. 2. Events to the server and UI updates sent back to the browser What is Signal R?
- 13. 2. Blazor Server
- 14. 2. Blazor Server
- 15. 2. Blazor Sever 1. Runs on the server 2. Load faster 3. No WebAssembly needed 4. FULL .NET Framework at your disposal 5. You can keep secrets, connection strings, etc 1. Needs a server 2. No offline support 3. Bigger Latencies than WA, but is not slow by any means 😀😀😀 🤔🤔🤔
- 16. 2. When to use Blazor Server or Blazor WebAssembly? 1. Perfomance (Games, etc) 2. Offline support 3. Server is not running on .NET 4. Need server resources (DB, Secrets, ML) 5. Need to support all browsers versions 6. Interactive WEB Apps
- 17. 3. Performance
- 18. 4. Reusable Components 1. Blazor is based on Reusable Components (Web Forms Replacement 🤔) 2. Composition of Components. Parent and childs. 3. Razor Libraries 4. Templates
- 20. 4. Blazor Server
- 22. 4. Blazor Components Componentes en WebAssembly vs Server. Diferencias es solo en acceso y permisos.
- 23. 4. Javascript Interop A Blazor app can invoke JavaScript functions from .NET methods and .NET methods from JavaScript functions.
- 24. 5. Future of Blazor 1. Server 2. Client 3. PWA. Offline support. Home screen and taskbar. Push Notifications 4. .Net renders to Electron/WebView. 5. Mobile
- 25. PWA - Blazor WebAssembly App 1. Offline capabilities. 2. Home screen and taskbar. 3. Push Notifications
- 27. 5. Why I have been waiting for Blazor? 1. C# (.NET) 2. Productivity – New Developers 3. Reduce cost y maximize reach 4. Brilliant Future
- 29. .NET 6 for Blazor • Hot reload for Blazor • AOT Compilation • Target and deploy to desktop platforms. • Support custom event args in Blazor • Required parameters to blazor components • Expose location changing event for NavigationManger • Dynamically rendered components • Update Blazor head components • Improve SVG support in Blazor • Drag & Drop 😀😀😀
- 30. 6. Community