You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We need an implementation for net6.0-windows10.0.18362 similar to what is in MainDispatcherScheduler.UWP.cs
Actual Behavior
The MainDispatcherScheduler.Windows.cs only has similar logic (ScheduleCore) to the iOS, Android and WebAssembly files. At the moment, if we try to replicate the UWP file with the .NET 6 Windows target, we get compile errors like this: error CS0246: The type or namespace name 'CoreDispatcherScheduler' could not be found in .net-5.0 which was supposedly a known issue, since then System.Reactive hasn't been updated at all and plan on any .net-6.0 targets seem to be uncertain.
Steps to Reproduce the Problem
Remove the WINDOWS10_0_18362_0 condition in the top of the MainDispatcherScheduler file.
Copy and paste the content from MainDispatcherScheduler.UWP.cs into the Windows file.
GabrielChouinardLetourneau
changed the title
Implement an CoreDispatcherScheduler equivalence for Windows .NET 6
Implement a CoreDispatcherScheduler equivalence for Windows .NET 6
Oct 11, 2022
Expected Behavior
We need an implementation for
net6.0-windows10.0.18362
similar to what is inMainDispatcherScheduler.UWP.cs
Actual Behavior
The
MainDispatcherScheduler.Windows.cs
only has similar logic (ScheduleCore) to the iOS, Android and WebAssembly files. At the moment, if we try to replicate theUWP
file with the .NET 6 Windows target, we get compile errors like this:error CS0246: The type or namespace name 'CoreDispatcherScheduler' could not be found in .net-5.0
which was supposedly a known issue, since then System.Reactive hasn't been updated at all and plan on any .net-6.0 targets seem to be uncertain.Steps to Reproduce the Problem
WINDOWS10_0_18362_0
condition in the top of theMainDispatcherScheduler
file.MainDispatcherScheduler.UWP.cs
into theWindows
file.Windows
namespace toMicrosoft
.Specifications
The text was updated successfully, but these errors were encountered: