Jesse Collins

Hi, does this issue repro in WinAppSDK? Thanks!

Thank you HO-COOH, this seems like a different issue, no? Xaml's Window is not a FrameworkElement, and doesn't have a FindName() function. See for example: [7305](https://github.com/microsoft/microsoft-ui-xaml/issues/7305). Do you still see...

I've marked this as a feature proposal because we'll likely solve this by adding a new API. (it would likely cause compat issues if we changed the timing of the...

Hi! Just to set expectations, we don't have any specific plans to address this soon, I'm mostly trying to categorize our issues. In WinAppSDK releases (especially minor ones) we try...

Hi sigmarsson, do you have a minimal repro of this? Sorry if I missed it somewhere in the thread. Thanks!

Thanks! I built and debugged this project locally: https://github.com/Sergio0694/SwapChainWinUI3Repro From what I can tell, the CLR is keeping the process alive because there's a managed thread that's still running --...

Agreed, if the process app process has exited, it doesn't sound like anything due to the CLR (or WinAppSDK / WinUI). I'm sorry, I don't have much experience with RuntimeBrokers,...

Hi @sigmarsson -- your scenario doesn't seem to involve RuntimeBroker (like @Sergio0694 is seeing), is that correct? Can you explain what the "x" process is in your screenshot? Also, can...

Hi, thanks for filing. The problem here might be that the WinAppSDK framework package isn't installed. When you press F5 in VS this will happen automatically. But if you just...

Hi @AceSyntax , it sounds like your issue might be different. Would you mind opening a new issue with information about what version you're using and the full error message?...