views:

76

answers:

3

I have developed an app on a dev machine using ASP.Net MVC and all is fine and it works. I have moved it to the Prod Server and when I type http://mydomain.com I get the error:

The incoming request does not match any route

If I then make a request to http://mydomain.com/pagename I then get a IIS 7 404 page.

It is hosted in a Full Trust Mode and Integrated Pipeline according to Softsys hosting who its hosted with.

I am currently accessing the site via a temporary DNS name eg/http://mydomain.com.serv7.temphostspace.com and my host believes this might be it.

From the support ticket this is what they say *"I believe, this is caused since you are access your website through temporary URL http://mdomain.com.serv7.temphostspace.com/ and relevant setting might be missing in your configuration."

Any ideas?

Thanks

A: 

Your host is probably barking up the wrong tree, unless the site isn't configured. I'd try and request a static file you know is there to be certain. As for the problem at hand, how are you wiring up the routes? Could something in production be failing before this and prevent this from happening?

Anyhow, first place I would start is by using the ASP.NET Routing Debugger to see what routes your app thinks it has.

Wyatt Barnett
Thanks. I have done a request for a file I know exists test.htm and that gets rendered ok
Jon
A: 

Similar problem: http://stackoverflow.com/questions/213774/iis7-asp-net-mvc-deployment-problem

Resolution from there: http://haacked.com/archive/2008/11/03/bin-deploy-aspnetmvc.aspx

queen3
I have put the MVC dll in the bin directory only as I'm informed that 3.5 SP1 is installed on the server and still no luck
Jon
A: 

Turns out it was trust issues not configured right

Jon