StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<ol> <li>Right click the project -> Add -> ASP.Net Folder and add a Theme. Name it as you wish.</li> <li>Right click your skin -> Add -> New item -> .skin</li> <li><p>In the skin file, write the Skins for your controls. ex. </p> <pre><code> <asp:TextBox runat="server" BackColor="IndianRed" ForeColor="Snow" Font-Size="X-Large" Font-Italic="true" Font-Underline="true" // optional SkinID = "textbox_skin" > </asp:TextBox> </code></pre> <p>Define the <strong>SkinID</strong> property - It allows you to apply the skin only on the needed controls later. If the skin should apply on all the controls in your project don't define it.</p></li> <li><p>In your <code>@Page</code> directive there are two options to add the skin, depending on your design:</p> <ul> <li><p>Add <code>Theme="your_skin_name"</code>, if you want the defined skin in your *.skin file to override the already existing style that the controls have. For example if the control already has some css defined, with Theme="your_skin_name" they won't be taken into account anymore.</p></li> <li><p>Add <code>StylesheetTheme="your_skin_name"</code> if you want to keep your already defined styles, and add from the skin only the ones that are missing. </p></li> </ul> <ul> <li>If you want to define by your self, which controls get the style from the Theme/Skin, than use the SkinID like this in your *.aspx file:</li> </ul> <p><code><asp:TextBox ID="TextBox1" runat="server" SkinID="textbox_skin"> </asp:TextBox></code></p></li> </ol> <p><em><strong>note</em></strong>: if you define the SkinID on a control skin in the *.skin file, than in the *.aspx you have to define it also, on the corresponding controls that the skin should apply to. </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