-
Notifications
You must be signed in to change notification settings - Fork 2k
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
[CRAWL Phase] .Net Core Compatibility #2145
Milestone
Comments
Closed
This was referenced Nov 30, 2016
Closed
This was referenced Jan 19, 2017
Closing this one, as it has served its purpose by now. |
ghost
locked as resolved and limited conversation to collaborators
Sep 29, 2021
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
This issue will track the CRAWL phase of Orleans 2.X milestone as tracked by #2143
The idea with this task is to basically make Orleans Core compatible with .Net Core, by having it target .Net Standard and have the minimal impact as possible in the current codebase.
Since .Net Core tooling still unreliable and will (drastically) change before it reach RTM, we are following the guidelines from here and in a new temporary solution we will work at
master
branch.The target is to have Orleans building and running on .Net Full CLR and .Net Core (hence why target .Net Standard) on Windows and have the full test set only for the .Net Full CLR (.Net 4.6.1+) while having basic validation on .Net Core on Windows.
We will focus on Windows as a baseline but that doesn't mean people can't run tests on Linux/OSX once this work is done. That means that the core test set will focus on .Net Full CLR and basic .Net Core on Windows but you can test your Orleans application on .Net Core supported OSes. The test framework should stay as is. That means the major efforts will not be to update the test kit to multiple OSes and full .Net Core coverage but, if you feel comfortable, we still accept (and really encourage and appreciate!) PRs however, it will take lower priority (and of course efforts on review) from the core team and people from the community working on this port.
Here are the macro tasks and its issues that will be tracked for this phase:
netstandard15
) - Solution for .NET Standard using linked files #2177NETSTANDARD_TODO
comments by implementing workaroundsNETSTANDARD
comments by moving platform specific components to platform specific DLLsnet462
)netcoreapp10
)Note: This list will be updated as new sub-tasks (issues and/or PRs) will emerge from this work.
The text was updated successfully, but these errors were encountered: