This project is read-only.

Migrating to Standalone Host

Topics: Web Api
Oct 28, 2011 at 5:44 PM

Hi all,

I'm migrating from IIS to standalone hosting. I don't know about you, but every time I have to install and deploy something to IIS I have problems. I'm not saying that IIS isn't good, but I'm not an IIS expert and I'm always thinking what problems I will have next time I will deploy application. My new notebook is an example. I could not make it work on it after two hours trying.

By the other side, using a standalone version makes the server run in a different port since my client (html + js files = easy deploy) is still running on IIS:80. Now I have to deal with proxies or JSONP to bypass the cross domain problem.

What is you preferred option? What the pros and cons of each one?

Talking about the standalone version, I have some questions.

1) Do I have to open a host to each service contract? I though it would be one host and lots of endpoints. Maybe I'm doing something wrong.

2) With the web version, I had the BeginRequest and EndRequest events, and they worked for any call to any service contract. What should I use now?


Thank you