RE: What is the best way to handle old browser versions?
From: Lenn (Lenn_at_discussions.microsoft.com)
Date: 09/18/04
- Next message: gh0st54: "Re: enter key hell problem 2"
- Previous message: Henrik Larsen: "Wrap a div tag around viewstate output"
- In reply to: Jason: "What is the best way to handle old browser versions?"
- Next in thread: Jason: "Re: What is the best way to handle old browser versions?"
- Reply: Jason: "Re: What is the best way to handle old browser versions?"
- Messages sorted by: [ date ] [ thread ]
Date: Sat, 18 Sep 2004 15:27:01 -0700
At my last job we had to support an Internet site opened to all browsers. I
am still having nightmares about supporting Netscape 4.7x time to time :)
You're lucky that you starting a new project in ASP.NET, because
'supposedly' according to Microsoft, it's supposed to work with all browsers.
The way it's achieved is in machine.config file there's a <BrowserCaps>
section that tells ASP.NET which browser supports which standard. So it will
send the right tags/script to the right browser, assuming you're using server
controls rather than Response.Write HTML. BUT there's a big "BUT"! When it
comes to Netscape, most of the tags/scripts will still not work right! For
whatever reasons, this link below is just one of them:
http://searchvb.techtarget.com/vsnetATEAnswers/0,293820,sid8_gci905632_tax293672,00.html
Also you'll have difficulties getting CustomValidators to work with
Netscape, so you’ll have to write server-side validation code…
I can't think of everything that doesn't work with Netscape... You might
have to fine-tune <BrowserCaps> settings to get it to work correctly.
Of course convincing them to upgrade to IE will save you lots of efforts and
development time ($ in general) and give users feature-rich application since
ASP.NET works best with IE. That company is not going to be using Netscape
4.7x forever. Maybe it could be a good opportunity for them to upgrade. They
found good enough reasons to convert from Java to ASP.NET, but they can’t
find any good reasons to upgrade to IE? Is not that ironic?
Good luck!
"Jason" wrote:
> We have an Extranet with one customer with 20,000 users that has,
> unfortunately, standardized on Netscape 4.77 for the entire company. We are
> in the process of rewriting this application from Java to .NET and, of
> course, would not like to be constrained by the Least Common Denominator
> (LCD) this particular company represents.
>
> Question: What is the best way to handle this without having to double the
> development effort? For example, MVC pattern, etc.?
>
>
>
- Next message: gh0st54: "Re: enter key hell problem 2"
- Previous message: Henrik Larsen: "Wrap a div tag around viewstate output"
- In reply to: Jason: "What is the best way to handle old browser versions?"
- Next in thread: Jason: "Re: What is the best way to handle old browser versions?"
- Reply: Jason: "Re: What is the best way to handle old browser versions?"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
