Fix .Net Core30 Compatibility issues #220
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…O call from ASP.NET dotnet/aspnetcore#7644 Fix issue on .Net Core 3.0 regression dotnet/aspnetcore#17973
workgroupengineering
pushed a commit
to workgroupengineering/Dotmim.Sync
that referenced
this pull request
Jun 15, 2020
Fix .Net Core30 Compatibility issues
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Found two issues for compatibility with .Net Core 3.0 (especially in ASP.Net Core 3.0)
.Net Core 3.0and new forbidden rule for synchronous IO call from ASP.NET: [Announcement] AllowSynchronousIO disabled in all servers dotnet/aspnetcore#7644All call to
ISerializerare now asynchronous.Net Core 3.0regression SDK regression in 3.0.101 and 3.1.100 for ASP.NET Core workloads dotnet/aspnetcore#17973Remove references in
Dotmim.Sync.Web.ServertoMicrosoft.AspNetCore