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.
Code Cleanup on Save in Visual Studio 2022
Earlier I posted Auto Save files in Visual Studio 2022, which saves the files in the background when Visual Studio loses the focus. There is another feature available which would do the Code Cleanup on save in Visual Studio 2022. This feature will automatically clean up your code file based on the preferences you have configured. This feature will save the developer time as he doesn’t have to deal with certain tasks related to code cleanup or coding standards. So, let’s see how can we use this new feature.
Read MoreAuto Save files in Visual Studio 2022
Earlier I posted about Temporary breakpoint – New feature in Visual Studio 2022, and in continuation with Visual Studio 2022 exploration, here is another new feature which will auto save files in Visual Studio 2022. This feature may come handy when you have to switch between different tools while working on your tasks. This would also ensure that your code is not out of sync, if the same files are opened in other tools along with Visual Studio.
Read More
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.
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
How to run locally build docker images with Kubernetes
To run Kubernetes in your local environment, Minikube is your choice. Minikube is a lightweight Kubernetes implementation that creates a Virtual Machine on your local machine and deploys a simple cluster containing only one node. By default, Minikube will always pull the docker images from the docker repository. To test locally build docker images with Minikube, you got to tell Minikube to refer them from your local system, instead of fetching from the docker registry. There are various ways to tell Minikube to look for local docker images. In this post, we’ll see how to run locally build docker images with Kubernetes. Read More