Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Did you try debugging your routes using <a href="http://haacked.com/archive/2008/03/13/url-routing-debugger.aspx" rel="nofollow noreferrer">Phil Haack route debugger</a> on the server?</p> <p><strong>Edit:</strong><br> On IIS 7.5 you dont need any special extensionless handler, this is handled automatically, you don't need to change anything. It is only necessary on IIS 6 as far as I know. Could that be the problem? what if you remove that special handler? maybe this is what is stopping it to kick in the route engine.</p> <p><strong>Edit:</strong><br> I double checked, and as I thought, starting on IIS7, the default mode of a AppDomain is <strong>Integrated Mode</strong>. This means that the Asp.net stack kicks in at every request, while in classic mode, asp.net was called only when an specific extensions where called (aspx ashx axd are mapped by default to the aspnet_isapi filter).<br> <strong>UrlRoutingModule</strong> is kicking in at every request without requiring anything from you because it is an HttpModule and not a Handler. (it just needs to be registered in the config file of your application, no need to map it to an extension, but that's by default in an MVC app. You can open you Web.Config file and verify that you have under <em></em> a node </p> <pre><code>&lt;modules runAllManagedModulesForAllRequests ="true"&gt; ... &lt;add name="UrlRoutingModule" type=.../&gt; &lt;/modules&gt; </code></pre> <p>Are you sure you deploy the MVC assemblies to the server? Check that <em>System.Web.Mvc</em>, <em>System.Web.Routing</em> and <em>System.Web.Abstraction</em> references have the Copy Local property set to true to be sure you use the same assemblies locally and on your production server...</p> <p>If all that is correct, I don't know how to help you more... I hope this will help you, or at least put you on the right tracks.</p> <p><strong>EDIT:</strong> Oww... just read your last comment... sorry I missed that element about classic mode. Your title mentions IIS7.5 and I assumed too much things. that's why I got confused.</p> <p>Honnestly now, I had to look in the book of Steven Sanderson. He has a checklist for troubleshooting IIS6 deployment. I know you're saying it's only when using MSBuild 4 that it fails, but it might still be usefull</p> <p>Check that Default.aspx is set as default content page. That could be the source of 404.</p> <p>Then to have extensionless urls, last time I deployed to IIS6 I used a simple wildcard map and I never had a problem... If you're still in trouble sorry that I could'nt help... not that I didnt try :) good luck</p>
    singulars
    1. This table or related slice is empty.
    1. PODeploy ASP.NET MVC 2 to IIS 7.5 targeting .NET 3.5
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USStéphane
    1. USStéphane
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COIt's not hitting the routing engine. That's the problem. Despite the web.config being configured, IIS appears to be ignoring it and returning it's standard 404. Enabling IIS tracing reveals that the routing handlers and modules are not being executed.
      singulars
      1. PO
      1. USAgent_9191
    2. COIn response to your edit, I needed the handler in there when it was compiled using MSBuild 3.5. Otherwise IIS doesn't know to send the page through the routing engine.
      singulars
      1. PO
      1. USAgent_9191
    3. COhm, I'm a bit confused because the Build shouldn't change anything at all concerning request handling. Your problem seems to happen even before it's hitting your app. Could you check that your app pool runs in Integrated Mode? I have to leave now, but I'll post an extended answer later.
      singulars
      1. PO
      1. USStéphane
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload