Aaron Robinson

>we might want to reconsider interop support for generic delegates or generic unmanaged function pointers to enable making WinRT code AOT-friendly I don't think this is _needed_ but rather makes...

This is proving to be far more complicated to address with the cleverness @jkoritzinsky and I came up with. We have something but it is going to be better, but...

@kant2002 It is indeed interesting. We are starting down some other paths right now - primarily `ref` field work. Our solution for this unfortunately has been slightly deferred and is...

The current thought will be to leverage `TypedReference` and have developers supply callbacks. However, there are a myriad of issues with the below API. The most obvious being `TypedReference` can't...

This is a blocking issue that, as currently implemented, is not possible with the [`WinRT.Host`](https://github.com/microsoft/CsWinRT/tree/master/src/Authoring/WinRT.Host). The root cause is use of the `hostfxr_initialize_for_runtime_config` API, which doesn't support a self-contained scenario....

> MSIX packaged apps are all self-contained (no other ways to guarantee .NET is on the machine), so this isn't a new concern for a self-contained WinRT component right? That...

> or is further work in CsWinRT required for that support? More work is needed. @jlaanstra was able to create a host that supports self-contained using DNNE but the built-in...

@jkoritzinsky Would CsWinRT expose this new API or the runtime for CsWinRT to query? I would prefer the former rather than the latter. I think providing some pseudo code that...

@jkoritzinsky Perhaps it would be better to have the caller provide a `ComWrappers` instance instead? I would like to limit ways to create external object wrappers and the `ComWrappers` already...

>We could do that as well if we're ok with this API being available only on the .NET 5 target. The non .NET 5 approach is already degraded due to...