mvcextensions Wiki Rss Feed

Updated Wiki: Home

hazzik — Tue, 21 Aug 2012 13:27:59 GMT

THE PROJECT HAS BEEN MOVED TO GITHUB: http://mvcextensions.github.com

Welcome to ASP.NET MVC Extensions

Project Description

ASP.NET MVC Extensions (aka System.Web.Mvc.Extensibility) is developed on top of ASP.NET MVC extensibility point, which allows your IoC Container to rule everywhere.

Features:

Container Neutral: Stop referencing you IoC Container in your application code, let your application independent from the underlying container, yet utilizing the complete power.
Multiple Adapter: Packed with all the Popular IoC Containers adapter which includes Autofac, Ninject, StructureMap, Unity and Windsor.
Bootstrapping: Stop writing the same bootstrapping code over and over again, let the extensions to handle your Controller/Controller Factory/Model Binders/View Engines/Action Filters/Custom Dependencies etc registrations.
PerRequestTask: Act as a HttpModule to perform custom logic in the start and end of the request without registering in web.config.
Model Binder: Inject custom dependencies in your Model Binder with constructor injection.
Action Filter Fluent Registration: Fluently register your action filters which supports constructor injection of your custom dependencies.
ModelMetadata Fluent Configuration: Supports Composite ModelMetadata provider, which fallback to default DataAnnotationsModelMetadataProvider, supports configuring your model with fluent syntax like EF Code First or Fluent NHibernate.
Various ActionResults: Contains common action result which includes XmlResult, ExtendedJsonResult (which supports JsonConverters), Adaptive PRG (PostRedirectGet) results.
Common Route Constraints: Contains common route constraints like Range, Positive Int/Long, Guid, Enum, RegEx etc.
Various other Utility methods and helpers.

OSS projects which are using Mvc Extensions

Nightly Builds : CodeBetter TeamCity

NuGet Packages: MvcExtensions Core, requires one of following IoC adapter:

Latest Updates
Click here to view the RSS feed.

Follow us in Twitter

Updated Wiki: Home

hazzik — Sat, 14 Apr 2012 19:10:08 GMT

WE ARE MOVING TO GITHUB: http://mvcextensions.github.com

Welcome to ASP.NET MVC Extensions

Project Description

ASP.NET MVC Extensions (aka System.Web.Mvc.Extensibility) is developed on top of ASP.NET MVC extensibility point, which allows your IoC Container to rule everywhere.

Features:

Container Neutral: Stop referencing you IoC Container in your application code, let your application independent from the underlying container, yet utilizing the complete power.
Multiple Adapter: Packed with all the Popular IoC Containers adapter which includes Autofac, Ninject, StructureMap, Unity and Windsor.
Bootstrapping: Stop writing the same bootstrapping code over and over again, let the extensions to handle your Controller/Controller Factory/Model Binders/View Engines/Action Filters/Custom Dependencies etc registrations.
PerRequestTask: Act as a HttpModule to perform custom logic in the start and end of the request without registering in web.config.
Model Binder: Inject custom dependencies in your Model Binder with constructor injection.
Action Filter Fluent Registration: Fluently register your action filters which supports constructor injection of your custom dependencies.
ModelMetadata Fluent Configuration: Supports Composite ModelMetadata provider, which fallback to default DataAnnotationsModelMetadataProvider, supports configuring your model with fluent syntax like EF Code First or Fluent NHibernate.
Various ActionResults: Contains common action result which includes XmlResult, ExtendedJsonResult (which supports JsonConverters), Adaptive PRG (PostRedirectGet) results.
Common Route Constraints: Contains common route constraints like Range, Positive Int/Long, Guid, Enum, RegEx etc.
Various other Utility methods and helpers.

OSS projects which are using Mvc Extensions

Nightly Builds : CodeBetter TeamCity

NuGet Packages: MvcExtensions Core, requires one of following IoC adapter:

Latest Updates
Click here to view the RSS feed.

Follow us in Twitter

Updated Wiki: Home

hazzik — Sun, 23 Oct 2011 18:40:53 GMT

Welcome to ASP.NET MVC Extensions

Project Description

ASP.NET MVC Extensions (aka System.Web.Mvc.Extensibility) is developed on top of ASP.NET MVC extensibility point, which allows your IoC Container to rule everywhere.

