Skip to main content

Don’t install Async CTP and ASP.NET MVC 3 RC on the same PC

After returning from TechEd Berlin this Friday, I downloaded and install the recent release of the ASP.NET MVC 3 RC build.  Everything seemed fine, until I tried to debug something inside Visual Studio. I couldn’t do any kind of useful debugging.

I found out on Scott Guthrie’s blog that it’s a known issue caused by installing both ASP.NET MVC 3 RC and C#/VB Async CTP. At this moment it isn’t possible to have both the Async CTP and the ASP.NET MVC 3 RC installed on the same machine at the same time.  You instead need to choose one or the other right now – installing both will cause problems.

To fix this, go to Add/Remove Programs and uninstall both the ASP.NET MVC 3 RC build (including the VS Tools components for it) and the Async CTP. Once you’ve uninstalled both your machine will be back to a clean state and working fine.  You can then choose to install either the Async CTP or ASP.NET MVC 3 RC and it will work fine.

Async CTP Uninstall Instructions

The Microsoft Visual Studio Async CTP is installed as two updates:

1) .NET Framework 4.0 update called “.NET Framework Async CTP”
2) Microsoft Visual Studio 2010 update called “Microsoft Visual Studio Async CTP”

To uninstall go to Control Panel > Programs and Features > View installed updates. You will need to uninstall both updates.

ASP.NET MVC 3 RC Uninstall Instructions

To completely uninstall MVC 3 RC, you actually need to uninstall all of the following:

  • Microsoft ASP.NET MVC 3
  • Microsoft ASP.NET MVC 3 - Visual Studio 2010 Tools (only installed when you have Visual Studio 2010)
  • Microsoft ASP.NET MVC 3 - VWD Express 2010 Tools (only installed if you have Visual Web Developer 2010 Express)
  • Microsoft ASP.NET Web Pages
  • Microsoft ASP.NET Web Pages - Visual Studio 2010 Tools (only installed when you have Visual Studio 2010)
  • Microsoft ASP.NET Web Pages - VWD Express 2010 Tools (only installed if you have Visual Web Developer 2010 Express)
  • NuGet
  • Update for Microsoft Visual Studio 2010 -  (KB2385361) (only installed when you have Visual Studio 2010)
  • Update for Microsoft Visual Web Developer 2010 Express -  (KB2385361) (only installed if you have Visual Web Developer 2010 Express)
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