Artwork

Sisällön tarjoaa David Gardiner and Adelaide .NET User Group / David Gardiner. David Gardiner and Adelaide .NET User Group / David Gardiner tai sen podcast-alustan kumppani lataa ja toimittaa kaiken podcast-sisällön, mukaan lukien jaksot, grafiikat ja podcast-kuvaukset. Jos uskot jonkun käyttävän tekijänoikeudella suojattua teostasi ilman lupaasi, voit seurata tässä https://fi.player.fm/legal kuvattua prosessia.
Player FM - Podcast-sovellus
Siirry offline-tilaan Player FM avulla!

Writing XAML like it's 2023, with Matt Lacey

1:20:51
 
Jaa
 

Manage episode 360786182 series 1329529
Sisällön tarjoaa David Gardiner and Adelaide .NET User Group / David Gardiner. David Gardiner and Adelaide .NET User Group / David Gardiner tai sen podcast-alustan kumppani lataa ja toimittaa kaiken podcast-sisällön, mukaan lukien jaksot, grafiikat ja podcast-kuvaukset. Jos uskot jonkun käyttävän tekijänoikeudella suojattua teostasi ilman lupaasi, voit seurata tässä https://fi.player.fm/legal kuvattua prosessia.

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

65 jaksoa

Artwork
iconJaa
 
Manage episode 360786182 series 1329529
Sisällön tarjoaa David Gardiner and Adelaide .NET User Group / David Gardiner. David Gardiner and Adelaide .NET User Group / David Gardiner tai sen podcast-alustan kumppani lataa ja toimittaa kaiken podcast-sisällön, mukaan lukien jaksot, grafiikat ja podcast-kuvaukset. Jos uskot jonkun käyttävän tekijänoikeudella suojattua teostasi ilman lupaasi, voit seurata tässä https://fi.player.fm/legal kuvattua prosessia.

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

65 jaksoa

Kaikki jaksot

×
 
Loading …

Tervetuloa Player FM:n!

Player FM skannaa verkkoa löytääkseen korkealaatuisia podcasteja, joista voit nauttia juuri nyt. Se on paras podcast-sovellus ja toimii Androidilla, iPhonela, ja verkossa. Rekisteröidy sykronoidaksesi tilaukset laitteiden välillä.

 

Pikakäyttöopas