khoabui1412
khoabui1412
I still meet the error: `UITestMethodAttribute.DispatcherQueue should not be null. ` in unpackaged mode. My project config: ``` WinExe net6.0-windows10.0.19041.0 10.0.17763.0 UnitTest app.manifest x86;x64;arm64 win10-x86;win10-x64;win10-arm64 win10-$(Platform).pubxml true true True None...
@Evangelink, it's still broken, it's ok if I set app as packaged app, but my case I want to run in unpackaged mode.
@Evangelink , it also has same error when calling by vstest.console.exe. Here're sample project: [UnpackagedWinUI3.zip](https://github.com/microsoft/testfx/files/11588456/UnpackagedWinUI3.zip)
@Evangelink, Iam not sure how to set that, I try to set that in obj folder in UnitTest.AssemblyInfo.cs file and It still meets the error about MSTest as before.
In my case, App crashed when ran debug in some OS, but release is fine.
> > In my case, App crashed when ran debug in some OS, but release is fine. > > Did you build your app's project in VS with its default...
Not sure which version is latest code/package, but I test on latest CommunityToolKit which is 7.1.2
> Possible duplicate of #3303 @fabiant3 FYI Calling **Bindings.StopTracking** doesn't help, it just helps release viewmodel but the view is not.
Hi, thing get worse, when I update to WASDK ver 1.2, even not using x:Bind, view did not release.
I tested with binding and it’s very slow compared to x:Bind