Search a title or topic

Over 20 million podcasts, powered by 

Player FM logo
Artwork

Content provided by David Gardiner and Adelaide .NET User Group / David Gardiner. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by David Gardiner and Adelaide .NET User Group / David Gardiner or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://podcastplayer.com/legal.
Player FM - Podcast App
Go offline with the Player FM app!

Writing XAML like it's 2023, with Matt Lacey

1:20:51
 
Share
 

Manage episode 360786182 series 1329529
Content provided by David Gardiner and Adelaide .NET User Group / David Gardiner. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by David Gardiner and Adelaide .NET User Group / David Gardiner or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://podcastplayer.com/legal.

Whether it be MAUI, WPF, WinUI, Xamarin.Forms, UWP, Uno Platform, Avalonia, or any other technology that defines UIs with XAML, there are some common complaints about working with XAML files that have been around as long as XAML has.

It can be hard to write, understand, maintain and modify. But, it doesn't have to be this way.

The solution isn't abandoning XAML entirely, adopting a new framework, or using a different pattern. The solution is treating XAML like a "real programming language."

By comparing it with how we write and work with C# and other files we compile into our applications, let me show you what we've been doing wrong, how we can do things differently, how it makes things better, and give you strategies for improving existing codebases.

Or, you can tell me why I'm wrong, and that it's still appropriate that the XAML files created today look like the ones created 15+ years ago..

Links:

  continue reading

68 episodes

Artwork
iconShare
 
Manage episode 360786182 series 1329529
Content provided by David Gardiner and Adelaide .NET User Group / David Gardiner. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by David Gardiner and Adelaide .NET User Group / David Gardiner or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://podcastplayer.com/legal.

Whether it be MAUI, WPF, WinUI, Xamarin.Forms, UWP, Uno Platform, Avalonia, or any other technology that defines UIs with XAML, there are some common complaints about working with XAML files that have been around as long as XAML has.

It can be hard to write, understand, maintain and modify. But, it doesn't have to be this way.

The solution isn't abandoning XAML entirely, adopting a new framework, or using a different pattern. The solution is treating XAML like a "real programming language."

By comparing it with how we write and work with C# and other files we compile into our applications, let me show you what we've been doing wrong, how we can do things differently, how it makes things better, and give you strategies for improving existing codebases.

Or, you can tell me why I'm wrong, and that it's still appropriate that the XAML files created today look like the ones created 15+ years ago..

Links:

  continue reading

68 episodes

Tất cả các tập

×
 
Loading …

Welcome to Player FM!

Player FM is scanning the web for high-quality podcasts for you to enjoy right now. It's the best podcast app and works on Android, iPhone, and the web. Signup to sync subscriptions across devices.

 

Listen to this show while you explore
Play