I prefer having an [external] css file for each page because 1) VS.Net [for some strange reason] gives me CSS IntelliSense and CSS designer support when css is either in an inline-style tag or in a .css file but *NOT* when the css is put into a <style></style> tag set in the HEAD of a document. The css IntelliSense support while not complete is nice. 2) I can make changes to the css file without touching the .aspx page 3) the css file is cached client side.
I really like the idea of giving the body tag an ID though - that's something I have never thought of. james c -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ian Anderson <snip> You should only use external CSS when the rules are for sharing with other pages, IMHO. Otherwise you are adding inconvenience without gaining any corresponding benefit, and it means an extra server hit for each page viewed - completely contrary to all the normal advantages of using external files. Keeping the rules within the document allows you to use sensible global naming conventions within each page like... </snip> ______________________________________________________________________ css-discuss [EMAIL PROTECTED] http://www.css-discuss.org/mailman/listinfo/css-d IE7b2 testing hub -- http://css-discuss.incutio.com/?page=IE7 List wiki/FAQ -- http://css-discuss.incutio.com/ Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
