Skip to content

NLog v5.2.5 #510

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

NLog v5.2.5 #510

wants to merge 1 commit into from

Conversation

snakefoot
Copy link
Contributor

@snakefoot snakefoot commented May 23, 2025

Maybe the next major-version could also include NLog upgrade?

  • NLog v5.2.5 released 15 Oct 2023

Copy link

🤖 GitHub comments

Expand to view the GitHub comments

Just comment with:

  • run docs-build : Re-trigger the docs validation. (use unformatted text in the comment!)

Mpdreamz
Mpdreamz previously approved these changes May 28, 2025
@Mpdreamz
Copy link
Member

run docs-build

@snakefoot
Copy link
Contributor Author

@Mpdreamz Fixed merge-conflicts, and updated unit-test to not rely on obsolete API.

Mpdreamz
Mpdreamz previously approved these changes Jun 3, 2025
@Mpdreamz
Copy link
Member

Mpdreamz commented Jun 3, 2025

run docs-build

@snakefoot
Copy link
Contributor Author

Little confused about how to handle the failing unit-test SeesMessageWithException, since it works-on-my-machine :)

Guess I just have to wait until build-server-gods are merciful.

@snakefoot
Copy link
Contributor Author

Think I found the cause of the failing unit-tests. NLog doesn't like that one re-assigns NLog.Config.ConfigurationItemFactory.Default.

Unit test are green for me now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants