World of innovations, sharing and progress together

Three steps to configuring Ninject Dependency Injection

2013-09-02T00:02:00.000+01:00

Ninject is an open source Dependency Injector for .NET.

Create MVC web application and add Ninject Dependencies to the project using nuget. Modify controller code to declare a read-only member variable of your service and modify the constructor to introduce the service instance parameter as below:

namespace DemoNinject.Controllers

{

    public class HomeController : Controller

    {

        private readonly IVehicleService _vehicleService;

        public HomeController(IVehicleService vehicleService)

        {

            _vehicleService = vehicleService;

        }

        public ActionResult Index()

        {

            ViewBag.VehicleName = _vehicleService.GetVehicleName();

            return View();

        }

    }

}

I have IVehicleService interface and want to inject _vehicleService with the implementation

IVehicleService

using Ninject;

namespace DemoNinject.ServiceLayer

{

    public class VehicleService:IVehicleService

    {

        public string GetVehicleName ()

        {

            return "Your new vehicle : BMW";

        }

    }

}
Create NinjectDependencyResolver implementing IDependencyResolver as under, which will be responsible for injecting dependencies.

using System;

using System.Collections.Generic;

using System.Linq;

using System.Web;

using System.Web.Mvc;

using Ninject;

using Ninject.Syntax;

namespace DemoNinject.Infrastructure

{

    public class NinjectDependencyResolver : IDependencyResolver

    {

        private readonly IResolutionRoot _resolutionRoot;

        public NinjectDependencyResolver(IResolutionRoot kernel)

        {

            _resolutionRoot = kernel;

        }

        public object GetService(Type serviceType)

        {

            return _resolutionRoot.TryGet(serviceType);

        }

        public IEnumerable<object> GetServices(Type serviceType)

        {

            return _resolutionRoot.GetAll(serviceType);

        }

        public void Dispose()

        {



        }

    }

}
Setup Dependency resolver in Application_Start in Global.asax as under.

public void SetupDependencyInjection()

{

        // Create Ninject DI kernel

        IKernel kernel = new StandardKernel();

        // Register services with Ninject DI Container

        kernel.Bind<IVehicleRepository>().To<VehicleRepository>();

        // Tell ASP.NET MVC to use our Ninject DI Container

        DependencyResolver.SetResolver(new NinjectDependencyResolver(kernel));

}

Three steps to configuring Castle Windsor Dependency Injection

2013-09-01T21:16:00.000+01:00

Assuming you are aware of dependency injection concept and you have used any dependency injection earlier, I would like to show how to configure CastleWindsor dependency injection in 3 easy steps.

* I am not a regular blogger so might not be able to respond your queries.

1. Add below configuration in web.config file

<?xml version="1.0" encoding="utf-8"?>

</configSections>

</components>

</castle>

</configuration>

In above configuration services contains fully qualified namespace of Interface separated by project name containing Interface. Type contains namespace and class implementing Interface.

2. Create WindsorControllerFactory to inject dependent classes

using System;

using System.Linq;

using System.Web.Mvc;

using Castle.Core;

using Castle.Windsor;

using Castle.Windsor.Configuration.Interpreters;

using Castle.Core.Resource;

using System.Reflection;

namespace DemoCastleWindor.Infrastructure