Features:

Container Neutral: Stop referencing you IoC Container in your application code, let your application independent from the underlying container, yet utilizing the complete power.
Multiple Adapter: Packed with all the Popular IoC Containers adapter which includes Autofac, Ninject, StructureMap, Unity and Windsor.
Bootstrapping: Stop writing the same bootstrapping code over and over again, let the extensions to handle your Controller/Controller Factory/Model Binders/View Engines/Action Filters/Custom Dependencies etc registrations.
PerRequestTask: Act as a HttpModule to perform custom logic in the start and end of the request without registering in web.config.
Model Binder: Inject custom dependencies in your Model Binder with constructor injection.
Action Filter Fluent Registration: Fluently register your action filters which supports constructor injection of your custom dependencies.
ModelMetadata Fluent Configuration: Supports Composite ModelMetadata provider, which fallback to default DataAnnotationsModelMetadataProvider, supports configuring your model with fluent syntax like EF Code First or Fluent NHibernate.
Various ActionResults: Contains common action result which includes XmlResult, ExtendedJsonResult (which supports JsonConverters), Adaptive PRG (PostRedirectGet) results.
Common Route Constraints: Contains common route constraints like Range, Positive Int/Long, Guid, Enum, RegEx etc.
Various other Utility methods and helpers.

OSS projects which are using Mvc Extensions

Nightly Builds : CodeBetter TeamCity

NuGet Packages: MvcExtensions Core, requires one of following IoC adapter:

Latest Updates
Click here to view the RSS feed.

Follow us in Twitter

Updated Wiki: Home

hazzik — Sun, 23 Oct 2011 18:39:04 GMT

Welcome to ASP.NET MVC Extensions

Project Description

ASP.NET MVC Extensions (aka System.Web.Mvc.Extensibility) is developed on top of ASP.NET MVC extensibility point, which allows your IoC Container to rule everywhere.

Features:

Container Neutral: Stop referencing you IoC Container in your application code, let your application independent from the underlying container, yet utilizing the complete power.
Multiple Adapter: Packed with all the Popular IoC Containers adapter which includes Autofac, Ninject, StructureMap, Unity and Windsor.
Bootstrapping: Stop writing the same bootstrapping code over and over again, let the extensions to handle your Controller/Controller Factory/Model Binders/View Engines/Action Filters/Custom Dependencies etc registrations.
PerRequestTask: Act as a HttpModule to perform custom logic in the start and end of the request without registering in web.config.
Model Binder: Inject custom dependencies in your Model Binder with constructor injection.
Action Filter Fluent Registration: Fluently register your action filters which supports constructor injection of your custom dependencies.
ModelMetadata Fluent Configuration: Supports Composite ModelMetadata provider, which fallback to default DataAnnotationsModelMetadataProvider, supports configuring your model with fluent syntax like EF Code First or Fluent NHibernate.
Various ActionResults: Contains common action result which includes XmlResult, ExtendedJsonResult (which supports JsonConverters), Adaptive PRG (PostRedirectGet) results.
Common Route Constraints: Contains common route constraints like Range, Positive Int/Long, Guid, Enum, RegEx etc.
Various other Utility methods and helpers.

OSS project are using it

Nightly Builds : CodeBetter TeamCity

NuGet Packages: MvcExtensions Core, requires one of following IoC adapter:

Latest Updates
Click here to view the RSS feed.

Follow us in Twitter

Updated Wiki: Home

hazzik — Thu, 20 Oct 2011 17:50:41 GMT

Welcome to ASP.NET MVC Extensions

Project Description

ASP.NET MVC Extensions (aka System.Web.Mvc.Extensibility) is developed on top of ASP.NET MVC extensibility point, which allows your IoC Container to rule everywhere.

Features:

