Chris Glein

If this would only cover VS project creation and not CLI project creation, yes we need our own events for this.

Depends on #9165

How .NET CLI telemetry handles their data: https://learn.microsoft.com/en-us/dotnet/core/tools/telemetry

Based on what I'm reading here I think you're looking for bubbled/routed/tunneling event hooks (the ability to catch events in parent controls before and/or after the direct control gets those...

Need to replicate this just in XAML to see how Narrator/etc. announces this. Then look at Accessibility Insights to see if there's something in the structure causing the double announce....

First thing to do here will be to replicate on other platforms and compare behavior.

Potentially related: https://github.com/facebook/react-native/pull/34287

Previously when adopting 142 we had to support a switch while we were getting customers like Office migrated. Likely we'd need something like this so we can take on 143...

Notes from planning poker: > Have tried upgrading the solution to VS2022. Using that with 142 seems to be fine, so 143 is probably fine? How does this affect key...

@jbcullis was Saad's suggestion above about looking that "live rewrite" example helpful? You're on 0.64 for macOS I take it - is upgrading to 0.66 an option?