Has HttpBrowserCapabilities Now Become Pragmatically Useless?

  • Thread starter Thread starter Hillbilly
  • Start date Start date
H

Hillbilly

Poof! Parsing of all of the stylesheets for various browsers I've re-worked
THREE TIMES in only two years already are once again FUBAR and it appears
the HttpBrowserCapabilities Object has become pragmatically useless.
Consider what it now returns...

Opera FireFox Chrome Safari IE8
=========================================================
Type = Opera9 Firefox3.5.7 Desktop Desktop IE7
Name = Unknown Unknown Safari Safari Unknown
Major = 9 3 532 531 7

WTF? We've got to write a whole bunch of code to sort this nonsense out. Is
there a better way or an updated library somebody has developed to process
all of the various inconsistent and incorrect differences now being
detected?
 
* Hillbilly wrote, On 24-1-2010 23:45:
Poof! Parsing of all of the stylesheets for various browsers I've
re-worked THREE TIMES in only two years already are once again FUBAR and
it appears the HttpBrowserCapabilities Object has become pragmatically
useless. Consider what it now returns...

Opera FireFox Chrome Safari IE8
=========================================================
Type = Opera9 Firefox3.5.7 Desktop Desktop IE7
Name = Unknown Unknown Safari Safari Unknown
Major = 9 3 532 531 7

WTF? We've got to write a whole bunch of code to sort this nonsense out.
Is there a better way or an updated library somebody has developed to
process all of the various inconsistent and incorrect differences now
being detected?

You can update the browser capabilities yourself and either put them in
the web.config or in the machine.config.

See the following article for more details:
http://msdn.microsoft.com/en-us/magazine/cc300549.aspx

And use the following website as a reference:
http://browsers.garykeith.com/downloads.asp
 
Back
Top