Skip to main content

Class Template is missing in Visual Studio

After playing around with Stylecop for a while, I decided to remove it from my system. So I just uninstalled it and everything seemed fine…until I tried to create a new class in Visual Studio. The class template was gone! I discovered that Stylecop replaces the default class template with it’s own one. However it doesn’t put the old one back in place after removing Stylecop.

So how do you get this template back?

I noticed inside the Visual Studio template folder(C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\ItemTemplates\CSharp\Code\1033) that the class template was still there but renamed. I changed it back to the original name and thought that the job was done. But I still had no class template available.

It took me some time to figure it out but in the end, I solved it by executing the following extra actions:

  • Close all Visual Studio instances.
  • Open a Visual Studio Command prompt.
  • Execute “devenv /InstallVSTemplates”. This command registers project or item templates that are located in <Visual Studio installation path>\Common7\IDE\ProjectTemplates\ or<Visual Studio installation path>\Common7\IDE\ItemTemplates\ so that they can be accessed through the New Project and Add New Item dialog boxes.
  • Execute “devenv /Setup”. This command forces Visual Studio to merge the resource metadata that describes menus, toolbars, and command groups from all VSPackages available.

Only after executing all these steps, my class template was back!

Labels:

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.
Read more

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...
Read more

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         ...
Read more