asp.net-mvc-areas

I've been following this guide from MSDN about "Creating an ASP.NET MVC Areas Application Using Multiple Projects" . Since ASP.NET MVC 2.0 is just preview one would imagine there to be some bugs. My problem is, it simply doesn't work! At least not the way it's suppose to. After setting everything up and pressing F5, one would think that, this will work, neat! BEEEP. Wrong. It doesn't find the Views in the child project! Because in my case it tries to search within ~/Views which of course is in the parent! When debugging i see that it Does run the Controller inside my child project, but when

I was able to to use ASP.NET MVC 3 and Ninject 2.2 to inject a logger object into a custom ActionFilterAttribute thanks to the help I received in this post . Now I would like to bind my custom ActionFilterAttribute only to all controllers that are in a specific area. I was able to get started with the following binding but it only handles one controller in a certain area. I would like my code to bind to all controllers in a specific area. Any ideas? /// <summary> /// Load your modules or register your services here! /// </summary> /// <param name="kernel">The kernel.</param> private static

I have just deployed an MVC4 .NET 4.0 app to my web host, for 'live' deployed testing. Non -area routes are working fine, e.g. my @Html.ActionLink("Register as a Client", "Register", "Account", new { registrationType = "Client"}, null) link works fine, and the link opens the correct page. However, with a link to an area based action like this: @Html.ActionLink("Authors", "Index", "Home", new { Area = "Author", registrationType = "Author" }, null) the link actually rendered to the browser is missing action and controller, i.e. http://mylivedomain.com/?Area=Author&registrationType=Author It may

Since it doesn't appear to be supported natively, what's the recommended way of implementing global filters on a per-area basis? You could use a custom IFilterProvider . Levi The reason it's not supported natively is because we want to discourage developers from doing it. Areas are not associated with controllers; they're associated with routes . We wanted to discourage developers from trying to apply authorization or other security-sensitive filters to areas since they can be bypassed. See How can we set authorization for a whole area in ASP.NET MVC? for more information. 来源： https:/

My model is public class SiteConfig { public SiteConfig() { } public int IdSiteConfig { get; set; } public string Name { get; set; } public byte[] SiteLogo { get; set; } public string Brands { get; set; } public string LinkColour { get; set; } public IEnumerable<SiteBrand> SiteBrands { get; set; } } and public class SiteBrand { public int Id { get; set; } public int SiteId { get; set; } public int BrandId { get; set; } public Brand Brand { get; set; } public SiteConfig SiteConfig { get; set; } } public class Brand { public int BrandId { get; set; } public string Name { get; set; } public