Container Neutral: Stop referencing you IoC Container in your application code, let your application independent from the underlying container, yet utilizing the complete power.
Multiple Adapter: Packed with all the Popular IoC Containers adapter which includes Autofac, Ninject, StructureMap, Unity and Windsor.
Bootstrapping: Stop writing the same bootstrapping code over and over again, let the extensions to handle your Controller/Controller Factory/Model Binders/View Engines/Action Filters/Custom Dependencies etc registrations.
PerRequestTask: Act as a HttpModule to perform custom logic in the start and end of the request without registering in web.config.
Model Binder: Inject custom dependencies in your Model Binder with constructor injection.
Action Filter Fluent Registration: Fluently register your action filters which supports constructor injection of your custom dependencies.
ModelMetadata Fluent Configuration: Supports Composite ModelMetadata provider, which fallback to default DataAnnotationsModelMetadataProvider, supports configuring your model with fluent syntax like EF Code First or Fluent NHibernate.
Various ActionResults: Contains common action result which includes XmlResult, ExtendedJsonResult (which supports JsonConverters), Adaptive PRG (PostRedirectGet) results.
Common Route Constraints: Contains common route constraints like Range, Positive Int/Long, Guid, Enum, RegEx etc.
Various other Utility methods and helpers.

If you want to see this extension in action, try Shrinkr

Nightly Builds : CodeBetter TeamCity

NuGet Packages: MvcExtensions Core, requires one of following IoC adapter:

Latest Updates
Click here to view the RSS feed.

Follow us in Twitter

Updated Wiki: Builtin BootstrapperTasks

hazzik — Sat, 20 Aug 2011 06:26:03 GMT

List of builtin BootstrapperTasks:

RegisterAreas is used to register available areas.
RegisterControllerActivator is used to register the default IControllerActivator.
RegisterControllers is used to register available Controllers. Depends on RegisterControllerActivator task.
RegisterFilterProviders is used to register available IFilterProviders.
RegisterFilters is used to register available IMvcFilters.
RegisterModelBinderProvider is used to register the default IModelBinderProvider
RegisterModelBinders is used to register available IModelBinders. Depends on RegisterModelBinderProvider
RegisterModelMetadata is used to register the default ModelMetadataProvider
RegisterValueProviderFactories is used to register available ValueProviderFactories
RegisterViewEngines is used to register available IViewEngines
RegisterViewPageActivator is used to register the default IViewPageActivator
RegisterViews is used to register available IViews

Updated Wiki: Builtin BootstrapperTasks

hazzik — Sat, 20 Aug 2011 06:16:27 GMT

List of builtin BootstrapperTasks:

RegisterAreas is used to register available areas.
RegisterControllerActivator is used to register the default IControllerActivator.
RegisterControllers is used to register available Controllers. Depends on RegisterControllerActivator task.
RegisterFilterProviders is used to register available IFilterProviders.
RegisterFilters is used to register available IMvcFilters.

Updated Wiki: Documentation

hazzik — Sat, 20 Aug 2011 06:11:30 GMT

Topics

Working with IoC Containers (coming up)
- Ninject
- StrucutreMap
- Unity
- Windsor
Working with metadata configurations
BootstrapperTask: builtin tasks, creating own BootstrapperTask
Creating PerRequestTask (coming up)
Working with Action Filters (coming up)
Working with Model Binders (coming up)
Working with Action Results (coming up)

Updated Wiki: Documentation

hazzik — Sat, 20 Aug 2011 06:09:50 GMT

Topics

Working with IoC Containers (coming up)
- Ninject
- StrucutreMap
- Unity
- Windsor
Working with metadata configurations
BootstrapperTask: builtin tasks, creating own BootstrapperTask
Creating PerRequestTask (coming up)
Working with Action Filters (coming up)
Working with Model Binders (coming up)
Working with Action Results (coming up)

Updated Wiki: Creating BootstrapperTask

hazzik — Fri, 19 Aug 2011 22:41:12 GMT

By design all bootstrapper code in MvcExtensions should be placed into BootstrapperTasks. Here a small example of how to write your own task.

Your bootstrapper task should inherit BootstrapperTask base class. It has only one method to override Execute which returns TaskContinuation enumeration.

public class MyCustomTask: BootstrapperTask
{
    public override TaskContinuation Execute()
    {
//your code goes here.

        return TaskContinuation.Continue;
    }
}

When the bootstrapper task written you should include it into task execution sequence:

//Global.asax.cs
public class MvcApplication : WindsorMvcApplication
{
    public MvcApplication()
    {
        Bootstrapper.BootstrapperTasks
            .Include<RegisterControllers>()
// other tasks
            .Include<MyCustomTask>();
    }
}

Updated Wiki: Creating BootstrapperTask

hazzik — Fri, 19 Aug 2011 22:35:52 GMT

