Skip to main content

Impress your colleagues with your knowledge about... the Visual Studio Hosting process.

Sometimes when working with C# you discover some hidden gems. Some of them very useful, other ones a little bit harder to find a good way to benefit from their functionality. One of those hidden gems that you all used but probably never wondered about is the vshost file.

When you create and compile an application in Visual Studio you get 2 executables for the price of one; your main output exe and a second vshost.exe file. The second executable is used by default when you are debugging your application. It was introduced in Visual Studio 2005 and its purpose is to provide improved debugging performance(among other things like Enabling Partial-Trust Debugging and Design-Time Expression Evaluation).

image

Without this hosting process, every time you debug your application an AppDomain has to be created, the debugger needs to be initialized and so on… This takes time and has a negative impact on the overall performance of your debugging experience. The hosting process speeds up this process by doing all of this work in the background before you hit F5, and keeping the state around between runs of your application.

If you don’t want to use this feature, you can disable it in the Project Properties by unchecking the “Enable the Visual Studio hosting process”:

image

MSDN Documentation: https://msdn.microsoft.com/en-us/library/ms242202.aspx

Popular posts from this blog

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...