Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>My friend and I were experiencing the same issue with Areas in ASP.NET MVC 2. We found a "hack" that, so far, seems to be working. For the tl;dr version, see the bottom of this answer.</p> <p>You've probably got something similar to the following in your "Admin" area's "AdminAreaRegistration.cs" class:</p> <pre><code>// Web/Areas/Admin/AdminAreaRegistration.cs public override void RegisterArea(AreaRegistrationContext context) { context.MapRoute( "Admin_default", "Admin/{controller}/{action}/{id}", new { action = "Index", id = UrlParameter.Optional } ); } </code></pre> <p>Thus, it should make sense that when you make a request for "<a href="http://website/Abstract" rel="nofollow noreferrer">http://website/Abstract</a>", the "Admin_default" route does not match the request. So, by design, the MVC framework attempts to match the request against any other defined routes. If you used the MVC tooling within Visual Studio to create your web project, you'll have a "Default" route defined in your "Global.asax" file (at the root of your web project). It should look similar to this:</p> <pre><code>// Web/Global.asax.cs public static void RegisterRoutes(RouteCollection routes) { routes.IgnoreRoute("{resource}.axd/{*pathInfo}"); routes.MapRoute( "Default", "{controller}/{action}/{id}", new {controller = "Home", action = "Index", id = UrlParameter.Optional} ); } </code></pre> <p>The "Default" route succeeds in matching the request for "<a href="http://website/Abstract" rel="nofollow noreferrer">http://website/Abstract</a>", with "controller" = "Abstract", "action" = "Index" (default value), and "id" = UrlParameter.Optional (default value). This is the correct, and intended, behavior... so far.</p> <p>Now, the MVC framework will attempt to load the "Abstract" Controller. By design, MVC will search for a class called "AbstractController" that extends "Controller" anywhere within the web project's file/namespace hierarchy. It is important to note that a Controller's file location and namespace do not affect MVC's ability to find it; in other words, just because you've placed the "AbstractController" within a folder called "Areas\Admin\Controllers" and changed the namespace to be "Web.Areas.Admin.Controllers" instead of, say, "Web.Controllers", doesn't mean that MVC won't use it.</p> <p>When MVC executes the "Index" action in "AbstractController" which, most likely, just returns "View()", then MVC gets confused because it doesn't know where to find the "Index" view. Because MVC has matched a non-area route (the "Default" route in Global.asax), it thinks the matching view should be located in non-area view folders. Thus you get the familiar error message:</p> <pre><code>The view 'Index' or its master was not found. The following locations were searched: ~/Views/Abstract/Index.aspx ~/Views/Abstract/Index.ascx ~/Views/Shared/Index.aspx ~/Views/Shared/Index.ascx </code></pre> <p>We, just as you, didn't want requests for "<a href="http://website/Abstract" rel="nofollow noreferrer">http://website/Abstract</a>" to resolve to "Admin" area's "AbstractController"; only "<a href="http://website/Admin/Abstract" rel="nofollow noreferrer">http://website/Admin/Abstract</a>" should work. I can't think of why anyone would want this behavior.</p> <p>A simple solution is to delete the "Default" route in Global.asax, <em>but</em> this will break any regular non-area Controllers/Views. This is probably not an option for most people...</p> <p>So, we thought we could restrict the set of Controllers that MVC would use for requests matched by the "Default" route in Global.asax:</p> <pre><code>// Web/Global.asax.cs public static void RegisterRoutes(RouteCollection routes) { routes.IgnoreRoute("{resource}.axd/{*pathInfo}"); routes.MapRoute( "Default", "{controller}/{action}/{id}", new {controller = "Home", action = "Index", id = UrlParameter.Optional}, new[] {"Web.Controllers"} // Added this line ); } </code></pre> <p>Nope. A request for "<a href="http://website/Abstract" rel="nofollow noreferrer">http://website/Abstract</a>" will <em>still</em> use "AbstractController" within the "Admin" area, even though the "AbstractController"'s namespace is "Web.Areas.Admin.Controllers" and (clearly) not "Web.Controllers". This is thoroughly confusing; it seems like this white-list has no dicernable affect on MVC's Controller resolution.</p> <p><strong>- tl;dr answer starts here -</strong></p> <p>After some hacking, we figured out how to force MVC to only use Controllers within the white-listed namespace(s).</p> <pre><code>// Web/Global.asax.cs public static void RegisterRoutes(RouteCollection routes) { routes.IgnoreRoute("{resource}.axd/{*pathInfo}"); routes.MapRoute( "Default", "{controller}/{action}/{id}", new {controller = "Home", action = "Index", id = UrlParameter.Optional}, new[] {"Web.Controllers"} ).DataTokens["UseNamespaceFallback"] = false; // Added this line } </code></pre> <p>Set the "UseNamespaceFallback" key of the DataTokens dictionary on the "Default" route to false. Now, when we make a request for "<a href="http://website/Abstract" rel="nofollow noreferrer">http://website/Abstract</a>", the "Default" route will still be matched (this is valid behavior!) but MVC will <em>not</em> use any Controller that is not within the defined namespace(s); in this case, only Controllers within the "Web.Controllers" namespace are valid. Finally, this is the functionality we were looking for! We can't figure out why this isn't the default behavior. Weird, huh?</p> <p>Hope this helps.</p>
    singulars
    1. This table or related slice is empty.
    1. POASP.NET MVC 2 RC 2 returns Area-specific controller when no area specified
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USBrad B.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POASP.NET MVC 2 RC 2 returns Area-specific controller when no area specified
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    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. COthanks for the detailed response. best answer i've seen yet. i had resorted to just hard-coding routes to all my root controllers.
      singulars
      1. PO
      1. USBryan
    2. COthis is great answer.. I just met the same behaviour and really surprised with it, actually.
      singulars
      1. PO
      1. USAlexander Beletsky
 

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