ASP.NET MVC 2 RC 2 & VS 2010 RC

Posted in ASP.NET MVC, Controllers, jQuery, Views by BlueCoder on 17/02/2010

Abstract: Visual Studio 2010 RC comes with MVC 2 RC 1 but if you had VS 2008 with MVC.NET 2 RC 2 installed ,as Phil Haack mentioned in his blog post, when you install VS 2010 RC you have using RC 2 version of MVC.NET automatically but without new item and project templates. In this post I’m going to show how you can manually use the latest version of templates which comes with RC 2 release of MVC.NET. I assumed you had installed VS 2008 with MVC.NET 2 RC 2 and then installed VS 2010 RC now want to update to latest version of templates. You can use this idea to install any other version of MVC.NET which comes in future.

Step 1: We are going to change the files in these locations:

Microsoft Visual Studio 10.0\Common7\IDE\ItemTemplates\CSharp\Web\MVC 2\
Microsoft Visual Studio 10.0\Common7\IDE\ItemTemplatesCache\CSharp\Web\MVC 2
Microsoft Visual Studio 10.0\Common7\IDE\ProjectTemplates\CSharp\Web\1033\
Microsoft Visual Studio 10.0\Common7\IDE\ProjectTemplatesCache\CSharp\Web\1033

So before we have chance to ruin all of our VS 2010 templates we are going to back up these files. Although we are not going to change all of files in these locations but I suggest you back up all of them so if something goes wrong you don’t miss anything.

Step 2: As I said I assume you already have VS 2008 and MVC 2 RC 2 installed on your machine. First go to “Microsoft Visual Studio 9.0\Common7\IDE\ItemTemplates\CSharp\Web\MVC 2\” and copy all the files in MVC 2 folder to the corresponding folder in VS 2010 folder (the first location in the list of step one) you should replace the current files with these new ones and you are not worry because you have already  a fresh back up of these files somewhere in your machine!

Step 3: Do the same work with files in
Microsoft Visual Studio 9.0\Common7\IDE\ItemTemplatesCache\CSharp\Web\MVC 2
Then go to “Microsoft Visual Studio 9.0\Common7\IDE\ProjectTemplates\CSharp\Web\1033\” and just copy these two files to the corresponding folder in VS 2010: and and as the previous steps you are going to replace the current ones with these new files.

Step 4: Do the same job with the same two files in
Microsoft Visual Studio 9.0\Common7\IDE\ProjectTemplatesCache\CSharp\Web\1033
So we now done with replacing files but if you now try to add a new project in your VS 2010 RC IDE you get an error says the project template tries to load from wrong assembly. But don’t worry we are one step to develop with the latest version of MVC.NET in VS 2010 RC.

Step 5: If you want to fix this issue you should dirty your hands with some manual fix of corresponding xml files in templates.
Go to “Microsoft Visual Studio 10.0\Common7\IDE\ItemTemplates\CSharp\Web\MVC 2\” and extract all zip files in the same location and delete zip files then open the unzipped files and find this section in each .vstemplate files in each folder:

“<Assembly>Microsoft.VisualStudio.Web.Mvc.2.0, Version=, Culture=neutral, PublicKeyToken=31bf3856ad364e35</Assembly>”

Then change the “Version=” to “Version=” then save each file in the same location. The last job is to zip back all the files. At this point you have the same zip files you had at first but with the changed version from 9 to 10. Do the same job with files at
Microsoft Visual Studio 10.0\Common7\IDE\ItemTemplatesCache\CSharp\Web\MVC 2” but this time you don’t need to do zip and unzip part.

Step 6: Repeat the exact job with that two file you copied to
Microsoft Visual Studio 10.0\Common7\IDE\ProjectTemplates\CSharp\Web\1033” you need to do the zip and unzip steps and the last step is to changing the assembly section in that two files at “Microsoft Visual Studio 10.0\Common7\IDE\ProjectTemplatesCache\CSharp\Web\1033” and this time without zip and unzip part. OK now we done! Open your VS 2010 RC IDE and create the new project you see the newly added project used the MVC 2 RC2 project template the more obvious changes are that the new template has jQuery 1.4.1 in its scripts folder and has the new “Optional Url parameter” in its global.asax.cs file at default route section.For more info about this new feature check out Phil Haack’s blog post.

Summary: We just updated our VS 2010 RC to use MVC.NET 2 RC 2 templates and for that we just had done some copying and pasting job and changed the assembly section in the .vstemplate files that had that section. As I said I assumed you have already VS 2008 with MVC.NET 2 RC2 installed on your machine.

