Saturday, December 15, 2007

browserCaps setting at web.config : All you need to view a nice asp.net application in Firefox?


"..which one you'll choose : IE7 or Cerie.. err I mean firefox?"

Sounds catchy huh... of course didn't solve most of your problems, but hey... worth a try la macha. Stumbled here while looking for awesome quickie solution to enable current ASP.NET apps to 'look and feel' as kicking as viewed on Internet Explorer 7. (sadly... IE6 also didn't do well).

Link above provide sample of web.config and machine.config example to somewhat make your asp.net application recognizes those Mozilla based, Opera, and what not 'other' browser than IE, treated as 'uplevel' browsers. hehehe... what the '#$%$'. (i believe there is top-secret project behind it) ..doncha see?

xhtml anyone? ..or you dudes have extra-ordinary kinda solution to churn out here?

some recommendation...



# re: ASP.NET Web Controls and browserCaps
Friday, April 04, 2003 9:52 AM by Lance

FYI: Rather than putting that section in your web.config, I recommend maintaining browscap info in your machine.config.

C:\windows\Microsoft.NET\Framework\v1.0.3705\CONFIG\machine.config

if you check your current machine.config you will notice that this is where the current browser mappings are held. By putting it in the web.config you are merely overriding these settings for your 1 app.

This can be useful for control-library developers, but for GP I would recommend deferring to machine.config maintenance instead.

Regards,

Lance


...one of the weird case(mirroring this topic)

Firefox vs Internet Explorer 7 (Firefox vs IE7)

trati tags : vsts, browsercaps,
web.config,
asp.net,
firefox,
xhtml

0 comments: