I am going to start a new series of posts that focus on HTML 5. HTML 5 is something I wanted to learn and finally I have covered enough ground to feel confident.HTML 5 gives us things like Semantic tags, the possibility to add video and audio in our pages without any plugins.With Canvas we can have very rich animations to our web pages.

I see that now with all these emerging technologies there are many things you can do on the client. JQuery is amazing and you can do so many things. Please have a look at my posts on JQuery. CSS3 is another big player that all developers should look into.

Some people might argue that front-end developers cannot use HTML 5 and CSS3 right now, because there are many browser versions from various vendors that do not support them or support them partially. IE6- IE8 do not support CSS3 (or there is a little support) but IE 9 supports many of them.In general (with some exceptions) IE9, Opera 10+, Firefox 3.5+, pretty much any reasonably recent version of Chrome, and Safari 3+ support CSS3.

CSS3 comes with Color enhancements,Transforms,Shadowing,Rounded corners and much more.

In these series of posts I am going to have a look into the various factors that make our web applications slower and how we can rectify that. Ι have already blogged about caching in this blog and you can find these blog posts below

This another post that is focusing on how to use JQuery in ASP.Net applications. If you want to have a look at the other posts related to JQuery in my blog click here

This another post that is focusing on how to use JQuery in ASP.Net applications. If you want to have a look at the other posts related to JQuery in my blog click here

This another post that is focusing on how to use JQuery in ASP.Net applications. If you want to have a look at the other posts related to JQuery in my blog click here

This another post that is focusing on how to use JQuery in ASP.Net applications. If you want to have a look at the other posts related to JQuery in my blog click here

This is going to be another short post regarding ASP.Net and custom error pages. Our goal is to specify a particular page to be displayed on the user's screen when error occurs within our application.In order to that we basically have to make some changes in the web.config file.

In this post (it is going to be very short for a change) I would like to show you how to take your ASP.Net application offline.