Updated Wiki: Documentation

hazzik — Fri, 19 Aug 2011 22:31:35 GMT

Topics

Working with IoC Containers (coming up)
- Ninject
- StrucutreMap
- Unity
- Windsor
Working with metadata configurations
Creating BootstrapperTask
Creating PerRequestTask (coming up)
Working with Action Filters (coming up)
Working with Model Binders (coming up)
Working with Action Results (coming up)

Updated Wiki: Windsor

hazzik — Fri, 19 Aug 2011 22:30:52 GMT

First of all you need to inherit you MvcApplication class located in Global.asax.cs from MvcExtensions.WindsorMvcApplication base class.

//Global.asax.cs
public class MvcApplication : MvcExtensions.WindsorMvcApplication
{
}

Second you want to register controller handling by Castle.Windsor IoC container. For that just include RegisterControllers task into bootstrapper tasks executing sequence:

//Global.asax.cs
public class MvcApplication : MvcExtensions.WindsorMvcApplication
{
    public MvcApplication()
    {
        Bootstrapper.BootstrapperTasks
            .Include<RegisterControllers>();
    }
}

Next you should write some installers for IoC container (see http://docs.castleproject.org/Windsor.Installers.ashx). Place them somewhere in your application folder (for ex. into <your mvc application>/Infrastructure) and it will be picked up automagically. Note that you shouldn`t install your controllers by that way, becouse it is already installed by framework.

public class AccountsInstaller : IWindsorInstaller
{
     public void Install(IWindsorContainer container, IConfigurationStore store)
     {
          container.Register(Component.For<IAuthenticationService>().ImplementedBy<FormsAuthenticationService>().LifeStyle.Transient);
     }
}

Updated Wiki: metadata

hazzik — Fri, 19 Aug 2011 22:23:05 GMT

MvcExtensions hase excellent replacement for DataAnnotations model metadata configurations: fluent model metadata configurations. It is provided unlimited flexibility and extensiblity for you metadata.

First of all you need to enable registration of all you metadata. For that include RegisterModelMetadata task into bootstrapper execution sequence

public class MvcApplication : WindsorMvcApplication
{
    public MvcApplication()
    {
        Bootstrapper.BootstrapperTasks
            .Include<RegisterControllers>()
            .Include<RegisterModelMetadata>();
    }
}

Second write some metadata configurations

public class ChangePasswordMetadata : MvcExtensions.ModelMetadataConfiguration<ChangePassword>
{
    public ChangePasswordMetadata()
    {
        Configure(x => x.OldPassword)
            .DisplayName("Old password")
            .Required("Old password is required")
            .AsPassword();

        Configure(x => x.NewPassword)
            .DisplayName("New password")
            .Required("New password is required")
            .MinimumLength(6, "Password length should be at least 6 characters")
            .AsPassword();

        Configure(x => x.ConfirmPassword)
            .DisplayName("Password confirmation")
            .Required("Password confirmation is required")
            .Compare("NewPassword", "Password and its confirmation should be equal")
            .AsPassword();
    }
}

Updated Wiki: metadata

hazzik — Fri, 19 Aug 2011 22:20:25 GMT

MvcExtensions hase excellent replacement for DataAnnotations model metadata configurations. It is provided unlimited flexibility and extensiblity for you metadata.

First of all you need to enable registration of all you metadata. For that include RegisterModelMetadata task into bootstrapper execution sequence

public class MvcApplication : WindsorMvcApplication
{
    public MvcApplication()
    {
        Bootstrapper.BootstrapperTasks
            .Include<RegisterControllers>()
            .Include<RegisterModelMetadata>();
    }
}

Second write some metadata configurations

public class ChangePasswordMetadata : MvcExtensions.ModelMetadataConfiguration<ChangePassword>
{
    public ChangePasswordMetadata()
    {
        Configure(x => x.OldPassword)
            .DisplayName("Old password")
            .Required("Old password is required")
            .AsPassword();

        Configure(x => x.NewPassword)
            .DisplayName("New password")
            .Required("New password is required")
            .MinimumLength(6, "Password length should be at least 6 characters")
            .AsPassword();

        Configure(x => x.ConfirmPassword)
            .DisplayName("Password confirmation")
            .Required("Password confirmation is required")
            .Compare("NewPassword", "Password and its confirmation should be equal")
            .AsPassword();
    }
}

Updated Wiki: metadata

hazzik — Fri, 19 Aug 2011 22:19:43 GMT

public class MvcApplication : WindsorMvcApplication
{
    public MvcApplication()
    {
        Bootstrapper.BootstrapperTasks
            .Include<RegisterControllers>()
            .Include<RegisterModelMetadata>();
    }
}

Second write some metadata configurations

public class ChangePasswordMetadata : MvcExtensions.ModelMetadataConfiguration<ChangePassword>
{
    public ChangePasswordMetadata()
    {
        Configure(x => x.OldPassword)
            .DisplayName("Old password")
            .Required("Old password is required")
            .AsPassword();

        Configure(x => x.NewPassword)
            .DisplayName("New password")
            .Required("New password is required")
            .MinimumLength(6, "Password length should be at least 6 characters")
            .AsPassword();

        Configure(x => x.ConfirmPassword)
            .DisplayName("Password confirmation")
            .Required("Password confirmation is required")
            .Compare("NewPassword", "Password and its confirmation should be equal")
            .AsPassword()                                                            ;
    }
}

Updated Wiki: Documentation

hazzik — Fri, 19 Aug 2011 22:09:40 GMT

Topics

Working with IoC Containers (coming up)
- Ninject
- StrucutreMap
- Unity
- Windsor
Working with metadata configurations
Creating BootStrapperTask (coming up)
Creating PerRequestTask (coming up)
Working with Action Filters (coming up)
Working with Model Binders (coming up)
Working with Action Results (coming up)

Updated Wiki: Documentation

hazzik — Fri, 19 Aug 2011 22:04:20 GMT

Topics

Working with IoC Containers (coming up)
- Ninject
- StrucutreMap
- Unity
- Windsor
Creating BootStrapperTask (coming up)
Creating PerRequestTask (coming up)
Working with Action Filters (coming up)
Working with Model Binders (coming up)
Working with Action Results (coming up)

Updated Wiki: Windsor

hazzik — Fri, 19 Aug 2011 22:03:46 GMT

First of all you need to inherit you MvcApplication class located in Global.asax.cs from MvcExtensions.WindsorMvcApplication base class.

//Global.asax.cs
public class MvcApplication : MvcExtensions.WindsorMvcApplication
{
}

Second you want to register controller handling by Castle.Windsor IoC container. For that just include RegisterControllers bootstrapper task into bootstrapper tasks executing sequence:

//Global.asax.cs
public class MvcApplication : MvcExtensions.WindsorMvcApplication
{
    public MvcApplication()
    {
        Bootstrapper.BootstrapperTasks
            .Include<RegisterControllers>();
    }
}

public class AccountsInstaller : IWindsorInstaller
{
     public void Install(IWindsorContainer container, IConfigurationStore store)
     {
          container.Register(Component.For<IAuthenticationService>().ImplementedBy<FormsAuthenticationService>().LifeStyle.Transient);
     }
}

Updated Wiki: Windsor

hazzik — Fri, 19 Aug 2011 22:03:12 GMT

First of all you need to inherit you MvcApplication class located in Global.asax.cs from MvcExtensions.WindsorMvcApplication base class.

//Global.asax.cs
public class MvcApplication : MvcExtensions.WindsorMvcApplication
{
}

Second you want to register controller handling by Castle.Windsor IoC container. For that just include RegisterControllers bootstrapper task into bootstrapper tasks executing sequence:

//Global.asax.cs
public class MvcApplication : MvcExtensions.WindsorMvcApplication
{
    public MvcApplication()
    {
        Bootstrapper.BootstrapperTasks
            .Include<RegisterControllers>();
    }
}

Next you should write some installers for IoC container (see url:http://docs.castleproject.org/Windsor.Installers.ashx). Place them somewhere in your application folder (for ex. into <your mvc application>/Infrastructure) and it will be picked up automagically. Note that you shouldn`t install your controllers by that way, becouse it is already installed by framework.

public class AccountsInstaller : IWindsorInstaller
{
     public void Install(IWindsorContainer container, IConfigurationStore store)
     {
          container.Register(Component.For<IAuthenticationService>().ImplementedBy<FormsAuthenticationService>().LifeStyle.Transient);
     }
}