Skip to content
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.

Sign up for GitHub

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

Jump to bottom

links to follow up post #12

Merged
merged 2 commits into from
Sep 25, 2018
Merged

links to follow up post #12

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
fec63a6
links to follow up post
robertmuehsig Sep 25, 2018
b6aa51a
Highlight the current article with a bold font
JuergenGutsch Sep 25, 2018
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions _source/_posts/2018-09-20-customizing-aspnetcore-01-logging.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,8 +14,8 @@ In this first part of the new blog series about customizing ASP.NET Core, I will

## The series topics

- Customizing ASP.NET Core Part 01: Logging
- Customizing ASP.NET Core Part 02: Configuration
- **Customizing ASP.NET Core Part 01: Logging - This article**
- [Customizing ASP.NET Core Part 02: Configuration]({% post_url customizing-aspnetcore-02-configuration.md %})
- Customizing ASP.NET Core Part 03: Dependency Injection
- Customizing ASP.NET Core Part 04: HTTPS
- Customizing ASP.NET Core Part 05: HostedServices
Expand Down Expand Up @@ -223,4 +223,4 @@ The first line configures NLog to use the previously created `NLog.Config` and t

The good thing of hiding the basic configuration is only to clean up the newly scaffolded projects and to keep the actual start as simple as possible. The developer is able to focus on the actual features. But the more the application grows the more important is logging. The default logging configuration is easy and it works like charm, but in production you need a persisted log to see errors from the past. So you need to add a custom logging or a more flexible logger like NLog or log4net.

To learn more about ASP.NET Core configuration have a look into the next part of the series: [Customizing ASP.NET Core Part 02: Configuration]({% post_url customizing-aspnetcore-02-configuration.md %}).
To learn more about ASP.NET Core configuration have a look into the next part of the series: [Customizing ASP.NET Core Part 02: Configuration]({% post_url customizing-aspnetcore-02-configuration.md %}).