Faisal is a master all right but this article fails to address the real issue facing web developers. The HttpBrowserCapabilites can tell us what functionality a User Agent *can* support but does nothing to tell us if the User Agent has certain specific functionality *activated*

For example, if the user has their browser configured to disable cookies or JavaScript the HttpBrowserCapabilites is useless. Perhaps Faisal could focus his mastery on publishing a solution to this dilemma.

The article explains how to make use of HttpBrowserCapabilities object which every ASP.NET application will have access to. So making good use of something which is available to all of us is not a bad thing but the point that it doesn''t answer issues like ''disabling cookies'' and/or JavaScript is also important as HttpBrowserCapabilities is not going to find that.

I''ll see if I can spare some time to develop a component to address issues like these but in the mean time you can make use of BrowserHawk ( http://ads.aspalliance.com/adredir.aspx?a=170&m=18&s=& ) component which does not only this but more.