Sticking to Default Routs in ASP .NET MVC

When dealing with the sharing of code on a project, I feel like having conventions and standards and following are of the utmost importance.  Only by following the patterns can someone else walk in and understand what is going on.  It also helps newer programmers by letting their acquired knowledge apply across environments.

Occasionally I see people really get into routing when dealing with a web MVC framework.  I have even seen some who place custom routing in their top 5 must haves when looking for a web MVC framework. While it can be fun and rewarding, the most elegant solution sometimes is the one that is default.  Further in my environment we hold to the standard that the simplest is usually the best.  This means using default routing if possible, period.  The first choice we made was already MVC .NET and therefore adhearing to the internal conventions is implied.  For the sake of this conversation we will be assuming we are using MVC as a UI.  API functionality beyond REST may or may not require a different approach. Let us take a walk down the path of :

‘What does that mean practically?’

Here is the default route registered in a new project:

Default Route

Imagine you publish to a place that is reachable via  Say you have a controller called MyController that resides within the Controllers folder in your project.  It has two methods : Index() and World().  If you go to you will see the output of the Index() action on MyController since the default action is Index().  You can also execute the same action by going to  Hopefully this aids in making sense of the fact that if you visit the action MyController.World() is executed.  Also, by understanding how defaults work, you understand that when you visit the routing is wanting you to have a controller named Home with an action method of Index().

This brings us to the first point of contention I will acknowledge. That of the third parameter ‘id’.  If we were going to leave the default routing and simply use this value, we end up having method parameters named id when they may be used as something like ‘name’.  Here is where my team and I have made the call that if it is any sort of identifier (like name or GUID, which it usually is) that we leave the default routing and reassign the value to a more specific variable inside the method.

Note that this routing pattern is matching the URL and not any parameter values like those sent in a HttpPost.  For example the Login() method of the default AccountController takes a LoginModel and a returnUrl without changing the default route.  The LoginModel is set via POST values and often the returnUrl is added to the URL queryString like  On my team these are the preferred methods of assigning values when building with .NET MVC.

Does this mean we never add routs.  The short answer is: We never add routs.  We may make exceptions in extreme situations, but we have not come across any that need it. This quickly brings us to Areas.  Yes we use the defaults here too.


Creating an Area by the name of AreaName you are given the routing:

Default Area Route

So in this case if you had a controller named MyController like mentioned above but in the project folder Areas\AreaName\Controllers you could get to the World() action method by visiting  Because we often build our controllers for areas in external libraries we add a little salt to our area routs. *Gasp* However, we still don’t actually modify the default route.

Area Route Modified

As you can see above, we add the namespace for the area and a default controller.   This is still the only routing we need.


You still may be asking yourself, where does this rule stop? The answer is simple: When making things work with the default routs is more complicated than route clutter.  I have yet to see where this is the case and it doesn’t warrant a whole new project.  Keeping it simple is an art.

Sticking to Default Routs in ASP .NET MVC

MVC Area in an External Assembly

The majority of ASP .NET MVC sites I build I treat the site itself as a single UI.  I don’t bother breaking it down into pieces, it is an MVC after all.  Thus it already addresses separation of concerns.  But what happens when your site gets large and you want to break it into application verticals within one MVC host.  The first thing you do is break the site into Areas.  This makes it possible to keep things organized.  Now lets take it a step further, and you would like your area to be in a separate assembly.  Maybe it is shared between applications, or you just want to track the development and control deployment a bit more.

I Googled all over trying to find a good solution.  The most helpful post came from Patrick Boudreaux a couple years ago.  Working your way through Patrick’s post you see that Javascript and Css still an issue:

To make a fully self-contained portable area, static content such as css, images and javascript needs to be embedded in the assembly, and found in a special way, just as the view templates are.

Thus we will include a way to solve that issue in my own ‘sepcial way’.  Mileage may vary, so let me know in the comments.

You can find the example code on GitHub. This series will be known as The Poor Mans Modular Area for ASP .NET MVC or PMMA for short.
works on my machineWe will try to make this as simple as possible.  I feel like ‘Simple‘ is a forgotten art form in the .NET world.  It would be great to just include a reference to another MVC application and use it’s areas.  If you try that though, you will find issues with both projects trying to take the wheel to drive.  We can avoid that by simply removing redundant pieces of the hosted Area.  Also, I want to simply and clearly prove the way the application is running, so we will assemble a prof of concept project.  We will  perform a simple string assignment in the Area’s controller, print that string in a View and load a Javascript file and a CSS file that all live in the Included project.

Add Area

The Project

Starting the project created a new MVC 5 solution and called it ‘MasterUI’.  Then add a second MVC 5 project called ‘Included’.  Next add an area by right clicking the Include project and selected Add > Area and name it “TestArea”.  Then within the area right clicked on the Controller folder and added a controller named ExampleController.cs.  Then inside the Index action add the line:

ViewBag.Message = "SUCCESS!!!";

