views:

54

answers:

2

I have converted my asp.net mvc project to asp.net mvc website.

Everything works find under IIS but under Cassini it doesn't resolve the URLs, even tough it does it when its an MVC project !!

What could be wrong ?

A: 

As a comparison, one of the ways to get it to get MVC to work correctly in IIS6 is to have all requests for all files run though aspnet_isapi.dll filter. I believe this is called wildcard mapping. Is there a similar feature in Cassini?

See this doc for reference on setting up wildcard mapping in II6, perhaps it might jog an idea for setting up in Cassini.

http://haacked.com/archive/2008/11/26/asp.net-mvc-on-iis-6-walkthrough.aspx

Update

There is a couple of references to cassini in the above link that may help.

Michael Gattuso
AFAIK: Cassini is already a managed web server (more similar to IIS7 than IIS6) that serves ALL requests via .net - managed requests, because there's no other mechanism in it. But it has its quirks that prevent it from working as IIS7.
Robert Koritnik
Rob - thanks for the info. It's been a long time since I played with Cassini.
Michael Gattuso
Sorry guys, but nothing ya'll said had anything to do with my question !
Binder
A: 

I have the following environment at work.

IIS6 on the desktop. IIS7 on production server. => Yeah I know!

So I use Cassini to debug everything and it works fine. I do however make all the global.asax changes required to make it run in IIS 6 and I test that periodically.

When it comes time to deploy I switch on the IIS 6 site and give it a good test. Nothing beats log files at this point. I also use Dubug / Attach to process... / asp.net WP so that I can still debug if there are issues.

When we all go to IIS7 on the desktops that should stop all that and I can probably ditch Cassini.

griegs
Dude, what does all of this have to do with the question I posted ?
Binder