StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>You can have many theme folders within the App_Themes folder. An ASP.Net Theme can consist of many skin files and many css files.</p> <ol> <li>Yes, the Skin file is aware of the CSS file. When you apply a Theme, your page is made aware of all of the .css files in the Theme automatically.</li> <li>I'm not sure. Testing is the only way to go.</li> <li>No, .skin files are different than .css files. Yes, you can just use css files in a theme and skip the skins. Yes, skins are just for asp.net server controls. </li> </ol> <h2>Themes vs. Cascading Style Sheets</h2> <p>Themes are similar to cascading style sheets in that both themes and style sheets define a set of common attributes that can be applied to any page. However, themes differ from style sheets in the following ways:</p> <ul> <li>Themes can define many properties of a control or page, not just style properties. For example, using themes, you can specify the graphics for a TreeView control, the template layout of a GridView control, and so on.</li> <li>Themes can include graphics.</li> <li>Themes do not cascade the way style sheets do. By default, any property values defined in a theme referenced by a page's Theme property override the property values declaratively set on a control, unless you explicitly apply the theme using the StyleSheetTheme property. For more information, see the Theme Settings Precedence section above.</li> <li>Only one theme can be applied to each page. You cannot apply multiple themes to a page, unlike style sheets where multiple style sheets can be applied.</li> </ul> <p>Quoted from: <a href="http://msdn.microsoft.com/en-us/library/ykzx33wh.aspx" rel="nofollow noreferrer">ASP.NET Themes and Skins Overview</a></p> <hr> <p>My Opinion:</p> <p>Generally, if you've got a good understanding of CSS you don't really need .Skin files but Themes are still useful.</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload