New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
An asynchronous operation cannot be started at this time #661
Comments
Issue is prioritized as it contains one of the following labels sponsor, installation, contribution, nuget, breakingchange, ReproSample, Deployment, Backer, ShowStopper |
The DevExpress.XAF repository includes commits that relate to this task: Please update the related Nuget packages and test if issues is addressed. These are nightly nuget packages available only from our NugetServer. If you do not use the Xpand.XAF.Modules directly but through a module of the main eXpandFramework project, please wait for the bot to notify you again when integration is finished or update the related packages manually. Thanks a lot for your contribution. |
Closing issue for age. Feel free to reopen it at any time. .Thank you for your contribution. |
Describe the bug
The exception is raised for asp.net if you try to observe .net events and you go with the default scheduler as it will schedule notification on the AspNetSynchronizationContext which may not be available at time.
To Reproduce
Expected behavior
Immediate scheduling of all events exposed from reactive modules is required and observables will behave like a normal dotnet event
The text was updated successfully, but these errors were encountered: