Before 2-3 days, while I was examining Bundling and Minification in ASP.NET 4.5. I observed problem with CSS3 minification while using default bundling which is available with Microsoft.Web.Optimization. Exploring more on it I found that there is a bug in CSS3 minification (while using nested parentheses) and it is already logged at

http://connect.microsoft.com/VisualStudio/feedback/details/696436/microsoft-web-optimization-cannot-compress-css3-animations
and
http://connect.microsoft.com/VisualStudio/feedback/details/689523/bugs-in-microsoft-web-optimization

Update:
Originally this article was written after first release of developer preview version of MVC 4. For latest changes in RTM version read ASP.NET 4.5 & MVC 4: Revisiting IBundleTransform

Yesterday, we have learnt how to implement default Bundling and Minification with ASP.NET MVC 4 application as well we also examined how to create custom bundle which bundle and minify only specified files. While creating custom bundle, we suppose to pass transform type to bundle. Microsoft.Web.Optimization assembly shipped with two inbuilt transform type namely JsMinify and CssMinify. In addition to built-in transform type, we can also create our own custom transform type. Today we will examine how to create custom transform type for Bundling and Minification.

This post is part of ASP .NET MVC 4 Article Series.

In yesterday’s post, we have discussed that in today’s web application, client side operation is also important as much as server operation. And hence client side operation increase, JavaScript code is also increased and for maintainability of code we generally separate it by functionality in different files. Hence separated code is JavaScript so web page needs to reference many JavaScript files. Now the trouble may starts, as all browsers limits the parallel request and request beyond that limits goes in queue. More information on each browser can be found here on Browserscope. To overcome this we can combine all JavaScript files in one. But as far as code maintainability is concern this is not the right solutions. Another way is to combine and minify all files on the fly. This is also sound to be right solution than combining all JavaScript files into one. Here we will see how we can leverage the Microsoft.Web.Optimization assembly to achieve this.

Day by day, jQuery is becoming a more popular and it is widely used instead core JavaScript. With ASP.NET & ASP.NET MVC also there are so many good examples available on net to get best of both. Moreover default project template of ASP.NET MVC is also including latest jQuery file for easiness of client operation.

To perform any jQuery operation, first we need to select target DOM element or set of DOM elements. And we are living (rather programming) in the era of web 2.0 and Mashup where web documents are suppose to be large with few hundred elements and lots of client side operation as well. So here we will see how one small tip can be helpful to improve jQuery performance.

Last month on 5th Anniversary give away of http://blog.sqlauthority.com/ , I received, SQL Wait Stats Joes 2 Pros book from Pinal Dave. Although I am not a SQL developer but I was very curious to know more about SQL Wait Stats since the June 11, 2011 (day, I attended Pinal Dave’s session on Wait Stats at Community Tech Day, Ahmadabad) as it affect the overall performance of system. As I told I am not SQL developer, so after that day, I could not bother (frankly telling) to look into book when it is published. Luckily, Last month I received book from Pinal Dave on 5th anniversary of his blog. And surprisingly after starting to read it I could not stop it and completed whole book in one seating! And I realized that I could have missed many things if I have not received the book. I would highly recommend all reader of this blog to read this book once. So I thought to write on why this book is special for person who has to deals with SQL server (and of course to convey my gratitude towards Pinal Dave also).

Updated on 03-Feb-2013
Check out this NuGet package for auto update MVC 3 to MVC 4 application and read this post for more info ASP.NET MVC: Auto upgrade MVC 3 to MVC 4 application

This post is part of ASP .NET MVC 4 Article Series.

To upgrade and existing ASP.NET MVC 3 Project to ASP.NET MVC 4, one need to take care of following points. Complete guideline on upgrading from MVC 3 to MVC 4 is available in MVC 4 Release Notes.

In last post, Efficient Use of Try Catch Block, we have used StopWatch class to measure CPU ticks consumed by particular code execution. After reading that one of the reader asked cant we use DateTime.Now instead. So here I have tried to explain the same.

Many times we have found developer to use DateTime.Now to measure the performance of code execution. But if you google it out, you will find plenty of source which recommend using StopWatch class instead DateTime.Now. Here I am summarizing few of them.

In all application, whether it is web or desktop, whether it is built in .NET or JAVA or any other language, we all are using (and we should use if we are not!) Try Catch Block or similar available mechanism to handle the exception.

But recently while I was working on one application, I observed that Try Catch Block was also used to make decision!!! As Try Catch mechanism is provided to handle exception and hence it is heavy operation and utilizes more CPU, we should not use Try Catch for such decision making scenario. Instead we should look for any alternate solution. Let try to understand whole scenario by formulating one small example.