Menu
I have tried to create simple proof-of-concept ASP.NET MVC 4 web site using areas in separate projects.
I tried to following tutorials: http://bob.archer.net/content/aspnet-mvc3-areas-separate-projects (Application doesn't work in virtual directory... I use IIS). I hope there is better way than virtual directories.
Then I tried this tutorial: http://forums.asp.net/t/1483660.aspx/1 But there is no "AreasManifestDir" element in *.csproj of area project (and got error "The view 'Index' or its master was not found or no view engine supports the searched locations")
Is there still support in ASP.NET for MVC 4? Because I found this answer that it can be removed in future: What are the pros and cons of Areas implemented as single projects vs multiple projects in asp.net mvc
I haven't found any how-to for MVC4.
Structure of solution is simple:
Solution 'MvcAreasMultiProject'
Areas [Directory]
Admin [Project]
Models
Views
Controllers
Routes.cs [Examples]
MvcAreasMultiProject [MainProject]
- References Admin project
M.V.C
Routes.cs of Admin project:
namespace Admin
{
public class Routes : AreaRegistration
{
public override string AreaName { get { return "Admin"; } }
public override void RegisterArea(AreaRegistrationContext context)
{
context.MapRoute(
"Admin_Default",
"Admin/{action}/{id}",
new { controller = "Admin", action = "Index", id = "" },
new[] { "Admin.Controllers" }
);
}
}
}
Thanks for any help!
970
You could use the RazorGenerator package to embed your Razor views into a separate assembly. Here are the steps to make this work:
Razor Generator Visual Studio extension (Tools -> Extensions and Updates...)AreasLibrary (you could also use an ASP.NET MVC project template in order to get Intellisense in Razor views)RazorGenerator.Mvc NuGet to the AreasLibrary project.Add a controller inside the AreasLibrary project (~/Areas/Admin/Controllers/HomeController.cs):
public class HomeController: Controller
{
public ActionResult Index()
{
return View();
}
}
Add a corresponding view (~/Areas/Admin/Views/Home/Index.cshtml):
@* Generator: MvcView *@
@{
Layout = null;
}
<!DOCTYPE html>
<html>
<head>
<meta name="viewport" content="width=device-width" />
<title>View1</title>
</head>
<body>
<div>
Index view
</div>
</body>
</html>
In the properties of the view set the Custom Tool to RazorGenerator.
Inside the class library add an ~/Areas/AdminAreaRegistration.cs:
public class AdminAreaRegistration : AreaRegistration
{
public override string AreaName { get { return "Admin"; } }
public override void RegisterArea(AreaRegistrationContext context)
{
context.MapRoute(
"Admin_Default",
"Admin/{action}/{id}",
new { controller = "Home", action = "Index", id = "" }
);
}
}
All that's left is to reference the class library in the main MVC application.
Reference: http://blog.davidebbo.com/2011/06/precompile-your-mvc-views-using.html
117
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
