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 MoreTag: ASP.NET Core
What’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.
Upgrade ASP.NET Core Web 3.1 app to ASP.NET Core 5
There is no .NET Core 5.0, everything now comes under one umbrella, which is .NET 5 (A Major Release). The idea is to bring all .NET runtimes into a single .NET platform with unified base class libraries (BCL) for all kinds of application like ASP.NET Core, Windows Forms, WPF, Blazor, Xamarin etc. This move now makes .NET a unified platform for all types of .NET applications. If you are working with ASP.NET Core 3.1 app, and planning to upgrade the app to .NET 5 then it’s very easy to upgrade ASP.NET Core Web 3.1 app to ASP.NET Core 5.
Read More
ASP.NET Core 5 – Enabling Razor runtime compilation
Razor files (.cshtml) are compiled at both build and publish time and this gives better performance as your views are compiled. We can also enable runtime compilation, which will help developers to see any modified view change in real-time, without starting the application again. The recent version of ASP.NET Core (ASP.NET Core 5.0) Preview 2 came out and you can start building an app on ASP.NET Core 5.0 framework. ASP.NET Core 5.0 changes this experience for enabling razor runtime compilation. This is now available as an option while creating the ASP.NET Core 5.0 project. It’s a tiny enhancement, but good to know. Read More