ASP.NET / NLog.Extended / Upgrade Issues #741

ghost · 2015-06-10T20:32:28Z

I've just upgraded from 3.2.1 to 4.0.0 on my ASP.NET WebForms project.

I am using NLog and NLog.Extended.dll. Both files have been upgraded to 4.0.0.

When I attempt to execute the website I get the following error:

Server Error in '/' Application.
Configuration Error
Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.
Parser Error Message: An error occurred creating the configuration section handler for nlog: Error when setting property 'Layout' on File Target[log]
Source Error:
Line 21:

This is caused by the ${aspnet-....} entries in the following line:

If I remove all of the ${aspnet-....} entries from this line the website works as before.

Prior to the upgrade everything was working fine.

If I revert back to 3.2.1 everything works again.

304NotModified · 2015-06-10T21:32:48Z

Do you have a full error with stack trace?

Please try full clean and rebuild. We are aware that the were some. similar Net cache problems with previous releases (when upgrading)

ghost · 2015-06-10T21:36:39Z

The layout renderer have been moved to the NLog.Web library. This library has not yet been updated to NLog 4.0, but will be tomorrow, where it also will be released on nuget.

ghost · 2015-06-10T23:06:55Z

Yes I did do a full clean rebuild but it made no difference.

I found NLog.Web too and I tried it but it still failed. I could see that it was still the old version and only supported .NET 3.5.1 in the nuget packages directory.

I'll try again tomorrow when it's updated.

Will I need both NLog.Extended and NLog.Web packages in order to support ASP.NET?

On Wed, Jun 10, 2015 at 10:36 PM, Kim Christensen
notifications@github.com wrote:

The layout renderer have been moved to the NLog.Web library. This library has not yet been updated to NLog 4.0, but will be tomorrow, where it also will be released on nuget.

Reply to this email directly or view it on GitHub:
#741 (comment)

304NotModified · 2015-06-11T10:10:16Z

Sorry for the inconvenience.

ghost · 2015-06-11T11:24:52Z

No problems. Happy to help. I can't try the update until later but can you confirm that I will need NLog.dll, NLog.Extended.dll and NLog.Web.dll now to support the aspnet variables?

304NotModified · 2015-06-11T20:40:41Z

You don't need NLog.extended solely for NLog.web.

304NotModified · 2015-06-11T22:10:35Z

The nuget packages had been updated (version 2.0 for the use with NLog 4.0).

So this has been resolved. If you have any problems, feel free to-open this issue, or create a new one.

blfuentes · 2015-06-15T14:18:52Z

I still get this error after updating to NLog 4.0 and Web 2.0
{"Error when setting property 'Layout' on File Target[f]"} when calling the GetCurrentClassLogger().

My layout is pretty simple:

    <target xsi:type="File" name="f" fileName="${basedir}/logs/${shortdate}.log"
        layout="${longdate} ${uppercase:${level}} :: ${aspnet-user-identity} :: ${stacktrace} ${newline} ${message}" />

Already tested if I remove the ${aspnet-user-identity} it works.

My packages.config file:
...

package id="NLog" version="4.0.0" targetFramework="net451" />
package id="NLog.Config" version="4.0.0" targetFramework="net451" />
package id="NLog.Extended" version="4.0.0" targetFramework="net451" />
package id="NLog.ManualFlush" version="2.0.0.0" targetFramework="net451" />
package id="NLog.Schema" version="4.0.0" targetFramework="net451" />
package id="NLog.Web" version="2.0.0.0" targetFramework="net451" />

...

304NotModified · 2015-06-15T16:09:34Z

moved to NLog/NLog.Web#4

Ekus · 2015-11-13T14:54:16Z

After updating from NLog + NLog.Extended 3.1 to NLog + NLog.Web 4.0 I had to add

    <!--needs before targets-->
    <extensions>
    <add assembly="NLog.Web"/>
    </extensions>

before my targets section. Can it be fixed so we don't need it in the future? It was able to use .Extended assembly without this trick before.

304NotModified · 2015-11-13T15:02:20Z

What are the new versions of each component?

Because this is all fixed a long time ago.

Ekus · 2015-11-13T15:17:24Z

I just used VS 2013's NuGet which provides the latest version by default. I typed "nlog web" and I only see one version, 4.0.0 Creaded by NLog, Id: NLog.Web, published 10/22/1015. It also included NLog 4.0.0 as dependency (which seems to explaint it since I saw mention of it being fixed in 4.0.1..?)

Ekus · 2015-11-13T15:19:20Z

Additionally, the reference says "runtime 2.0" for that NLog.Web version... while for NLog (also 4.0.0) it says runtime 4.0

304NotModified · 2015-11-13T15:20:33Z

I recommend to upgrade NLog to the latest version. (4.2.0). Thinks are fixed in 4.0.1 but also 4.1.

