Master pages - A page can have only one server-side Form tag.

  • Thread starter Thread starter Karthik
  • Start date Start date
K

Karthik

I am converting all my asp.net pages to asp.net 2.0 for supporting
master pages.

I get the following error in runtime.



A page can have only one server-side Form tag.
Description: An unhandled exception occurred during the execution of
the current web request. Please review the stack trace for more
information about the error and where it originated in the code.

Exception Details: System.Web.HttpException: A page can have only one
server-side Form tag.



your help is highly appreciated
 
Karthik said:
I am converting all my asp.net pages to asp.net 2.0 for supporting
master pages.

I get the following error in runtime.

A page can have only one server-side Form tag.
Description: An unhandled exception occurred during the execution of
the current web request. Please review the stack trace for more
information about the error and where it originated in the code.

Exception Details: System.Web.HttpException: A page can have only one
server-side Form tag.

your help is highly appreciated

And how many forms do your pages actually have? Do you by any chance
have one on the master page and one in the actual pages?
 
And how many forms do your pages actually have? Do you by any chance
have one on the master page and one in the actual pages?

Hi jon,

Thanks for your response.

I have two pages, one master page and another page which uses the
master page.
i have <form runat = "server"> tag in my derived page. because of this
i got this error.
i tried removing the form tag, but it didn't work. it gives the same
error.
Is there any other way to convert these pages.
 
I have two pages, one master page and another page which uses the
master page.
i have <form runat = "server"> tag in my derived page. because of this
i got this error.
i tried removing the form tag, but it didn't work. it gives the same
error.
Is there any other way to convert these pages.

Please post a sample master page, and a sample content page, as simple
as possible, that still gives you the error.
 
Back
Top