In asp.net, .css file is encouraged to use?

Guest · Nov 9, 2005

Hi, friends,

In our ASP app, we have a lot of style definitions in our .css file. Now, in
asp.net, .css is encouraged to continue to use, or is better to be replaced
by something new in .net???

Any reference papers?

Thanks a lot.

Juan T. Llibre · Nov 9, 2005

CSS is quite encouraged to be used.

Nothing in .Net replaces CSS.

Tim Cartwright · Nov 9, 2005

IMHO it is actually very good practice to combine the two, skinning, and
css. One of the nice things about using skinning and css, regardless of
whether or not if you only have one theme, is that you get WSIWYG if you set
the page.theme, and the page.stylesheettheme in the IDE. Not to mention the
fact that your css will automatically go in the <head> tag. I have actually
set both of these properties in my config as such :

<system.web>
<pages theme="default" styleSheetTheme="default" />

..... other config suff
</system.web>

Using the location element in the config, you can also change the theme per
file / directory. Or you could just over ride the theme in the page itself.

Juan T. Llibre · Nov 9, 2005

Is skinning supported cross-browser ?

Tim Cartwright · Nov 9, 2005

Here is a very nice tutorial / explanation Juan.
http://msconline.maconstate.edu/tutorials/ASPNET2/ASPNET10/aspnet10-09.aspx
Also to answer your question, yes, they are cross browser.

Juan T. Llibre · Nov 9, 2005

Thanks, Tim.

I haven't gone too deep into skinning.

Scott Allen · Nov 10, 2005

Maybe some fine-tuning is needed for a true "cross-browser" experience?

All of the skin and theme work happens server side (see "Under the
Hood in http://odetocode.com/Articles/423.aspx). If doubt any cross-
browser issues are due to a deficiency in the theme/skin feature. I'd
suspect the problem is with styles or properties the desginer used in
a skin / theme.

Juan T. Llibre · Nov 10, 2005

re:

I'd suspect the problem is with styles or properties
the designer used in a skin / theme.

Two out out three browsers rendered correctly, while a third did not.

re:

All of the skin and theme work happens server side

There's some "fine-tuning" needed.

I checked the source for those tables for FF, IE and Opera and they're identical.

Maybe the issue is with Firefox not being identified correctly,
and therefore FF is not getting HTML it can understand well ?

FF *should* render standard HTML the same way IE and Opera render it.
Check out the source. I was surprised when I found them to be the identical.

Kevin Spencer · Nov 10, 2005

I haven't gone too deep into skinning.

You mean, you've only gone "skin-deep?"

--
;-),

Kevin Spencer
Microsoft MVP
..Net Developer
Complex things are made up of
Lots of simple things.

Tim Cartwright · Nov 10, 2005

Well, actually sometimes the issue with rendering to Firefox is that the
built in browscaps are outdated, and do not recognize FireFox as an uplevel
browser, so the asp.net engine outputs exactly what it thinks is the
appropriate html for Firefox. Read
http://www.asptoday.com/Content.aspx?id=2339 and
http://slingfive.com/pages/code/browserCaps/ for more info.

Juan T. Llibre said:
re:

I'd suspect the problem is with styles or properties
the designer used in a skin / theme.

Click to expand...

Two out out three browsers rendered correctly, while a third did not.

re:

All of the skin and theme work happens server side

Click to expand...

There's some "fine-tuning" needed.

I checked the source for those tables for FF, IE and Opera and they're
identical.

Maybe the issue is with Firefox not being identified correctly,
and therefore FF is not getting HTML it can understand well ?

FF *should* render standard HTML the same way IE and Opera render it.
Check out the source. I was surprised when I found them to be the
identical.

Juan T. Llibre · Nov 10, 2005

re:
Read

http://www.asptoday.com/Content.aspx?id=2339 and
http://slingfive.com/pages/code/browserCaps/ for more info.

Yes, I've recommended those very same links, many times, here.

That's what I implied in this statement :

Maybe the issue is with Firefox not being identified correctly,
and therefore FF is not getting HTML it can understand well ?

Tim Cartwright said:
Well, actually sometimes the issue with rendering to Firefox is that the built in
browscaps are outdated, and do not recognize FireFox as an uplevel browser, so the
asp.net engine outputs exactly what it thinks is the appropriate html for Firefox. Read
http://www.asptoday.com/Content.aspx?id=2339 and
http://slingfive.com/pages/code/browserCaps/ for more info.

CSS File does not really work?	1	Jul 7, 2023
Need assistance finetuning HTML, CSS, Javascript - sticky header issue	3	Feb 25, 2022
What is the purpose of the resource file asp.net. you see it in text as resource:resources file	0	Apr 20, 2022
Help to decide which sw to use	1	Nov 18, 2023
I'm tempted to quit out of frustration	1	Aug 13, 2023
Hi, I am a webflow user. I am looking for CSS code that can KEEP ALL ELEMENTS POSITIONED in the SAME spot across all resolutions	0	Oct 27, 2023
Working on mobile css menu with plenty of frustration!	2	Dec 29, 2022
Css not being loaded	1	Oct 3, 2017

In asp.net, .css file is encouraged to use?

Guest

Juan T. Llibre

Tim Cartwright

Juan T. Llibre

Tim Cartwright

Juan T. Llibre

Scott Allen

Juan T. Llibre

Kevin Spencer

Tim Cartwright

Juan T. Llibre

Ask a Question

Similar Threads

Members online

Forum statistics

Latest Threads