Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Notifications
Mark all as read
Q&A

How to migrate NLog configuration from XML file(s) to application settings (JSON)?

+0
−0

I have just created an ASP.NET Core 6 application and added NLog support for logging:

NLogBuilder.ConfigureNLog("nlog.config").GetCurrentClassLogger()

However, this API is almost deprecated as the remarks says:

It is now recommended to use NLog.LogManager.Setup().LoadConfigurationFromAppSettings()

I began switching to using appsettings.json as it seems idiomatic when working in ASP.NET Core (one expects for virtually all app configurations to be defined here).

The first step was to automatically migrate from XML to JSON using this resource.

However, the JSON file is not exactly what NLog configuration parser expects.

I am wondering if there is any guide or tool to help with such a migration?

Why does this post require moderator attention?
You might want to add some details to your flag.
Why should this post be closed?

0 comment threads

1 answer

+0
−0

FreeFormatter resource mentioned in the question is useful and I could use the output as a base for getting to a working configuration. All the changes were manually performed.

- enable throw configuration exceptions and allow for internal log messages to be output in a file for understanding what is wrong with the configuration

"throwConfigExceptions":  "true",
"internalLogLevel": "Debug",
"internalLogFile": "<some_path>\\internal_log.log",
  • extensions must be simplified (example):

from

"extensions": {
  "add": [
  {
    "assembly": "NLog.Web.AspNetCore"
  },
  {
    "assembly": "NLog.Appsettings.Standard"
  }
  ]
},

to

"extensions": [
  { "assembly": "NLog.Web.AspNetCore" },
  { "assembly": "NLog.Appsettings.Standard" }
],
  • targets must be simplified:

from

"target": {
   "name": "foo",
}

to

"foo": {

}
  • rules changes:

from

"rules": {
  "logger": [
  {
    "name": "Microsoft.*",
    "maxLevel": "Warn",
    "writeTo": "blackhole",
    "final": "true"
   },

to

"rules": [
  {
    "logger": "Microsoft.*",
    "maxLevel": "Warn",
    "writeTo": "blackhole",
    "final": true
  },

This is not an exhaustive list, but it should cover most of the aspects to consider when performing the migration.

Why does this post require moderator attention?
You might want to add some details to your flag.

0 comment threads

Sign up to answer this question »

This community is part of the Codidact network. We have other communities too — take a look!

You can also join us in chat!

Want to advertise this community? Use our templates!

Like what we're doing? Support us! Donate