Try this : <%= Html.ActionLink(“Back”, “Index”, “Home”, new { area = “” }, null) %> When using Areas, you should always specify the area your are calling in your ActionLinks by adding a route value as above, If the link is outside the area (as in your case), just use an empty parameter for the … Read more
You can specify the area as part of the RouteValueDictionary (or just object of route values) which RenderAction takes as a third parameter in your case: Html.RenderAction(“UserInfo”, “Account”, new { area = “” }); This is assuming the Account controller is in the root area.
Right click on your web project and select Add -> Area… Then type the name of the area and Visual Studio will take care of the rest which is to generate all the necessary classes. For example the area registration might look like this: public class AreasDemoAreaRegistration : AreaRegistration { public override string AreaName { … Read more
Simply specify a blank area for them if they are to be served from root controllers: <li>@Html.ActionLink(“About Us”, “About”, “Home”, new { area = “” }, null)</li>
Strange indeed. Steps that worked perfectly fine for me: Create a new ASP.NET MVC 3 application using the default Visual Studio template Add an area called Admin using Visual Studio designer by right clicking on the project Add new Controller in ~/Areas/Admin/Controllers/MeetsController: public class MeetsController : Controller { public ActionResult Index() { return View(); } … Read more
What you need to do is set a token to your area name: for instance: context.MapRoute( “SomeArea_default”, “SomeArea/{controller}/{action}/{id}”, new { controller = “SomeController”, action = “Index”, id = UrlParameter.Optional } ).DataTokens.Add(“area”, “YOURAREANAME”);
Web.config-based security should almost never be used in an MVC application. The reason for this is that multiple URLs can potentially hit a controller, and putting these checks in Web.config invariably misses something. Remember – controllers are not associated with areas, routes are associated with areas. The MVC controller factory will happily serve controllers from … Read more
In order to include an Area in an ASP.NET Core app, first we need to include a conventional route in the Startup.cs file (It’s best to place it before any non-area route): In Startup.cs/Configure method: app.UseMvc(routes => { routes.MapRoute(“areaRoute”, “{area:exists}/{controller=Admin}/{action=Index}/{id?}”); routes.MapRoute( name: “default”, template: “{controller=Home}/{action=Index}/{id?}”); }); Then make a folder named Areas in the app … Read more
I’ve found it. When a page, that is located inside an area, wants to access a controller that is located outside of this area (such as a shared layout page or a certain page inside a different area), the area of this controller needs to be added. Since the common controller is not in a … Read more
You just have to add a file named: _ViewStart.cshtml Under each area views folder: /Areas/Area1/Views/_ViewStart.cshtml And edit the file to point to the root layout like this: @{ Layout = “~/Views/Shared/_Layout.cshtml”; } In order for this to work, you do not have to specify a value in the view’s layout property, if you do, you … Read more