{

public class WindsorControllerFactory : DefaultControllerFactory

{

private WindsorContainer container;

public WindsorControllerFactory()

{

this.container = new WindsorContainer(

new XmlInterpreter(new ConfigResource("castle"))

);

var controllerTypes = from t in Assembly.GetExecutingAssembly().GetTypes()

where typeof(IController).IsAssignableFrom(t)

select t;

foreach (Type t in controllerTypes)

this.container.AddComponentLifeStyle(t.FullName, t, LifestyleType.Transient);

}

protected override IController GetControllerInstance(System.Web.Routing.RequestContext requestContext, Type controllerType)

{

return (IController)this.container.Resolve(controllerType);

}

3. Create WindsorControllerFactory to inject dependent classes

In global.asax, configure controller factory to create the new instance of controller.

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

Basic Links for MVC Developers

2013-01-15T20:44:00.002+00:00

jQuery
==================
Async Call
-----------

http://forums.asp.net/t/1741929.aspx/1
http://api.jquery.com/jQuery.getJSON/

Entity Framework
==================
EF 4 Tutorial
---------------

http://www.entityframeworktutorial.net/entityframework4.aspx

DB First
-----------
http://programmaticponderings.wordpress.com/2012/11/22/first-impressions-of-database-first-development-with-entity-framework-5-in-visual-studio-2012/

http://msdn.microsoft.com/en-us/data/jj206878.aspx

Calling Stored Procedures
----------------------------

http://www.devtoolshed.com/using-stored-procedures-entity-framework-scalar-return-values

Simple Unit Of Work
--------------------

http://blogs.msdn.com/b/adonet/archive/2009/06/16/using-repository-and-unit-of-work-patterns-with-entity-framework-4-0.aspx

Generic Unit Of Work
---------------------

http://blog.damianbrady.com.au/2012/07/24/a-generic-repository-and-unit-of-work-implementation-for-entity-framework/

Multiple Submit Button on MVC page

2013-01-15T20:44:00.000+00:00

Thanks to

http://blog.ashmind.com/2010/03/15/multiple-submit-buttons-with-asp-net-mvc-final-solution/

http://weblogs.asp.net/dfindley/archive/2009/05/31/asp-net-mvc-multiple-buttons-in-the-same-form.aspx

public class HttpParamActionAttribute : ActionNameSelectorAttribute {
    public override bool IsValidName(ControllerContext controllerContext, string actionName, MethodInfo methodInfo) {
        if (actionName.Equals(methodInfo.Name, StringComparison.InvariantCultureIgnoreCase))
            return true;

        if (!actionName.Equals("Action", StringComparison.InvariantCultureIgnoreCase))
            return false;
        
        var request = controllerContext.RequestContext.HttpContext.Request;
        return request[methodInfo.Name] != null;
    }
}

How to use it? Just have a form similar to this:

<% using (Html.BeginForm("Action", "Post")) { %>
  <!— …form fields… -->
  <input type="submit" name="saveDraft" value="Save Draft" />
  <input type="submit" name="publish" value="Publish" />
<% } %>

and controller with two methods

public class PostController : Controller {
    [HttpParamAction]
    [AcceptVerbs(HttpVerbs.Post)]
    public ActionResult SaveDraft(…) {
        //…
    }

