Clean Architecture in .NET MAUI and ASP.NET Core with Matt Goldman

November .NET User Group: Clean Architecture in .NET MAUI and ASP.NET Core

0:00 | Introduction
1:00 | Agenda
1:25 | Matt Goldman
2:30 | SSW Rewards
3:20 | What is Full Stack
6:13 | What is code sharing?
6:57 | Demo
11:10 | What is Clean Architecture
15:33 | Demo
45:19 | Taps to watch out for
46:48 | Trap #1
52:34 | Trap #2
55:25 | Bonus tip
58:35 | Python - Lessons to learn
59:36 | Code Sharing ++
1:02:20 | Shameless self-promotion
1:03:07 | Other resources
1:04:05 | SSW Rewards App
1:05:19: Got Feedback?
1:06:02 | Q&As

We've heard a lot about how using .NET to build our UI applications lets us share code across our whole stack, but finding the best way to do this isn't straightforward. UI code and API code can sometimes seem at cross-purposes and it's not always obvious how using .NET code across your whole stack provides any advantages over using different technologies for your UI and API. It's easy to fall into the trap of underutilizing the right code-sharing techniques. Or, at the other extreme, butchering your architecture for the sake of sharing code.

In this talk, Matt Goldman (author of .NET MAUI in Action) will look at extending Clean Architecture to incorporate UIs built with .NET MAUI and Blazor. See sensible ways to write clean, testable, re-usable code that can be shared across the different layers of your solution, and across different solutions in your enterprise, to optimize efficiency and minimize duplication, without compromising the core principles of Clean Architecture. We'll also see how to avoid the common pitfalls of over-engineering or under-sharing.

You will walk away knowing how to make full-stack code shared with .NET a reality.

|| Subscribe for more content from SSW TV ||

|| Press like and leave a comment below to let us know how we're doing ||

LinkedIn ↴

Instagram ↴

Twitter ↴

Facebook ↴

----------------------------------------------------------------------------

SSW Solution Architect

Since joining SSW, Matt has worked on a number of projects for a range of clients, including government agencies and multinational organisations. Matt loves making things, and at SSW uses that passion to fuel his work with .NET, EF / EF Core, Xamarin and .NET MAUI, Azure and Blazor. Matt also works with security and authentication/authorisation.

Additionally, Matt (author of .NET MAUI in Action) regularly presents at the .NET User Group in 3 states, has hosted SSW's Xamarin Hack Day, has presented at the .NET Superpowers Tour, and regular co-hosts SSW's Clean Architecture Superpowers and Clean Architecture Workshop. Matt has also presented at NDC Sydney.

Matt loves DevOps, DevOps, and DevOps. He loves deploying code with GitHub Actions, Azure DevOps Build Pipelines, Octopus and definitely not with a right click. Matt likes clean architecture, using the right tool for the job, seeing developers push changes to production with confidence, automated tests, building solutions on Azure, and now he never has to reminisce about Web Forms.

----------------------------------------------------------------------------

Created by SSW TV | Videos for developers, by developers

v1 - Jonty

[gagikkyurkchyan]

I couldn't agree more with your last comments regarding the past, the present, and the future of MAUI/Xamarin. I started doing Xamarin about 8-9 years ago. I did have a .NET background, but I hopped onto it as a mature iOS developer. To say it was an arduous journey, it's to say nothing. When Xamarin.Forms came out, making our lives easier, but the cost was a tremendous decrease in app performance and crippled UI/UX. To make Xamarin.Forms work you actually had to build an app that was either MVP, or a had a very simple UI/UX. Otherwise, you would make many compromises or have to give into the Dark world of custom renderers. To do that, you had to be an exceptionally versed iOS/Android developer, and I had to learn. Yeah, It's cool, I know iOS/Android, but it's a nightmare for someone new.

The reason Flutter and React.Native became prominent, is the fact they are kind of a framework (especially Flutter), that is well sufficient to build a beautiful app with almost 0 knowledge of underlying platforms as they implement their own rendering.

With .NET MAUI, it seems they are solving all of the problems Xamarin.Native & Xamarin.Forms suffered. And I totally agree on the remark that Microsoft should really showcase the power of Maui by using it for their apps. They have several big desktop/cross-platform apps (Teams, VS Code for instance) that use Electron. That's kind of shooting your feet when you think about marketing. Considering those other technologies have a lot of high-profile show-case apps, we can say for sure that Microsoft needs to do at least that to have the slightest chance of reaching more people.

I am a very avid .NET developer myself, and the same way as you Matt, I don't use other technologies simply because they are not .NET. But I envy their developers a lot :). We are already seeing dreams coming true with .NET Maui. And I do hope, some day, .NET MAUI will be at least as popular as other technologies are.

[levijacksonssw]

Great video Matt! Love the Monty Python fact! 😆

[fieryscorpion]

That was a great talk. Thank you!
I feel Clean Arch makes the whole project unnecessarily complex. I really hope you guys give more love to Vertical Slice Architecture. VSA makes the development experience so much easier and cleaner!