Update: So after all this steps you may need do some other versional ! changes in Project Template so I uploaded the new project template (normal and  cache) so you can just download and compare it the original one to see the changes I zipped the file belong to cache folder so after copy you need to unzip and rename it as the original file. You can download the new template files here :

For copy to Microsoft Visual Studio 10.0\Common7\IDE\ProjectTemplates\CSharp\Web\1033 : here

For copy to Microsoft Visual Studio 10.0\Common7\IDE\ProjectTemplatesCache\CSharp\Web\1033: here (don’t forget to unzip and rename it as original file)

Shout it

kick it on


Setting Up IoC in ASP.NET MVC using Castle Windsor

Posted in ASP.NET MVC, Controllers, IoC by BlueCoder on 09/01/2010

Abstract: This post gathers information needed to setting up Inversion of Control (IoC) in an ASP.NET MVC application using Castle Windsor.

Introduction: In previous post I summarized how ASP.NET MVC components work together to process request from user and return result . In that post I mentioned we can customize each step to satisfy our needs so I’m going to show you how you can create a custom Controller Factory to implement IoC in your application. For more information about IoC and why we use it you can take a look at this like : .

I learned how to use Windsor to set up IoC by reading the great book of Steven Sanderson “Pro ASP.NET MVC framework”. You can read the section I used for this post here :Pro ASP.NET MVC framework by Steven Sanderson

You can get the latest version of Castle project here :

After download and install Castle Project follow these steps to set up IoC in a very simple MVC project. I use default project template & routing configuration that comes with MVC 2.

1.Right click your References folder and add reference to “Castle.Core.dll”, “Castle.MicroKernel.dll”, “Castle.Windsor.dll” files which are in  “C:\Program Files\CastleProject\Bin\net-2.0 after installing Castle.

Add Reference to Castle

2.Next we are going to create a custom Controller Factory class. Add WindsorControllerFactory.cs to the root of your application and write these lines of codes to create a controller factory which uses castle to load the required objects at run time base on configuration section which we set up later. Don’t afraid of XML & Reflection parts in the code. These snippets just say to Windsor Container that where in the Web.config file look for registering components and Reflection part just registers all controllers’ types as components. Usually when we use IoC we want to inject an object to an constructor parameter at run time, but in constructor code we just say which interface that object implements but IoC Container loads the needed object base on its configuration. The Interfaces, objects and classes which their constructor injected are components of an IoC container. In this example we register components in two places: We register controllers in the controller factory but register other types using  castle section in Web.config file. So let just right the needed Controller Factory which uses the snippets of Steven’s book that I just updated it to be compatible with MVC 2:

using System;
using System.Collections.Generic;
using System.Linq;
using System.Web;
using System.Web.Mvc;
using Castle.Windsor;
using Castle.Windsor.Configuration.Interpreters;
using Castle.Core.Resource;
using System.Reflection;
using Castle.Core;
using System.Web.Routing;