    [HttpParamAction]
    [AcceptVerbs(HttpVerbs.Post)]
    public ActionResult Publish(…) {
        //…
    }
}

As you see, the attribute does not require you to specify anything at all. Also, name of the buttons are translated directly to the method names. Additionally (I haven’t tried that) these should work as normal actions as well, so you can post to any of them directly.

Async Call using Ajax

2013-01-14T12:49:00.000+00:00

using System;
using System.Collections.Generic;
using System.Linq;
using System.Web;
using System.Web.Mvc;
using PCO.Web3.Models;

namespace PCO.Web3.Controllers
{
public class HomeController : Controller
{
public ActionResult Index()
{
ViewBag.Message = "Welcome to ASP.NET MVC!";

return View();
}

public ActionResult About()
{
return View();
}

[HttpGet]
public ActionResult Employees()
{
return View();
}

[HttpGet]
public ActionResult ListEmployee(string id, Int64 age=0)
{
EmployeeViewModel model = new EmployeeViewModel();
model.Name=id ;
model.Age= age ;

return PartialView(model);
}

public JsonResult GetEmployeeList(string id, Int64 age = 0)
{
List<EmployeeViewModel> model = new List<EmployeeViewModel>();
model.Add(new EmployeeViewModel() { Name = "Puru", Age=36, Salary=5000});
model.Add(new EmployeeViewModel() { Name = "Puru1", Age = 36, Salary = 5000 });
model.Add(new EmployeeViewModel() { Name = "Puru2", Age = 39, Salary = 8000 });
model.Add(new EmployeeViewModel() { Name = "Puru3", Age = 34, Salary = 6000 });

return Json(model, JsonRequestBehavior.AllowGet);
}
}
}

HTML

@model PCO.Web3.Models.EmployeeViewModel

ViewBag.Title = "Employees";

}

$(document).ready(function () {

$("#btnSearch").click(function () {

//GetList();

//GetListUsingAjax();

GetJsonListUsingAjax();

});

function GetListUsingAjax() {

var strName = $("#Name").val();

var targetUrl = "/home/ListEmployee/" + strName;

$.ajax({

url: targetUrl,

dataType: 'text',

data: { id: strName, age: $("#Age").val() },

success: function (bsHTML) {

alert(123456);

$("#listContainer").html(bsHTML);

error: function (req, status, ex) {

alert(2);

}

});

}

function GetJsonListUsingAjax() {

var strName = $("#Name").val();

var targetUrl = "/home/GetEmployeeList/" + strName;

$.ajax({

url: targetUrl,

dataType: 'json',

data: { id: strName, age: $("#Age").val() },

success: function (bsHTML) {

alert(bsHTML[1].Name);

$("#listContainer").html(bsHTML.name[1]);

error: function (req, status, ex) {

alert(ex);

}

});

}

function GetList() {

var strName = $("#Name").val();

var url = "/home/ListEmployee/" + strName;

$("#listContainer").load(url);

$("#partialHeader").load(url);

return false;

}

</script>

<h2>Employees</h2>

@using (Html.BeginForm())

{

@Html.LabelFor(x => x.Name)

@Html.TextBoxFor(x => x.Name)

@Html.LabelFor(x => x.Age)

@Html.TextBoxFor(x => x.Age)

//@Html.ActionLink("Search", "ListEmployee", new { id = 1})

</div>

}

Dpendency Resolver Using Ninject

using System;
using System.Collections.Generic;
using System.Linq;
using System.Web;
using System.Web.Mvc;
using Ninject;
using Ninject.Syntax;

namespace BasicMVCDemo.Infrastructure
{
public class NinjactDependencyResolver: IDependencyResolver
{

private readonly IResolutionRoot _resolutionRoot;

public NinjactDependencyResolver(IResolutionRoot kernel)
{
_resolutionRoot = kernel;
}

public object GetService(Type serviceType)
{
return _resolutionRoot.TryGet(serviceType);
}

public IEnumerable<object> GetServices(Type serviceType)
{
return _resolutionRoot.GetAll(serviceType);
}
}
}

Setting in Global.asax

public void SetupDependencyInjection()
{
// Create Ninject DI kernel
IKernel kernel = new StandardKernel();

// Register services with Ninject DI Container
kernel.Bind<DbContext>().To<DBFirstDemoEntities>();
kernel.Bind<ICustomerRepository>().To<CustomerRepository>();

// Tell ASP.NET MVC 3 to use our Ninject DI Container
DependencyResolver.SetResolver(new NinjactDependencyResolver(kernel));
}

DB Connection

<add name="DBFirstDemoEntities" connectionString="Server=(local);Database=DBFirstDemo;Trusted_Connection=True;" providerName="System.Data.SqlClient" />

OnModelCreating

protected override void OnModelCreating(DbModelBuilder modelBuilder)
{
//throw new UnintentionalCodeFirstException();
modelBuilder.Conventions.Remove<PluralizingTableNameConvention>();

modelBuilder.Configurations.Add(new ArticleConfiguration());

}

DbConfiguration

public class ArticleConfiguration : EntityTypeConfiguration<Article>
{
   public ArticleConfiguration()
   {
      this.HasMany(x=>x.RelatedArticles)
         .WithMany(x=>x.OtherRelatedArticles)
         .Map(x=>x.ToTable("RelatedArticles"));
   }
}

MVC3 Razor - Basics

2012-01-17T22:14:00.000+00:00

Creating Dropdownbox

Step 1: Create Data provider so that we can bind with drop down list

using System;

using System.Collections.Generic;

using System.Linq;

using System.Text;

using System.Web.Mvc;

namespace WebRepository

{

public class UserProvider: IUserProvider

{

public List<SelectListItem> GetRoles()

{

List<SelectListItem> roles = new List<SelectListItem>();

roles.Add(new SelectListItem() { Selected = false, Text = "Admin", Value = "0" });

roles.Add(new SelectListItem() { Selected = true, Text = "Standard User", Value = "1" });

roles.Add(new SelectListItem() { Selected = false, Text = "Super User", Value = "2" });

return roles;

}

Step 2: Create action and fetch the data from data provider, bind with model and pass model to view.

public ActionResult Index()

{

WebUser webUser = new WebUser();

webUser.Name = "My Name";

webUser.Role = new UserProvider().GetRoles();

return View(webUser);

}

Step 3:Pass model data to select list and bind with dropdown.

@Html.DropDownList("UserRolesId", Model.Role)

Displaying Selected Value using JQuery

$('#UserRolesId').change(function () {

$("option:selected").each(function () {

alert($(this).text());

});

</script>

Attaches a change event to the select that gets the text for each selected option and writes them in the div. It then triggers the event for the initial text draw.

Source: http://api.jquery.com/change/

<!DOCTYPE html>
<html>
<head>
<style>

div { color:red; }
</style>
<script src="http://code.jquery.com/jquery-latest.js"></script>
</head>
<body>
<select name="sweets" multiple="multiple">
<option>Chocolate</option>
<option selected="selected">Candy</option>

<option>Taffy</option>
<option selected="selected">Caramel</option>
<option>Fudge</option>
<option>Cookie</option>

</select>
<div></div>
<script>
$("select").change(function () {
var str = "";
$("select option:selected").each(function () {
str += $(this).text() + " ";
});
$("div").text(str);
})
.change();
</script>

</body>
</html>

jQuery
==================
Async Call
-----------

http://forums.asp.net/t/1741929.aspx/1
http://api.jquery.com/jQuery.getJSON/

Entity Framework
==================

DB First
-----------

http://msdn.microsoft.com/en-us/data/jj206878.aspx

Simple Unit Of Work
--------------------

http://blogs.msdn.com/b/adonet/archive/2009/06/16/using-repository-and-unit-of-work-patterns-with-entity-framework-4-0.aspx

Generic Unit Of Work
---------------------

http://blog.damianbrady.com.au/2012/07/24/a-generic-repository-and-unit-of-work-implementation-for-entity-framework/

Working with MSBuild - <ItemGroup>

2011-07-08T00:34:00.004+01:00

While working on MSBuild and doing some RND, I found that if we utilize <ItemGroup> properly we can achieve lot's things very easily and keep the build file very clean. I am not going in details but still trying to highlight how we can use it in various scenarios. You can utilize it then according to your requirement.

I assume you have created build file. If not then create build.xml (you can use naming convention as per your requirement). In my case I have created it "build.xml" at "C:\Projects\MSBuildDemo\", which contains some basic code as under.

<?xml version="1.0" encoding="utf-8"?>

</Department>

</Department>

<Name>Jacob</Name>

</Department>

<Name>Jacob</Name>

</Department>

</ItemGroup>

</Project>

Note: Our example will be based on the </ItemGroup> which is added in it.

Scenario 1: I want list of all departments in ItemGroup.

Add target as under in build file which will display list of all departments.

</Target>

If you will open Visual Studio Command Prompt and execute the target "DepartmentsInItemGroup", you will see the result as under.

Notice here you will get "HR" department twice.

Scenario 2: I want list of unique departments in ItemGroup.

Same as above create target as below and execute it.

</Target>

You will get the result as under having unique department.

Scenario 3: If you will see the <ItemGroup> above there are two person with the same name "Jacob". One is in Finance and other is in HR department. I want unique names from the <ItemGroup>.

Same as above create target as below and execute it.

</Target>

You will see the result as under.

If you will notice you will see names "Paul", "Ewen", "Jacob". There are two Jacob's but only one is displayed.

Scenario 4: I want Department based employee names list from the <ItemGroup>.

Create target as below and execute it.

    <Message Text="***** List of Department Based Employee Name *****"/>

    <Message Text="%(Department.Identity): @(Department->'%(Name)')" />

</Target>

You will see the result as under.

Scenario 5: I want to display same departments list for multiple authorized branches (Cross Join ItemGroups).

Create a property containing Authorized branches as under.

<AuthorizedBranches>Branch1;Branch2;Branch3</AuthorizedBranches>

</PropertyGroup>

Create Target as under

<Target Name="DepartmentsInItemGroup">

    <Message Text="***** Display department in ItemGroup  *****"/>

       <ItemGroup>

              <AuthorizedBranch Include="$(AuthorizedBranches)"/>

       </ItemGroup>

    <Message Text="%(AuthorizedBranch.Identity)" />

       <Message Text=" "/>

       <CreateItem Include="@(Department)" AdditionalMetadata="BranchName=%(AuthorizedBranch.Identity)">

              <Output TaskParameter="Include" ItemName="BranchDetails"/>

       </CreateItem>

       <Message Text="Department : %(BranchDetails.Identity); AuthorsizedBranchName : %(BranchDetails.BranchName)" />

       <Message Text=" "/>

       <Message Text="Department : %(BranchDetails.Identity)"/>

  </Target>

You will see the Output as under.

Hope this will help to get started with <ItemGroup>. If you notice we have used different @, % with department itemgorup. So what that stands for?

@ is for an item in collection, which is a group of files with attached metadata under a name.

% denote an access to a metadata of an item.

There are wellknown metadatas (like RecursiveDir, see the definition in msdn) automatically attached to an item, or you can attach your own metadata when you define your items.

$ denotes access to a property.

To get better understanding or looking to make career in configuration management refer books like Inside the Microsoft Build Engine: Using MSBuild and Team Foundation Build and Continuous Delivery: Reliable Software Releases through Build, Test, and Deployment Automation (Addison-Wesley Signature Series (Fowler))

Installing ASP.Net web application using WIX (Windows Installer XML)

2011-06-15T22:26:00.002+01:00

While doing day to day activities in office so many times I have been helped by blogs created by developers community. There are lot to learn and lot to serve. I though why not to give something in return to our community.

So one thing which I learned by following blogs is WIX Installer. I tried make it a bit generic so that it could be used as a template to create new "Web Application Installer". I am going to put that in first blog of my life.

Here we go.....

Topics covered

Introduction
Creating new WIX Setup project.
Adding IIS Configuration settings (Virtual directory, setting application properties, Application pool)
Harvesting web application files.
Transforming file source according to required folder structure.

Introduction

The Windows Installer XML (WiX) is a toolset that builds Windows installation packages from XML source code. The toolset supports a command line environment that developers may integrate into their build processes to build MSI and MSM setup packages. (I am not a regular blogger but I may cover integrating with MSBuild and uninstallation and installation or web application created by WIX.)

To gain more knowledge you can google or buy

Creating new WIX Setup project

I am assuming that you already have WiX v3.5 installed on your machine. If not you can find it at http://wix.codeplex.com/releases/view/60102

Before creating Wix installer let's create a simple web application which we want to install using WIX.

Open visual studio and create new web application. (Assuming you know how to create new web application.)

In my case I have created a web application called "DefaultWebApp". If you see my solution explorer you can find the folder structure as under.

2. Build you web application and make sure that there is no compilation error.

3. Now we can create a new WIX installer for web application installation. I am going to add installer project in same solution. Right click on solution and click on Add -> New Project...

4. Select "Windows Installer XML" from Installed Templates in left panel of the dialog box. Choose "Setup Project" from the list of project types in right panel. Provide the appropriate name and the location of the project. Ideally I keep installer project name same as web project and post fix ".Install".

5. Click on Ok button. You will be able to see the new WIX project in your solution explorer as under.

6. You can build the project and can see the msi file generated in bin directory.

The msi file generated previously is of no use till we configure it to create virtual directory, application pool and harvest the file to be installed.

Before doing that let do some configuration settings so that if you want to build it using MSBuild you can provide product version, install location, web site name, port number, application pool name, source directory etc in run time.

7. Right click on the installer project and select option "Unload Project"

8. Once project is unloaded from the solution, again right click on it and choose "Edit<YourProjectName>.wixproj"

Once you click the option mentioned above you will be able to see the project file in edit mode as under. And we are interested in the highlighted part below.

9. Let's add some of the project properties as under which can be used by MSBuild to pass the value as parameter.

<Project ToolsVersion="4.0" DefaultTargets="Build" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">

..... (Existing properties)

<InstallLocation Condition=" '$(InstallLocation)' == '' ">WebHome</InstallLocation>

<WebSiteName Condition=" '$(WebSiteName)' == '' ">DefaultWebApp</WebSiteName>

<WebSitePoolName Condition=" '$(WebSitePoolName)' == '' ">$(WebSiteName)</WebSitePoolName>

<SourceDir Condition=" '$(SourceDir)' == '' ">C:\Projects\WixDemo\DefaultWebApp\</SourceDir>

</PropertyGroup>

<OutputPath>bin\$(Configuration)\</OutputPath>

<IntermediateOutputPath>obj\$(Configuration)\</IntermediateOutputPath> <DefineConstants>Debug;ProductVersion=$(VersionFull);InstallLocation=$(InstallLocation);WebSiteName=$(WebSiteName);WebSitePortNumber=$(WebSitePortNumber);WebSitePoolName=$(WebSitePoolName);SourceDir=$(SourceDir)</DefineConstants>

</PropertyGroup>

<OutputPath>bin\$(Configuration)\</OutputPath>

<IntermediateOutputPath>obj\$(Configuration)\</IntermediateOutputPath>

<DefineConstants>ProductVersion=$(VersionFull);InstallLocation=$(InstallLocation);WebSiteName=$(WebSiteName);WebSitePortNumber=$(WebSitePortNumber);WebSitePoolName=$(WebSitePoolName);SourceDir=$(SourceDir)</DefineConstants>

</PropertyGroup>

..... (Existing properties)

</Project>

Above we have set the additional properties which can be passed at run time as parameter. If omitted it will use the default value set above.

10. Save the file and reload the project again.
11. Now let's change the hard coded (Default) value in our installer projects "Product.wxs" file to use the value passed in parameter set earlier in project file. After making changes your Product.wxs file should look like below. (Make sure you don't change the product Id and UpgradeCode)

<?xml version="1.0" encoding="UTF-8"?>

<Product Id="Your GUID Value"

Name="$(var.WebSiteName) $(var.ProductVersion)"

Language="1033"

Version="$(var.ProductVersion)"

Manufacturer="Demo application Manufaturer"

UpgradeCode="Your GUID Value">

<RegistrySearch Id="FrameworkRootDir"

Root="HKLM"

Key="SOFTWARE\Microsoft\.NETFramework"

Type="directory" Name="InstallRoot" />

</Property>

</Directory>

</Feature>

</Product>

</Wix>

NOTE: Don't forget to add your GUID value in project Id (Curly bracket not required).

We are now ready to build our installer package using MSBuild and pass command line parameters like product version, install location, web site name, port number, application pool name, source directory etc.

Adding IIS Configuration settings

For IIS configuration we need to add required references to the installer project as below.

2. Add new item in installer project. From the dialog box select "Wix File" and give it appropriate name. In my case I am giving name as "IISConfiguration".

3. Add code in file as under.

<?xml version="1.0" encoding="UTF-8"?>

<Wix xmlns="http://schemas.microsoft.com/wix/2006/wi"

xmlns:iis="http://schemas.microsoft.com/wix/IIsExtension"

xmlns:util="http://schemas.microsoft.com/wix/UtilExtension">

</ComponentGroup>

<iis:WebAppPool Id="AppPool"

Name="$(var.WebSitePoolName)"

Identity="networkService"

IdleTimeout="20"

QueueLimit="1000"

MaxWorkerProcesses="1">

<iis:RecycleTime Value="02:00"/>

</iis:WebAppPool>

</Component>

<iis:WebVirtualDir Id="Application_VirtualDir"

Alias="$(var.WebSiteName)"

Directory="SiteDirectory"

WebSite="DefaultWebSite">

<iis:WebApplication Id="$(var.WebSiteName)"

Name="$(var.WebSiteName)"

Isolation="medium"

WebAppPool="AppPool"

AllowSessions ="yes"

SessionTimeout="20"

ParentPaths="no"

Buffer="yes"

ScriptTimeout="90"

ClientDebugging="no"

ServerDebugging="no">

<iis:WebApplicationExtension Extension="asax" CheckPath="yes" Script="yes" Executable="[FRAMEWORKROOT]v4.0.30319\aspnet_isapi.dll" Verbs="GET,HEAD,POST" />

<iis:WebApplicationExtension Extension="ascx" CheckPath="yes" Script="yes" Executable="[FRAMEWORKROOT]v4.0.30319\aspnet_isapi.dll" Verbs="GET,HEAD,POST" />

<iis:WebApplicationExtension Extension="asp" CheckPath="yes" Script="yes" Executable="$(env.SystemRoot)\System32\inetsrv\asp.dll" Verbs="GET,HEAD,POST" />

<iis:WebApplicationExtension Extension="aspx" CheckPath="no" Script="yes" Executable="[FRAMEWORKROOT]v4.0.30319\aspnet_isapi.dll" Verbs="GET,HEAD,POST" />

<iis:WebApplicationExtension Extension="axd" CheckPath="no" Script="yes" Executable="[FRAMEWORKROOT]v4.0.30319\aspnet_isapi.dll" Verbs="GET,HEAD,POST" />

<iis:WebApplicationExtension Extension="browser" CheckPath="yes" Script="yes" Executable="[FRAMEWORKROOT]v4.0.30319\aspnet_isapi.dll" Verbs="GET,HEAD,POST" />

<iis:WebApplicationExtension Extension="config" CheckPath="yes" Script="yes" Executable="[FRAMEWORKROOT]v4.0.30319\aspnet_isapi.dll" Verbs="GET,HEAD,POST" />

<iis:WebApplicationExtension Extension="cs" CheckPath="yes" Script="yes" Executable="[FRAMEWORKROOT]v4.0.30319\aspnet_isapi.dll" Verbs="GET,HEAD,POST" />

<iis:WebApplicationExtension Extension="csproj" CheckPath="yes" Script="yes" Executable="[FRAMEWORKROOT]v4.0.30319\aspnet_isapi.dll" Verbs="GET,HEAD,POST" />

<iis:WebApplicationExtension Extension="exclude" CheckPath="yes" Script="yes" Executable="[FRAMEWORKROOT]v4.0.30319\aspnet_isapi.dll" Verbs="GET,HEAD,POST" />

<iis:WebApplicationExtension Extension="master" CheckPath="yes" Script="yes" Executable="[FRAMEWORKROOT]v4.0.30319\aspnet_isapi.dll" Verbs="GET,HEAD,POST" />

<iis:WebApplicationExtension Extension="resources" CheckPath="yes" Script="yes" Executable="[FRAMEWORKROOT]v4.0.30319\aspnet_isapi.dll" Verbs="GET,HEAD,POST" />

<iis:WebApplicationExtension Extension="resx" CheckPath="yes" Script="yes" Executable="[FRAMEWORKROOT]v4.0.30319\aspnet_isapi.dll" Verbs="GET,HEAD,POST" />

<iis:WebApplicationExtension Extension="skin" CheckPath="yes" Script="yes" Executable="[FRAMEWORKROOT]v4.0.30319\aspnet_isapi.dll" Verbs="GET,HEAD,POST" />

<iis:WebApplicationExtension Extension="svc" CheckPath="no" Script="yes" Executable="[FRAMEWORKROOT]v4.0.30319\aspnet_isapi.dll" Verbs="GET,HEAD,POST" />

<iis:WebApplicationExtension Extension="vb" CheckPath="yes" Script="yes" Executable="[FRAMEWORKROOT]v4.0.30319\aspnet_isapi.dll" Verbs="GET,HEAD,POST" />

<iis:WebApplicationExtension Extension="vbproj" CheckPath="yes" Script="yes" Executable="[FRAMEWORKROOT]v4.0.30319\aspnet_isapi.dll" Verbs="GET,HEAD,POST" />

<iis:WebApplicationExtension Extension="vsdisco" CheckPath="no" Script="yes" Executable="[FRAMEWORKROOT]v4.0.30319\aspnet_isapi.dll" Verbs="GET,HEAD,POST" />

</iis:WebApplication>

<iis:WebDirProperties Id="Application_Properties"

AnonymousAccess="yes"

WindowsAuthentication="no"

DefaultDocuments="Default.aspx"

Read="yes"

LogVisits="yes"

Index="yes"

Execute ="yes"

Script="yes" />

</iis:WebVirtualDir>

</Component>

</DirectoryRef>

</Fragment>

</Wix>

NOTE: Don't forget to add your GUID value in above code.

4. Save the file.
5. Open "Product.wxs" file and modify ComponentGroupRef as below in "Feature" element.

</Feature>

6. Build your project. It should be build successfully.

Harvesting web application files

When we install our web application it should not just create virtual directory and configure IIS but also should copy the required files and libraries in appropriate folder. For example in our case apart from creating virtual directory and configuring IIS installer it should also install web application folders (Account, Scripts, Styles etc.) and files (About.aspx, Default.aspx, Global.asax, Site.Master, Web.config etc.) along with the bin folder containing required libraries.

So in that case we have to specify which folder and files to be installed and the hierarchy of the folders. Our application can contain number of folders and files which is not require to be installed by the installer like .pdb, .cs files and folders like "obj", "Debug". So we have to add the require files and at the same time filter out the unwanted files and folders. To achieve this we can transform the source in the required structure and filter out the unwanted files.

1. Create file "TransformDirectoryToWix.xslt" in our installer project.
2. Add below code in "TransformDirectoryToWix.xslt" file.

<?xml version="1.0" encoding="utf-8"?>

<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"

xmlns:msxsl="urn:schemas-microsoft-com:xslt"

xmlns:wix="http://schemas.microsoft.com/wix/2006/wi"

version="1.0"

exclude-result-prefixes="msxsl wix">

<xsl:output method="xml" indent="yes" encoding="utf-8"/>

<xsl:template match="@* | node()">

<xsl:apply-templates />

</xsl:template>

<xsl:template match ="wix:Fragment[wix:DirectoryRef]">

<xsl:apply-templates />

</DirectoryRef>

</Include>

</xsl:template>

<xsl:template match="wix:Directory[wix:Directory and (not(@Name='obj') and not(@Name='logs') and not(@Name='.svn') and not(@Name='Debug') and not(@Name='Release')) or (@Name='bin') or (@Name='css')]">

<xsl:apply-templates />

</Directory>

</xsl:template>

<xsl:template match="wix:Component[wix:File[(not(contains(@Source,'.pdb') or contains(@Source,'.cs') or contains(@Source,'.css.svn') or contains(@Source,'.svn') or contains(@Source,'\obj\'))) or (contains(@Source,'.css') and not(contains(@Source,'.svn')))]]">

</Component>

</xsl:template>

</xsl:stylesheet>

3. Add "Files.wxs" (you can choose file name as per your naming convention) where we will put the transformed output. (Hierarchical representation of components to be installed)
4. Right click on the installer project, choose properties, select Build Events tab as shown in screen below and enter command
"$(WixToolPath)heat.exe" dir "C:\Projects\WixDemo\DefaultWebApp" -var var.SourceDir -gg -sfrag -scom -sreg -suid -t "$(ProjectDir)TransformDirectoryToWix.xslt" -out "$(ProjectDir)Files.wxs in pre-build event text area.

Note: Quotation mark at the end is not required.

5. Open "Product.wxs" file add include tag as under to link "Files.wxs", below "Feature" element.

<?include Files.wxs?>

6. Finally your "Product.wxs" file should look as under.

<?xml version="1.0" encoding="UTF-8"?>

<Product Id="8ee0accb-4a08-4307-801e-7b8c74388097"

Name="$(var.WebSiteName) $(var.ProductVersion)"

Language="1033"

Version="$(var.ProductVersion)"

Manufacturer="Demo application Manufaturer"

UpgradeCode="18c68f5d-ed41-4681-a3c7-1377a8f58c39">

<RegistrySearch Id="FrameworkRootDir"

Root="HKLM"

Key="SOFTWARE\Microsoft\.NETFramework"

Type="directory" Name="InstallRoot" />

</Property>

</Directory>

</Feature>

<?include Files.wxs?>

</Product>

</Wix>

7. Build your installer project. It will harvest your source project folder and put the required components in "Files.wxs". We are linking "Files.wxs" in our "Product.wxs", so all the components present in "Files.wxs" will be installed when you will run the installer.

8. Run the installer and check the created virtual directory and the folders and files installed by installer.

Hope this post will give you basic understanding of installing ASP.Net application using WIX.