-
Notifications
You must be signed in to change notification settings - Fork 151
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
Why named the extensions class "AspNetExtensions"? #76
Comments
Because those extensions are only for ASPNET (core) We will move them to NLog.web in the future |
So there will be extension class for console or other backend applications? |
The first steps will be splitting the For Console their aren't plans, and if we include them, they should be in another package, depending of the dependencies. |
I have a similar question. Why this logging library has a dependency on Microsoft.AspNetCore.Hosting (though Microsoft.Extensions.Logging has not this dependence)? I want to use NLog (via Microsoft.Extensions.Logging) in the console application and I do not need any dependencies associated with web applications. |
Same answer. This will be also moved to NLog.web in the future. Had no time to fix it yet. Could use some help, although NLog.web needs also an update first. |
@304NotModified Thanks for the quick reply! |
We have to do the following to remove the dependency to ASP.NET for this package
I could use some help on 1. |
closing this is favor of #25 |
this has been released! https://www.nuget.org/packages/NLog.Extensions.Logging/1.0.0-rtm-beta1 ASP.NET Core users should also install NLog.Web.AspNetCore: https://www.nuget.org/packages/NLog.web.aspnetcore |
I don't think it's a good idea to name the extensions class as "AspNetExtensions". Because NLog also can be use in other back end applications than website.
Probably the name "NLogExtensions" would be better?
The text was updated successfully, but these errors were encountered: