-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Load Akka Config from App.config automatically #671
Comments
I think this makes sense. Also, very soon the internal behavior will probably need some change to work with the new config providers from asp.net vnext, that don't require xml files. In that case, akka can load the settings directly from some hocon file with some |
This is already how it works... |
@rogeralsing here's what var section = new AkkaConfigurationSection();
Config config = section.AkkaConfig;
return config; This returns a blank Needs to be changed to using the |
Ohhh. that is a bug in that case. |
I'm having Bootcamp attendees use this in Unit 2 - would love to have a hotfix for this for them in the near future :p |
Automatic App / Web.config loading #671
This is broken in the latest release of Akka.Net 1.4.1. Please reopen this issue. It is no longer automatically loading the akka section in the app.config file. Reverting back to 1.3.18 works fine. |
Open a new issue.
…Sent from my iPhone
On Mar 12, 2020, at 12:04 PM, ejohn54 ***@***.***> wrote:
This is broken in the latest release of Akka.Net 1.4.1. Please reopen this issue. It is no longer automatically loading the akka section in the app.config file. Reverting back to 1.3.18 works fine.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
I took care of it - #4330 |
I would love to be able to remove the following boilerplate code from Akka.NET apps if possible:
And just have the following call, which would automatically load configuration sections in via ConfigurationManager:
Any objections to this?
The text was updated successfully, but these errors were encountered: