Skip to main content
Temporary-breakpoint-–-New-feature-in-Visual-Studio-2022

Temporary breakpoint – New feature in Visual Studio 2022

Breakpoints are great help for the developers to debug the code in Visual Studio. Sometimes while debugging an interconnected call, we as developers tend to put breakpoints in every class to find out if a particular code is hit or not. And once our problem is solved, we forget to remove those breakpoints. So, next time while debugging, those breakpoints may hit again, and that is annoying as now you don’t want them to hit. To help overcome such situation in better way here is, Temporary Breakpoints – New feature in Visual Studio 2022.

Read More

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

A clean way to add Swagger to ASP.NET Core application

Swagger needs no introduction. It is one of the best methods to test your WEB APIs. Adding swagger to your ASP.NET Core application is very easy and straightforward. I already have a couple of posts on my blog on Swagger. Swagger comes with many options and customization to help you prepare better API documentation. The ASP.NET Core Startup.cs is the place to add Swagger or any middleware that you would like to use in your ASP.NET Core application. The Startup.cs file will become lengthy when we use more swagger customization. So in this post, we’ll see a clean way to add Swagger to ASP.NET Core application using C# extension methods. Read More

Create a Trimmed Self-Contained Single Executable in .NET Core 3.0

A self-contained app is a great way to share your application as all components, runtime, and framework are included with the application. All you have to provide is the application .exe file without worrying about the presence of framework or runtime installation status on other machines. .NET Core 3.0 Preview 6 is out and there are a lot more new features. One of the useful feature is the introduction of PublishTrimmed flag. This flag reduces the size of the executable to a great extent and create a trimmed self-contained single executable in .NET Core 3.0.
Read More