namespace Mvc2Application6
    public class WindsorControllerFactory : DefaultControllerFactory
        WindsorContainer container;
        // The constructor:
        // 1. Sets up a new IoC container
        // 2. Registers all components specified in web.config
        // 3. Registers all controller types as components
        public WindsorControllerFactory()
            // Instantiate a container, taking configuration from web.config
            container = new WindsorContainer(
            new XmlInterpreter(new ConfigResource("castle"))
            // Also register all the controller types as transient
            var controllerTypes =
                from t in Assembly.GetExecutingAssembly().GetTypes()
                                  where typeof(IController).IsAssignableFrom(t)
                                  select t;
            foreach (Type t in controllerTypes)
                    (t.FullName, t,LifestyleType.Transient);

        // Constructs the controller instance needed to service each request this part is Updated to be compatible with MVC 2
        protected override IController
            (RequestContext requestContext, Type controllerType)
            return (IController)container.Resolve(controllerType);
         * For MVC 1 use this
        protected override IController GetControllerInstance(Type controllerType)
            return (IController)container.Resolve(controllerType);

Note : This post works with Castle 1 RC 3. I recently got an email from one of readers that this not works with the latest version which is 2
so for those folks who want to work which the latest version I notify that instead of AddComponentWithLifestyle method they should use the new AddComponentLifeStyle method.

3.To ASP.NET MVC use your new controller factory add this to the application start method of your global.asax.cs file :

ControllerBuilder.Current.SetControllerFactory(new WindsorControllerFactory());

4. Next we need manipulate our Web.config file in the root of the application: Add a <castle> node directly in the configuration node: <castle><components></components></castle> we edit this shortly. In the configSections node add this:

<section name="castle" type="Castle.Windsor.Configuration.AppDomain.CastleSectionHandler,Castle.Windsor" />

5. To work with our new IoC structure you need to construct your application to use it so follow these steps to set up a simple application which use our IoC implementation:
Create an IEbookRepository interface in Model folder:

namespace Mvc2Application6.Models


public interface IEbookRepository


IEnumerable<Book> ListEbook();



As you see it’s a simple interface with a property that returns a list of Books. Book is a simple class with 3 properties:

namespace Mvc2Application6.Models


public class Book


public int ID { get; set; }

public string Name { get; set; }

public string Author { get; set; }



Create a concrete class which implements IEbookRepository interface (for simplicity we don’t touch DB and an in memory  list of books satisfies our example):

namespace Mvc2Application6.Models


public class EBookRepository : IEbookRepository


public IEnumerable<Book> ListEbook()


List<Book> books = new List<Book>();

books.Add(new Book { ID = 1, Author = "Steven Sanderson", Name = "Pro ASP.NET MVC framewok" });

books.Add(new Book { ID = 2, Author = "Stphan Waler", Name = "ASP.NET MVC framework Unleashed" });

books.Add(new Book { ID = 3, Author = "Scott Guthrie", Name = "ASP.NET MVC 1.0" });

return books;




Add a new Constructor to your Home Controller:

private IEbookRepository _repository ;

public HomeController(IEbookRepository repository)


this._repository = repository;


Now we need to tell WindsorContainer to inject IEbookRepository with an object of type EBookRepository so back to your Web.config file and edit castle node we created in step 4:



<component id="EbookRepository"







This says whenever a class has a dependency to a IEbookRepository (in our example through its constructor) IoC container should load an EBookRepository  object with whenever a web  request comes.

Then we need to register Windsor’s PerRequestLifestyle module in httpModules section :

<add name="PerRequestLifestyle" type="Castle.MicroKernel.Lifestyle.PerWebRequestLifestyleModule,Castle.MicroKernel" />

To register Windsor’s PerRequestLifestyle for IIS 7 refer to the original book “APRESS Pro ASP.NET MVC framework” or use the Google book link above.

So that’s it we set up an IoC container for our ASP.NET MVC application.

you can download sample project here.

Summary: We used Castle Windsor to Set up IoC in a very simple MVC application and for this we created a custom controller factory and added some configuration in web.config file. We also edited Application Start Method to tell MVC use our new controller factory instead of DefaultControllerFactory.

Shout it

kick it on


Posted in ASP.NET MVC, Controllers, Models, Routing, Views by BlueCoder on 03/01/2010

Abstract : In this very short article we travel through ASP.NET MVC Request Processing Pipeline from accepting the request by IIS to showing the result view by View Engine.

IIS takes each HTTP request and invokes ASP.NET which in turn invokes UrlRoutingModule which is a registered HTTP module. UrlRoutingModule starts Routing System which lives in System.Web.Routing namespace. Routing system parses the incoming Url and constructs a data structure named Request Context and searches RouteTable entries to find the matching entry and by default  invokes MvcRouteHandler passing the Request Context to it. Request Context includes parameters parsed from Url and provides access to Request and Response objects. MvcRouteHandler by default invokes DefaultControllerFactory which follows a naming convention to choose the correct controller class for a given request. Chosen controller invokes the correct action method which in turn returns an ActionResult object. and that’s it! The request is processed and a result returned. Hooray!

In case of ViewResult, action method constructs a ViewData structure and passes it to ViewResult. ViewResult is able to locate and render a particular view template using ViewData. It does so by invoking WebFormViewEngine which uses WebForms ASPX files as view templates.

The great news is every steps above can be customized: you can have your own Controller Factory and any View  Engine you comfortable with you even can create your own Route Handler to take control of routing .

summary : To be able to get the best of ASP.NET MVC you should know whats going on behind the scene and how you  can change that so in this very short post you get familiar with ASP.NET MVC Request Processing Pipeline and now have a good idea about it you also learned you can change the way MVC behaves by extending each part in your own way. hope this helps.

Further Readings:

In depth: ASP.NET MVC Pipeline

Request Handling Pipeline Poster

Custom Controller Factory in ASP.NET MVC

Custom Routing for ASP.NET MVC

Extending ASP.NET MVC : Replacing the View Engine

Extending ASP.NET MVC – Replacing the View Engine

Shout it

kick it on