Yesterday, I came across a forum post, where user was facing problem in integrating web optimization framework with MVC 3. So here in this post we will see how we can integrate asp.net web optimization framework with MVC 3 and ASP.NET 4.0 web form application.

Web optimization framework was introduced with MVC 4 and it is included in default MVC 4 template. But we can use it with MVC 3 and ASP.NET 4.0 web form application as well. This is because web optimization framework is built on top of framework 4.0. So here are the steps to use web optimization framework with ASP.NET 4.0 application.

Over the last few days, I was getting many requests from reader and friends, to start beginner level article series on ASP.NET and MVC. Generally I am sharing my learning experience here on this blog and mostly which fall in intermediate or advanced level. So I thought to write several beginners level article series on ASP.NET MVC. Towards to this step, this is the first article series on action filter in ASP.NET MVC. In this series we will see different available action filter in MVC including MVC 4. Do request other article series here with me; I will try my best to get it here.

In yesterdays post ASP.NET 4.5 & MVC 4 Bundling: Next Approach, we have seen how we can pass additional parameters to bundle transform so we can utilize it while generating bundle response. I suggest you to read that post first before starting with this post.

What was the original idea?

Recently in one application, I have to create one JavaScript object which represents C# enum in client side. Later on C# enum keep extending and at the same time I used to add entry in JavaScript object too. Everything was fine but sometime me or team member forget to sync JavaScript object with C# enum when adding or removing existing entry in C# enum and JavaScript starts breaking and further more each time syncing JavaScript object with C# enum was also tedious task specially when team member is new and do not know whole application architecture. So I though let me create one HTTP handler which generates dynamic JavaScript which represent C# enum.

In the earlier post, we have seen how we can access bundle context while processing bundle through custom transform. Taking it further, in this post we will see how we can utilize bundle context to pass extra parameters to transform and later how we can utilize those parameters to transform bundle.

ChildActionOnly action filter confirms that specified action method should be only accessible by child request. Unlike NonAction filter, such methods are still treated as action method but it can’t be invoke as a parent request. More specific user can’t invoke it direct by requesting action name but we developer can invoke it through code.

So far we have seen various action filter in ASP.NET MVC which allow us to restrict action method usage based on HTTP verb or method. But with the usage of HttpGet, HttpPost, HttpPut or other such action filter, we are limited to only respective HTTP verb. But sometime we require that action method should be accessible by more than one HTTP verb but not all. This is the case where AcceptVerbs comes in picture.