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
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Welcome to Software Development on Codidact!

Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.

Post History

50%
+0 −0
Q&A How to migrate NLog configuration from XML file(s) to application settings (JSON)?

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 conf...

posted 2y ago by Alexei‭  ·  edited 2y ago by Alexei‭

Answer
#2: Post edited by user avatar Alexei‭ · 2022-07-12T12:13:14Z (over 2 years ago)
clarified that the steps were manually performed
  • FreeFormatter resource mentioned in the question is useful and I could use the output as a base for getting to a working configuration:
  • - enable throw configuration exceptions and allow for internal log messages to be output in a file for understanding what is wrong with the configuration
  • ```json
  • "throwConfigExceptions": "true",
  • "internalLogLevel": "Debug",
  • "internalLogFile": "<some_path>\\internal_log.log",
  • ```
  • - extensions must be simplified (example):
  • from
  • ```json
  • "extensions": {
  • "add": [
  • {
  • "assembly": "NLog.Web.AspNetCore"
  • },
  • {
  • "assembly": "NLog.Appsettings.Standard"
  • }
  • ]
  • },
  • ```
  • to
  • ```json
  • "extensions": [
  • { "assembly": "NLog.Web.AspNetCore" },
  • { "assembly": "NLog.Appsettings.Standard" }
  • ],
  • ```
  • - targets must be simplified:
  • from
  • ```json
  • "target": {
  • "name": "foo",
  • }
  • ```
  • to
  • ```json
  • "foo": {
  • }
  • ```
  • - rules changes:
  • from
  • ```json
  • "rules": {
  • "logger": [
  • {
  • "name": "Microsoft.*",
  • "maxLevel": "Warn",
  • "writeTo": "blackhole",
  • "final": "true"
  • },
  • ```
  • to
  • ```json
  • "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.
  • [FreeFormatter resource mentioned in the question](https://www.freeformatter.com/xml-to-json-converter.html) 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
  • ```json
  • "throwConfigExceptions": "true",
  • "internalLogLevel": "Debug",
  • "internalLogFile": "<some_path>\\internal_log.log",
  • ```
  • - extensions must be simplified (example):
  • from
  • ```json
  • "extensions": {
  • "add": [
  • {
  • "assembly": "NLog.Web.AspNetCore"
  • },
  • {
  • "assembly": "NLog.Appsettings.Standard"
  • }
  • ]
  • },
  • ```
  • to
  • ```json
  • "extensions": [
  • { "assembly": "NLog.Web.AspNetCore" },
  • { "assembly": "NLog.Appsettings.Standard" }
  • ],
  • ```
  • - targets must be simplified:
  • from
  • ```json
  • "target": {
  • "name": "foo",
  • }
  • ```
  • to
  • ```json
  • "foo": {
  • }
  • ```
  • - rules changes:
  • from
  • ```json
  • "rules": {
  • "logger": [
  • {
  • "name": "Microsoft.*",
  • "maxLevel": "Warn",
  • "writeTo": "blackhole",
  • "final": "true"
  • },
  • ```
  • to
  • ```json
  • "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.
#1: Initial revision by user avatar Alexei‭ · 2022-07-12T12:12:03Z (over 2 years ago)
FreeFormatter resource mentioned in the question is useful and I could use the output as a base for getting to a working configuration:

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

```json
"throwConfigExceptions":  "true",
"internalLogLevel": "Debug",
"internalLogFile": "<some_path>\\internal_log.log",
```

- extensions must be simplified (example):

from 

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

to

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

- targets must be simplified:

from

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

to

```json
"foo": {

}
```

- rules changes:

from

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

to

```json
"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.