Xamarin developers can maximize code shared across all platforms

[maddymontaquila]

• o Create a consistent cross-platform application lifecycle model M P1
  • [Spec] Cross-Platform LifeCycle maui#30
  • [Spec] VisualElement Handler Lifecycle Events maui#1198
• o Write cross platform application startup code to register of services, vendor controls, libraries, components S P1
• o Xamarin.Forms and Xamarin.Essentials will be combined to become .NET MAUI and reduce API overlap S P0
  • [Spec] Essentials Dependency maui#19
  • [Spec] Remove Application.Properties  maui#22
• o Remove obsoleted code to improve developer clarity and reduce maintenance costs S P1 [Spec] Remove members marked with Obsolete attribute maui#21
• o Combine Essentials codebase with Forms and reduce API overlap
• o Add multiple window support to applications L P0 [Spec] Add IDispatcher to the IAnimatable interface maui#17
• o Gesture recognizer implementations should be consistent across platforms XL P2
• o Accessibility features are easily accessed at a cross-platform level L P1
  • [Spec] Implement Hiding of Children Elements from the Accessible Tree maui#1214
  • [Spec] Implement LabeledBy property for accessibility maui#845
  • [Spec, WIP] Accessibility.LeafFlags maui#487
  • [Spec] Accessibility Talkback and VoiceOver Properties maui#469
• o Support drag & drop in applications from shared code L P1
• [Spec] TabView maui#7
• [Spec] Shapes maui#8
• [Spec] Shadows maui#9
• [Spec] Rounded Corners maui#10
• [Spec] Brushes maui#11
• [Spec] Border maui#12
• [Spec] AppBar maui#13
• [Spec] Animations maui#265
• [Spec] Implement Effects maui#1226
• [Spec] Implement ContentView inside Core maui#1302
• [Spec] Implement Device class functionality to Core maui#1305

[GalaxiaGuy]

I apologise if this is not meant to be open for public discussion. I haven't seen this repo mentioned publicly, but I ended up here after following a discussion on a ticket elsewhere (dotnet/runtime probably).

Xamarin.Forms and Xamarin.Essentials will be combined to become Xamarin 6 and reduce API overlap

Will this still produce a separate Nuget package for Essentials? I can definitely see the benefit of Forms depending on Essentials, and having them in the same repo could make things simpler. But I also work on some non-Forms projects that are unlikely to ever adopt Forms, but do use Essentials.

[Aguilex]

Xamarin Tools comments... There might be some icon, layout changes in the solution explorer resulting from this.