Alexander Sklar

I see, I recommend seeking support on the [react-native-screens repo](https://github.com/software-mansion/react-native-screens ), as it's possible that that module doesn't work well on Windows. CC @chiaramooney in case she's seen this issue...

@chrisglein I believe the existing instrumentation is in VS for file->new project which wouldn't capture usage through since we don't use the winappsdk templates.

Related to #9901 @acoates-ms is this something you are planning to take on soon?

See #10063 for a sketch of what a solution might look like; not needed for 0.70 but good thing to target to iron out the wrinkles between native and RN...

will need to try this out in winappsdk 1.0 once we update @AgneLukoseviciute fyi

> If this change lands, what's the rollout plan? In Messenger for example, we rely on the implementation detail that the React tag is set to the FrameworkElement::Tag property in...

> @asklar RNX will need to update its getting and setting (with either a compile time version macro or a runtime API check) but I don't think it's that big...

> > > @asklar > > > > > > Alexander Sklar > > > FTE RNX will need to update its getting and setting (with either a compile time...

fyi @vmoroz

this may be done with the PackageReference work, right? if so can you close @jonthysell ?