[StaFact] tests do not execute when targeting net462 about xunit.stafact HOT 8 CLOSED

What OS and .NET runtime are you running your test on?

from xunit.stafact.

from xunit.stafact.

It should work in that environment. Can you share a minimal repro zip file?

from xunit.stafact.

Here is a small project that shows the problem.
StaFactTestProject.zip

from xunit.stafact.

Wow. That seems ... totally broken. I'll see what I can do to fix it.

from xunit.stafact.

Ok, the reason is your test project targets something less than net472. xunit.stafact now targets net472 so although VS test discovery will find your test, xunit cannot run it since xunit.stafact.dll targets a newer framework than your test. Bump your test to net472 to resolve.

from xunit.stafact.

Thanks! It's working with 4.7.2. Is it correct that, if running your sample then this
Assert.Equal(originalThread, Environment.CurrentManagedThreadId);
will fail for StaFact but not for [UIFact], [WinFormsFact] or [WpfFact]?
Should you not get the same ThreadId also for StaFact?

from xunit.stafact.

If you're talking about that Assert appearing after an await, yes it would be expected to fail.

Awaits rely on a SynchronizationContext.Current or TaskScheduler.Current to get you back to the original "context" to execute the rest of an async method on. They can't just magically get you on a given thread. STA threads are no different: the only thing that can get an await to resume on that same thread is if a SynchronizationContext is applied. But STAFact is just a plain vanilla STA thread. If your purpose is to get UI-thread like semantics where a SynchronizationContext is applied to the thread so await brings you back to the original thread, then you should use those other attributes you named.

from xunit.stafact.