Now right click on the Index() method name and selected add View.  My view Code looks like this:

    ViewBag.Title = "Index";



@section scripts

You will notice the Styles.Render() under the default ‘Title’ assignment that refer to a package with a URL that includes the Area name.  I did this to keep convention and keep it clear where the script is coming from.  It may make sense to be even more explicit, but this will be OK for this context.  Then note it will place the message inside H2 tags to prove the controller is talking to the view.  The Scripts.Render() call will place some scripts in the ‘scripts’ layout section of the master layout.  It too refers to the Area name.

From the Included project delete Global.asax, Controllers, fonts, Models and Views. In the ‘MasterUI’ project add a reference to the ‘Included’ project.  Run MasterUI and navigate to /TestArea/Example and prove you get a 404.

The Magic

Custom ToolThe first thing you want to do is add a Visual Studio extension that allows you to precompile your MVC Razor views.  Open Extensions and Updates and search for and install Razor Generator.  Razor Generator has two pieces: a VS extension and a NuGet package.  These enable you to compile your Razor Views into the library.  Enabling this is a little manual, but the payoff is well worth the effort.  Once you install the VS Extension, manage the NuGet packages on the Included project, search for and add RazorGenerator.Mvc.  As long as we are thinking about our views, browse to TestArea\Views in Solution Explorer.  Locate the _ViewStart.cshtml and view it’s properties.  Here is where the manual part happens.  You want to type “RazorGenerator” into the ‘Custom Tool’ field.  This should cause a .cs file to be generated from your view.  There is no need to edit the .cs file, simply make your changes in the .cshtml and it will be updated for you.  Next do the same to Example\Index.cshtml.

Now it is time to setup our static content.  ASP .NET MVC has great static content handling built-in.  We will leverage this by using a custom bundle transform.  You may not consider my method to be “correct” but it seems to work.  I am open to suggestions, let me know in the comments.  The class implements IBundleTransform as follows:

public class StringResourceTransform : IBundleTransform
    private List<String> _resourceFiles = new List<String>();
    private string _contentType;

    public StringResourceTransform(List<String> resourceFiles, String contentType = "text/javascript")
        _resourceFiles = resourceFiles;
        _contentType = contentType;

    public void Process(BundleContext context, BundleResponse response)
        string result = String.Empty;

        foreach (var resource in _resourceFiles)
            using (Stream stream = Assembly.GetExecutingAssembly()
                using (StreamReader reader = new StreamReader(stream))
                    result += reader.ReadToEnd();

        response.ContentType = _contentType;
        response.Content = result;

This allows you to specify a Bundle by giving a list of Resource paths.  When the request comes in, the resources are read into a string and passed back out to via the response.  Given the above class, you would then specify your bundles in the Included project’s Bundle config similar to the this:

var scriptsBundle = new Bundle("~/Included/Scripts", 
  new StringResourceTransform(new List<String>() 
scriptsBundle.Transforms.Add(new JsMinify());

var cssBundle = new Bundle("~/Included/Content", 
  new StringResourceTransform(new List<String>()
    }, "text/css"));
cssBundle.Transforms.Add(new CssMinify());

Above first specifies a JS file that is located in the Included project under the Scipts folder by the name of test1.js.  You notice that the contentType defaults to “text/javascript” so it doesn’t need to specify this on these sorts of files.  The second set of lines do the same for a css file located in the Content folder.  The path is specified as the location within the project by setting the files to be an Embedded Resource.

First place a file in the Scripts directory by the name of test1.js.  Place the following text into it:


Then in its properties set ‘Build Action‘ to “Embedded Resource”.  Next, add a file by the name of Test.css to the Content directory and also set its Build Action to “Embedded Resource”.  Add the following text to it.

    color: red;

Now head back to the MasterUI.  There are only a couple changes that need to be made to make it aware of Included.  With all the work we did in the Bundle config, simply add the following to the end of the BundleConfig in MasterUI:


This will ensure the bundles fire.  Now you just need to make sure the routing can find the controllers.  The following line could be placed several places, but I just put mine in the Global.asax:



This bit of magic lets the routing know to look in our Included project area namespace and find controllers.  This way you don’t have to make any crazy changes to routing or build a custom anything else. Now run the application and go to /TestArea/Example.  If you see an alert that says ‘success!!” and a result like the screenshot you did it right.


As you may be thinking, you could certainly do this without having a sub-folder ‘Areas’.  The reason I did this is to make it clear we are dealing with an area, and to keep the namespace a little more organized.

If you are running in debug mode optimizations are off so you have to enable them with

BundleTable.EnableOptimizations = true;

But the problem then is that you have all your minification turned on too.  This is addressed by simply surrounding your minify transforms with #if(!DEBUG) compiler directives.


Using this method I plan on creating a multi-facet application that will be a one stop shop for custom tools where I work.  I will keep you posted on how it works out for me, feel free to do the same or ask questions in the comments.

MVC Area in an External Assembly