-
Notifications
You must be signed in to change notification settings - Fork 165
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
The Name 'NLogBuilder' does not exist in the current context #221
Comments
is this #208? |
I guess so, but It is not clear on how to resolve this issue. Is the documentation up to date? |
The Example located at : https://github.com/NLog/NLog.Web/blob/master/examples/ASP.NET%20Core%202/Visual%20Studio%202017/ASP.NET%20Core%202%20-%20VS2017/Program.cs does not match the documentation. Can this be updated to a working example? |
Could you highlight the differences for me please? I'm currently working on .NET 4.6.1 to get it working on ASP.NET Core 2 |
There is no using statement in the file. So it could not possibly work
…On Nov 30, 2017 4:16 PM, "Julian Verdurmen" ***@***.***> wrote:
does not match the documentation. Can this be updated to a working example?
Could you highlight the differences for me please? I'm currently working
on .NET 4.6.1 to get it working on ASP.NET Core 2
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#221 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AOKnC6yCJr4DfT6jf7KkevCBGn_8Z8igks5s7xsXgaJpZM4Qw5qn>
.
|
I will check. The last time the sample builds and runs at my local machine. Maybe it's a different platform (netstandard 2.0 vs .net 4.6.1+) |
Fixed in Fixed in Nlog.Web.AspNetCore 4.5 rc1 |
In my 'asp.net core 2' project I am unable to configure Nlog as specified in the document located here:
https://github.com/NLog/NLog.Web/wiki/Getting-started-with-ASP.NET-Core-2
Visual studio is providing an error message of:
'The Name 'NLogBuilder' does not exist in the current context'
The text was updated successfully, but these errors were encountered: