Skip to main content

Hosting a .NET 4.0 REST service in IIS 6

Last week I had to deploy a WCF 4.0 REST service on an IIS 6 environment. When I ran this service locally everything worked perfect. In the route table I had configured that my service was accessible at http://localhost/servicename/.

But when i tried to call the service on the server environment, I got nothing back. I knew that IIS by default expects that a request can be mapped to a physical file on disk. So what I could have done was adding an SVC file. But I didn’t need an SVC file on my local machine. I wanted a better solution.

It took me some time but with these steps I got everything working as expected:

  1. Open the IIS  manager. Right click on the VirtualDirectoryName where the service is installed and select Properties. On the Virtual Directory Tab click the Configuration Button. Insert a new WildCard Mapping C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\aspnet_isapi.dll. Don’t forget to uncheck Verify that file exists.
  2. Go back to the Properties and open Directory Security Tab. In the Authentication and access control click the Edit Button. Uncheck Integrated Windows Authentication.
  3. Reset IIS(really important!).
Labels:

Popular posts from this blog

.NET 8–Keyed/Named Services

A feature that a lot of IoC container libraries support but that was missing in the default DI container provided by Microsoft is the support for Keyed or Named Services. This feature allows you to register the same type multiple times using different names, allowing you to resolve a specific instance based on the circumstances. Although there is some controversy if supporting this feature is a good idea or not, it certainly can be handy. To support this feature a new interface IKeyedServiceProvider got introduced in .NET 8 providing 2 new methods on our ServiceProvider instance: object? GetKeyedService(Type serviceType, object? serviceKey); object GetRequiredKeyedService(Type serviceType, object? serviceKey); To use it, we need to register our service using one of the new extension methods: Resolving the service can be done either through the FromKeyedServices attribute: or by injecting the IKeyedServiceProvider interface and calling the GetRequiredKeyedServic...
Read more

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