You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 8, 2024. It is now read-only.
As mentioned in an update to the README last year and repeating here, we're going to archive this repo effective immediately.
The focus of aligning the XAML dialect across a number of our XAML-based languages was our initial goal. We were unable to find a direct alignment with our product areas as we’d hoped. To that end, we are choosing to archive this repo. Our frameworks such as Windows Presentation Foundation (WPF), WinAppSDK, and .NET MAUI are rich with features powerful for each use case and can leverage XAML declarative markup unique to their own scenarios and underlying platforms they serve. We will continue to evolve those frameworks as appropriate, enabling developers choosing those platforms for their apps to be most successful in their developer scenarios and targets.
As a side note, the issues will remain in their current state as we're not resolving/dispositioning any of them individually as a part of this archive.
The text was updated successfully, but these errors were encountered:
microsoft
locked as resolved and limited conversation to collaborators
Mar 8, 2024
As mentioned in an update to the README last year and repeating here, we're going to archive this repo effective immediately.
The focus of aligning the XAML dialect across a number of our XAML-based languages was our initial goal. We were unable to find a direct alignment with our product areas as we’d hoped. To that end, we are choosing to archive this repo. Our frameworks such as Windows Presentation Foundation (WPF), WinAppSDK, and .NET MAUI are rich with features powerful for each use case and can leverage XAML declarative markup unique to their own scenarios and underlying platforms they serve. We will continue to evolve those frameworks as appropriate, enabling developers choosing those platforms for their apps to be most successful in their developer scenarios and targets.
As a side note, the issues will remain in their current state as we're not resolving/dispositioning any of them individually as a part of this archive.
The text was updated successfully, but these errors were encountered: