Morten Nielsen

I do wonder if you're hitting this issue that's been an issue on Windows for YEARS https://github.com/microsoft/WindowsAppSDK/issues/4068

most likely hardware related. We're using the same version since I'm using your project to repro. I'm closing this out since this doesn't seem to be caused by WinUIEx itself...

Could also be this: https://github.com/microsoft/microsoft-ui-xaml/issues/8423 It was fixed in the latest 1.5exp2. Perhaps you could confirm with that version whether you still see it?

@softworkz Nice find. Not sure what I was thinking there :-)

D'oh! Thanks for the catch. Much appreciated

Personally I have a couple concerns about this one - mostly around it not considering catalyst _yet_. 1. The first one is, that without catalyst support up-front, I think it's...

Workaround for anyone else hitting this: ```cs #if NETFX_CORE global using DataRowAttribute = MyNamespace.DataRowAttribute; // Requires C# LangVersion=10+ namespace MyNamespace { public class DataRowAttribute : Microsoft.VisualStudio.TestTools.UnitTesting.DataRowAttribute { public DataRowAttribute(params object[]...

I agree it's super annoying, however how do you debug a testrun where some tests are actually timing out? Ie you do a test run with the debugger attached, a...

I don't think just having the debugger attached should disable timeouts. If you do a full test run with the debugger attached, you could have a test hang indefinitely. IMHO...

This is especially a big problems with using 3rd party libs that aren't annotated like WPF. For instance this intellelisense makes it clear how misleading it is. For example the...