Support `UWP` / WinUI 2 via package

[bitsandfoxes]

Benefits

• Allows us to be optinionated whether UWP is targeted
• Wrap the enricher to fix non-available stuff (i.e. in foreground)
• Wrap .NET native functionality that is not available
• UWP events missing debug_meta.images information #3388
• UWP: Investigate CPUSets #569
• Run UWP gatekeeper in CI #2416

Challenges

• UWP is not under active development and appears to have been deprecated in favour of WinUI 3
• Currently we publish all our NuGet packages from the same build on the macOS runner. I don't think we can build packages with dependencies in WinAPI from macOS, so we'd need to use multiple runners to publish the release builds

See Also

• Sentry package for WinUI 3 apps #3712 (comment)
  • Distinction between WinUI 2 and WinUI 3

[bruno-garcia]

Isn't "UWP" just netX-windows ?

Sorry my ignorance, I dunno much about UWP. @lucas-zimerman might know.

[bruno-garcia]

I think I created a dupe:

• Sentry package for WinUI 3 apps #3712

We should merge them

[jamescrosswell]

I think I created a dupe:

Possibly not. See this comment...

I think we could clarify and narrow the scope of this issue to be supporting UWP and WinUI2.

The other issue you referenced could be about supporting WinUI3.