# Monday, January 20, 2014
« ng-conf videos available | Main | Are you interested in an aspiring techno... »

Recently we upgraded to Visual Studio 2013 at my client. This morning my colleague came over and had a small problem. Some of the .svc services gave 404 errors. As I had another solution open of which I knew the in project .svc services simply worked I sat down with him. Some searching on the internet, trying out http activation, reregistering WCF, … it didn’t work out.

The difference between both solutions was that the one I was looking at was Webforms while the other one was MVC4 based. Aha! I used Nuget to include routedebugger. A super handy package for, well, debugging MVC routes. However since the .svc files themselves were put into a /Services subfolder I had to make it up like this:


Put this at pretty much of the top of all the route configuration so that it gets picked up early.

The funny part was that the .svc was working pretty fine, even the wsdl could get obtained. However when we wanted to make a REST call to a specific method it gave 404 mistakes. Turned out to be that the default {controller}/{action}/{id} that ships with every template caught it. Making a more specific rule near the top of the configuration dealt with it and it all started out working smoothly again.

After testing it locally with IIS Express we also tested it out on Cassini due to the fact that the servers are still not up to IIS 8 at the moment and that also worked out fine.

Grz, Kris.