Azure Tech Frogs La vida despues de Xamarin NET MAUI y el desarrollo de apps.pptx

Notas del editor

• #7: .NET 6, the next generation of the company’s software development platform that will finish the parts of the .NET unification begun in .NET 5.  Due as a production release in November, .NET 6 is set to deliver improvements for cloud, desktop, and mobile apps.  Microsoft .NET 6 will integrate capabilities for Android, iOS, and MacOS that currently reside in the Xamarin open source mobile .NET platform. Microsoft also is extending the Blazor client web app development tool, so developers can build a hybrid client app that combines web and native UIs for desktop and mobile usage. Blazor WebAssembly was the first unified platform deliverable in .NET 5 The .NET unification creates one .NET from the separate .NET Core, .NET Framework, and Xamarin/Mono technologies. Parts of .NET Framework already had moved to .NET Core; .NET 5 began the journey of combining .NET Core and Mono/Xamarin on a base class library and toolchain.
• #12: .NET Multi-platform App UI (MAUI) is a cross-platform framework for creating native mobile and desktop apps with C# and XAML. Using .NET MAUI, you can develop apps that can run on Android, iOS, macOS, and Windows from a single shared code-base. .NET MAUI is open-source and is the evolution of Xamarin.Forms, extended from mobile to desktop scenarios, with UI controls rebuilt from the ground up for performance and extensibility. If you've previously used Xamarin.Forms to build cross-platform user interfaces, you'll notice many similarities with .NET MAUI. However, there are also some differences. Using .NET MAUI, you can create multi-platform apps using a single project, but you can add platform-specific source code and resources if necessary. One of the key aims of .NET MAUI is to enable you to implement as much of your app logic and UI layout as possible in a single code-base.
• #13: Las API de Android, iOS, macOS y Windows están unificadas en una API abstracta que permite una experiencia de desarrollo que permita escribir una vez y ejecutar en cualquier plataforma, al tiempo que proporciona un acceso total a todos los aspectos de cada plataforma nativa. App Code interactúa principalmente con .NET MAUI API (1). Según sea necesario, App Code puede acceder directamente las API de la plataforma (2) a través Handlers, etc. .NET MAUI accede directamente las API de la plataforma nativa (3). How is it native? Everything starts with your app code. This is where you want to spend all your time being productive. And you want to deliver your app on 1+ devices The first layer of the technology cake is the native platform SDK. This what Google, Android, and Microsoft ship for those platforms So how do we get from our .NET app code to those platforms and running on devices? First we need something that can run .NET code: the .NET Runtime. (Yes, it uses MonoVM on mobile and Mac, and CoreCLR on Windows, but that’s not terribly important because...) Next we need a common .NET API we can write our code against, and that’s the Base Class Library (BCL). New in .NET 6 app runtimes use the same BCL. To use .NET against native platform SDKs we need a .NET representation of them. We do this via binding a .NET API and implementation to the native API. When you call a native method from C#, it’s just as if you had done it from Obj-C, Swift, Java, Kotlin, or C++. The final layer of the cake that really makes it delicious is .NET MAUI. .NET MAUI provides a rich library of controls, layouts, and services that work across all of the platforms supported, so you need only master one API to get native apps. (next slide) With .NET MAUI, all of that complexity is delivered in a single framework that gives you access to it all.
• #14: With .NET MAUI, all of that complexity is delivered in a single framework that gives you access to it all.
• #16: You have more than 40 controls, layouts, and pages to mix and match from. These are all of the controls you have out of the box, you can of course create your own. What is unique is you get the native control and have access to it.
• #17: And, our partners building controls make much of this possible, creating gorgeous pre-built UI controls for you to drop right in to your app
• #19: .NET Multi-platform App UI (MAUI) provides a collection of controls that can be used to display data, initiate actions, indicate activity, display collections, pick data, and more. By default, handlers map these cross-platform controls to native controls on each platform. For example, on iOS a .NET MAUI handler will map a .NET MAUI Button to an iOS UIButton. On Android, the Button will be mapped to a AppCompatButton: Handlers can be accessed through a control-specific interface provided by .NET MAUI, such as IButton for a Button. This avoids the cross-platform control having to reference its handler, and the handler having to reference the cross-platform control. The mapping of the cross-platform control API to the platform API is provided by a mapper. Handlers expose the native control that implements the .NET MAUI cross-platform control via the NativeView property. This property can be accessed to set platform properties, invoke platform methods, and subscribe to platform events. Handlers are global and therefore customization can occur anywhere in your .NET MAUI app. For example, customizing a handler for a control in your App class will result in all controls of that type being customized in the app. Similarly, customizing a handler for a control in the first page of your app will also result in all controls of that type in the app being customized.
• #21: The new handler architecture makes it easy to hook into any property and add/modify behavior right in .NET MAUI In this example we hook into the background color and change the Android underline visibility on the Entry. We could also, with a little more effort, add a custom property mapping specific to the underline and implement that with almost identical code.
• #23: One project can now publish to any of the platforms supported. Images are optimized at build time for the multiple densities of screens required across all the platforms you target. Fonts are registered in one location for every platform, and you can alias the name as you desire. Platform code can all live within this one, multi-targeted project. Splash screen support makes it easy to declare a visual asset (PNG or SVG for example) and a background color.
• #25: The App class should derive from the Application class, and must override the CreateWindow method to provide a Window within which your app runs, and that defines the UI for the initial page of the app: In the example above, MainPage is a ContentPage that defines the UI for the initial page of the app. To register your own handlers, call the ConfigureMauiHandlers method on the IAppHostBuilder object. Then, on the IMauiHandlersCollection object, call the AddHandler method to add the required handler: In this example, the MyEntryHandler handler is registered against the MyEntry control. Therefore, any instances of the MyEntry control will be handled by the MyEntryHandler. 
• #26: Code live whether it’s C#, CSS, Razor, or XAML. Less time building and more time coding. In a future Visual Studio 2022 release you’ll also be able to see your app right inside the IDE where you can inspect elements and set UI guides. (this is showing Xamarin.Forms and will be replaced with a .NET MAUI example. Same technology)
• #27: Aka “Hot Restart” enables you to use your Apple developer account, a Windows dev machine, and any iOS device to build and test iOS apps.
• #28: Code live whether it’s C#, CSS, Razor, or XAML. Less time building and more time coding. In a future Visual Studio 2022 release you’ll also be able to see your app right inside the IDE where you can inspect elements and set UI guides. (this is showing Xamarin.Forms and will be replaced with a .NET MAUI example. Same technology)
• #32: Github.com/dotnet/maui/wiki/roadmap