Tuesday, May 19, 2015
This post describes how to perform Url Routing to a Web Service. If you’re just interested in the solution, click here.
OK, this was a tough one.
The goal was to implement URL routing for an existing web site that has asmx Web Services. The intention was to allow white-labeling
of the Web Services. You might argue why one would want to do that, so
I’ll summarize by writing that one of the reasons to do so was that I
wanted to enjoy URL Routing advantages, without having to rewrite the
existing Web Services into a more “modern” alternative such as MVC.
Other reasons are obvious: Web APIs are becoming more and more URL
friendly and allow great flexibility.
Note that the web site is written in .NET 4 over IIS7, so I won’t get
into how to configure routing or web services. You can read here about Routing, and specifically about Routing in WebForms here.
Unlike routing in MVC which you can’t really do without, in WebForms
this is less trivial. In WebForm’s Routing we have the MapPageRoute
method, but we have nothing specific for Web Services or other handlers.
I already blogged
about how to route to a handler (ashx), but I found it much less
trivial to accomplish routing for Web Services, and in this post I’ll
try to explain why...
See more:
https://evolpin.wordpress.com/2012/12/30/net-4-url-routing-for-web-services-asmx/