-
Notifications
You must be signed in to change notification settings - Fork 62
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
.Net Core 3.0 support #118
Comments
fixed with #119 |
Thanks! When can we expect a new release to be published with this fix? |
To be determined. But I'd expect it not to take to long. While on the
subject are there any other Pr's you would find essential to merge before
we release?
Op vr 4 okt. 2019 19:28 schreef Brian Romanko <notifications@github.com>:
… Thanks! When can we expect a new release to be published with this fix?
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<#118?email_source=notifications&email_token=AAHQ3F4L2EC23GG5PYR4PZLQM54KHA5CNFSM4IZSQIO2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEAMLC4A#issuecomment-538489200>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAHQ3F7BC7CLMAKOY2NTK23QM54KHANCNFSM4IZSQIOQ>
.
|
This is the only thing that looks to be completely blocking. At the moment you cannot run Akka.NET using remoting/cluster with .Net Core 3. |
To be fair, there are more issues with running akka.net on .Net Core 3. We have gotten multiple reports on different things. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
On .Net Core 3.0 (releases today), Hyperion's constructor throws an exception:
System.TypeInitializationException: 'The type initializer for 'Hyperion.SerializerOptions' threw an exception.'
This was properly reported in issue #111 about 6 months ago. Is this project still being maintained?
The text was updated successfully, but these errors were encountered: