Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
i have a search form on every page, hence i put it on the master page. after adding runat=server to that form i am now unable to use other forms that runat server 😉
how do people usually get around this?
one idea is to surround the whole page with one form runat=server but then i have to have the code in the master page even for those forms that are used on only one sub page (like contact for example).
how do people usually get around this?
thnx
This has often been considered one of the most problematic design decisions on ASP.NET. It’s a sad thing that you’re kinda fixed to this one-form-per-page principle.
One reason that you may want to have multiple forms is that the default button will be set by the browser to the submit button. Someone typing into your search box and hitting enter should not submit the main form (suppose that’s the login page), but the tiny form of the search button.
The easiest and “standard” way to work around this is using an asp:Panel and set the DefaultButton property. This should wrap around the part that includes both the search fields and the search button.
Don’t worry about coding the
<form>from inside the masterpage, surrounding the whole page. That’s a common design. Most server controls require a form, so why not simply include it regardless: it is supposed to be there.