Are there any known issues for visiting asp.net pages on Macintosh?

[Jack]

Hello:
We have a customer whose stuff are using Macintosh, and we just created
an asp.net web application in windows 2003 server, but we met some
strange problems when they visit the application, so I wonder are there
any known issues and solutions about this?

Thanks in advance!
Jack

 

[Juan T. Llibre]

Hi, Jack.

Incorporating the additional browser definitions at :
http://slingfive.com/pages/code/browserCaps/browserCaps_spaces.txt
should get rid of your customer's problems.

If it doesn't, please post back the browser's name and version,
and it's user-Agent, to see if somebody can come up with a
custom browser definition for it.

 

[Bruce Barker]

several issues

1) need to update browsercaps, or asp.net strips height and width styles
2) no client validation runs
3) no smart nav support (should not use anyway)
4) the mac is html 4.0 complient, while IE is not, may change layout (style
commands work different)
5) grid mode may cause layout problems (this actually true with IE and
windows ) and should not be used.
6) any client script must be validated

-- bruce (sqlwork.com)

 

[Jack]

Thank you both!
But Juan, how to incorporate the additional browser definiitions?

 

[Jack]

And they are running Internet Explorer, in Macintosh.

 

[Juan T. Llibre]

Jack,

there's full instructions at :
http://slingfive.com/pages/code/browserCaps/

See the "installation" section.
Be careful when editing machine.config, and make a backup before starting.

If you prefer, copy the whole browsercaps section in
machine.config to your web.config, and add the code at :
http://slingfive.com/pages/code/browserCaps/browserCaps_spaces.txt
to the end of the <browsercaps> section.

Make sure you don't duplicate the section heading ( <browsercaps> ).

Warning : for Beta 2 and later versions of ASP.NET 2.0, the complete
browser detection system is overhauled and the browsercaps section
disappears from machine.config.

It was replaced by a series of *.browser configuration files stored in
drive:\WINDOWS\Microsoft.NET\Framework\v2.0.50xxx\CONFIG\Browsers

There's still a <browsercaps> section in web.config, but it's a minimal one.

What you'll need to do for adding browser detection capabilities in Beta 2
and later is write a *.browser file for the new browser and an alias for it in
the <clientTarget> section of web.config, if needed.

 

[Juan T. Llibre]

I should have added that while the browser detection mechanism
has changed, the old model ( with <browsercaps> entries ) is still supported.

I'm diving into the new model, though.

Here two links to more information on the new browser detection model :

browserCaps Element (ASP.NET Settings Schema)
http://msdn2.microsoft.com/sk9az15a

Browser Definition File Schema (browsers Element)
http://msdn2.microsoft.com/ms133991

There's also an App_Browsers directory for adding *.browser files.
If you modify any file in the App_Browsers directory, the application will restart.

If you modify any *.browsers file in the CONFIG\Browsers directory, you must
manually recompile the application by using the aspnet_regbrowsers.exe tool,
or you must programmatically recompile it by using the BrowserCapabilitiesCodeGenerator
class.

 

[Jack]

Aha, thanks, will try your solution and come back to you.