StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>Does your page contain these</p> <pre><code><asp:Content ID="Content1" ContentPlaceHolderID="ContentPlaceHolder1" Runat="Server"> </asp:content> </code></pre> <p>tags, and are all your controls inside these? You should only have the Form tags in the MasterPage.</p> <hr> <p>Here are some of my understanding and suggestion:</p> <p>Html element can be put in the body of html pages and html page does support multiple elements, however they can not be nested each other, you can find the detailed description from the W3C html specification:</p> <h1>The FORM element</h1> <p><a href="http://www.w3.org/MarkUp/html3/forms.html" rel="nofollow noreferrer">http://www.w3.org/MarkUp/html3/forms.html</a></p> <p>And as for ASP.NET web form page, it is based on a single server-side form element which contains all the controls inside it, so generally we do not recommend that we put multiple elements. However, this is still supported in ASP.NET page(master page) and I think the problem in your master page should be caused by the unsupported nested element, and multiple in the same level should be ok. e.g:</p> <p>In addition, if what you want to do through multiple forms is just make our page posting to multiple pages, I think you can consider using the new feature for cross-page posting in ASP.NET 2.0. This can help us use button controls to postback to different pages without having multpile forms on the page:</p> <h1>Cross-Page Posting in ASP.NET Web Pages</h1> <p><a href="http://msdn2.microsoft.com/en-us/lib...39(VS.80).aspx" rel="nofollow noreferrer">http://msdn2.microsoft.com/en-us/lib...39(VS.80).aspx</a></p> <p><a href="http://msdn2.microsoft.com/en-us/lib...40(VS.80).aspx" rel="nofollow noreferrer">http://msdn2.microsoft.com/en-us/lib...40(VS.80).aspx</a></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