Serilog is a third-party, open-source structured logging library. It provides diagnostic logging to files, the console, and elsewhere. It is easy to set up, has a clean API, and is portable between recent .NET platforms. In the ASP.NET Core framework, Serilog has emerged as a popular logging library due to its flexibility, extensibility, and ease of use. In continuation with Shorts Series, here is a another very short post to add or enable Serilog in ASP.NET Core 7.0 application.
Read MoreCategory: ASP.NET Core
Shorts Series – Add or Enable OData in ASP.NET Core 7.0
In today’s world, where videos have become increasingly shorter and gained immense popularity through platforms like YouTube Shorts, Insta Reels, and TikTok, why shouldn’t blog posts follow suit? I’m considering launching a series of brief blog posts that you can read and finish in less than one minute. Here is a very short post to add or enable OData in ASP.NET Core 7.0 application.
Read MoreTroubleshooting Common Errors and Issues in .NET 7.0
Earlier I posted about what’s new in ASP.NET Core 7.0 but at the same time the release of a new version of the .NET framework brings exciting features and improvements to the development experience. However, like any software release, there can be occasional errors and issues that developers may encounter while working with .NET 7.0. In this blog post, we will explore some common errors and issues that you may come across when using .NET 7.0 and provide troubleshooting tips to help you overcome them effectively.
Read MoreWhat’s New in ASP.NET Core 7
ASP.NET Core 7 is a significant update for the open-source cross-platform framework for building modern web applications. The new version comes packed with a lot of exciting features and improvements that enhance the development experience and performance. In this blog post, we will discuss some of the most significant changes in ASP.NET Core 7.
Read MoreClean way to add Startup class in ASP.NET Core 6
If you are following ASP.NET Core 6, then probably you are aware that with ASP.NET Core 6.0 projects, there is no Startup.cs file. It is now combined with Program.cs file to bring unified experience. I posted about How to Add Startup.cs in ASP.NET Core 6 Project and this approach brings Startup.cs class in the project in a traditional way that we have today with ASP.NET Core 5 and it’s prior version. But what if we can improve things and make it better. Well, in this post, let’s take a look at a clean way to add Startup class in ASP.NET Core 6 projects.
How to add Swagger to ASP.NET Core 6 Application
Swagger is very popular and doesn’t need an introduction. It helps you to test your API. Earlier, I posted about how to add Swagger to ASP.NET Core 2.0 web API and those steps still works for ASP.NET Core 5 based applications where you bring Swashbuckle nuget packages and then add code to Startup.cs file to enable Swagger. But with ASP.NET Core 6, things have become a little easy and time saving. Now you can easily add swagger to ASP.NET Core 6 application with a mouse click.
How to Add Startup.cs in ASP.NET Core 6 Project
With ASP.NET Core 6.0 projects, you will not find Startup.cs file. By default, this file is removed and Program.cs is the new place where you need to register your dependencies and Middleware. But if you are a fan of Startup.cs or upgrading your project to ASP.NET Core 6.0, you might want back the Startup.cs file. So in this post, let’s find out how to add Startup.cs in ASP.NET Core 6 project.