NLog.web is compatible with all version of NLog 4.0+

All other NLog extensions should be 4.0+

The <extensions> is not needed anymore.

304NotModified · 2015-11-13T15:21:25Z

Additionally, the reference says "runtime 2.0" for that NLog.Web version... while for NLog (also 4.0.0) it says runtime 4.0

That's correct. There is not special build for NLog.Web for .Net 4 (not needed, no benefit). It's .Net3.5+ (which is runtime 2.0)

Ekus · 2015-11-13T15:28:55Z

I see, it makes sense now but it's confusing. Shouldn't just the NLog.Web nuget be updated then? To require 4.0.1+ NLog as dependency? Or else it will keep resurfacing

Ekus · 2015-11-13T15:31:43Z

The best thing about NLog is how simple to use it is, but I have recently had hard time spreading it among colleagues, with the breaking changes in 4.0 (move from .Extended to .Web) and this bugged autoload version being installed by default on new boxes. In any case thanks for maintaining this great tool!

304NotModified · 2015-11-13T15:38:38Z

Well, NLog 4.0 works well with NLog.Web 4.0, but it's not optimal.

When upgrading, it's good practice to upgrade all components to have the optimal experience. With the command line it's really easy:

Install-Package NLog.Web; Install-Package NLog;

Blame Nuget for the annoying dependency resolution, which is really bad. (it takes always the lowest version)

We can upgrade NLog.Web to 4.2.0, but no code is changed in that component, so we think it's bad practice.

Ekus · 2015-11-13T16:28:11Z

Yes I agree it should not be required and that the blame is on nuget's side (albeit they must have their reasons and they bring more good than harm anyway ;-) ) but the simplest pragmatic solution would be to either update the NLog.Web package (not sure if you can update package definition without changing its version) or to recompile it with new version and create new package to match.

304NotModified · 2015-11-18T23:51:29Z

@Ekus went everything fine with upgrading?

Ekus · 2015-12-13T05:48:40Z

Oh, yes, once I installed the newest NLog first, instead of relying on NLog.Web adding NLog 4.0 as a dependency. Thank you.

304NotModified assigned ghost Jun 11, 2015

304NotModified mentioned this issue Jun 11, 2015

No RichTextBoxTarget found in NLog 4.0 #748

Closed

304NotModified added this to the 4.0 milestone Jun 11, 2015

304NotModified closed this as completed Jun 11, 2015

304NotModified reopened this Jun 15, 2015

304NotModified closed this as completed Jun 15, 2015

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

ASP.NET / NLog.Extended / Upgrade Issues #741

ASP.NET / NLog.Extended / Upgrade Issues #741

ghost commented Jun 10, 2015

304NotModified commented Jun 10, 2015

ghost commented Jun 10, 2015

ghost commented Jun 10, 2015

The layout renderer have been moved to the NLog.Web library. This library has not yet been updated to NLog 4.0, but will be tomorrow, where it also will be released on nuget.

304NotModified commented Jun 11, 2015

ghost commented Jun 11, 2015

304NotModified commented Jun 11, 2015

304NotModified commented Jun 11, 2015

blfuentes commented Jun 15, 2015

304NotModified commented Jun 15, 2015

Ekus commented Nov 13, 2015

304NotModified commented Nov 13, 2015

Ekus commented Nov 13, 2015

Ekus commented Nov 13, 2015

304NotModified commented Nov 13, 2015

304NotModified commented Nov 13, 2015

Ekus commented Nov 13, 2015

Ekus commented Nov 13, 2015

304NotModified commented Nov 13, 2015

Ekus commented Nov 13, 2015

304NotModified commented Nov 18, 2015

Ekus commented Dec 13, 2015

ASP.NET / NLog.Extended / Upgrade Issues #741

ASP.NET / NLog.Extended / Upgrade Issues #741

Comments

ghost commented Jun 10, 2015

304NotModified commented Jun 10, 2015

ghost commented Jun 10, 2015

ghost commented Jun 10, 2015

The layout renderer have been moved to the NLog.Web library. This library has not yet been updated to NLog 4.0, but will be tomorrow, where it also will be released on nuget.

304NotModified commented Jun 11, 2015

ghost commented Jun 11, 2015

304NotModified commented Jun 11, 2015

304NotModified commented Jun 11, 2015

blfuentes commented Jun 15, 2015

304NotModified commented Jun 15, 2015

Ekus commented Nov 13, 2015

304NotModified commented Nov 13, 2015

Ekus commented Nov 13, 2015

Ekus commented Nov 13, 2015

304NotModified commented Nov 13, 2015

304NotModified commented Nov 13, 2015

Ekus commented Nov 13, 2015

Ekus commented Nov 13, 2015

304NotModified commented Nov 13, 2015

Ekus commented Nov 13, 2015

304NotModified commented Nov 18, 2015

Ekus commented Dec 13, 2015