Just wondering if this got solved yet?!

I am having the same problem.

Thanks!

> Hey gang,
> 
> I just installed the monstorous release candidate 1 (upgrading from beta 
> 2).  It's screwing up some forms.  Namely, the exercise in chapter 3, 
> holidaypage.aspx.  The form, which ran correctly in beta 2, is coded as 
> such:
> 
> <form action="holidayresponse.aspx" method="post">
> [[[note: this is from wrox's sample code, not mine.]]]
> 
> In release candidate 1, it generates an error: 
> "System.Web.HttpException: Control 'FullName' of type 'TextBox' must be 
> placed inside a form tag with runat=server"
> 
> Clearly it's flipping out on any asp control that's not inside a form 
with 
> a runat="server" value.  Makes some sense.
> 
> Here's the real conumdrum:  I tried to include runat="server", but when 
> that's in the the form tag, it dosn't generate an error, but it also no 
> longer posts to the holidayresponse.aspx page.  It doesn't matter if the 
> method="post" is removed from the form tag.
> 
> Does anybody have any thoughts on this?  Thanks

One part I can comment on:

Aspx web forms no longer support posting away.

It can be done with a workaround but essentially you need to be thinking
in terms of always posting back to the same form.

Not all controls need to be inside a runat=server form label for example

I have coded some post away examples and will share them if anyone
requests.

Mark Harwood

-----Original Message-----
From: Adam Cavaliere [mailto:aspbeginer@a...] 
Sent: 23 November 2002 15:34
To: aspx_beginners
Subject: [aspx_beginners] Re: .NET Release Candidate 1 flubbing up html
forms!

Just wondering if this got solved yet?!

I am having the same problem.

Thanks!

> Hey gang,
> 
> I just installed the monstorous release candidate 1 (upgrading from
beta 
> 2).  It's screwing up some forms.  Namely, the exercise in chapter 3, 
> holidaypage.aspx.  The form, which ran correctly in beta 2, is coded
as 
> such:
> 
> <form action="holidayresponse.aspx" method="post">
> [[[note: this is from wrox's sample code, not mine.]]]
> 
> In release candidate 1, it generates an error: 
> "System.Web.HttpException: Control 'FullName' of type 'TextBox' must
be 
> placed inside a form tag with runat=server"
> 
> Clearly it's flipping out on any asp control that's not inside a form 
with 
> a runat="server" value.  Makes some sense.
> 
> Here's the real conumdrum:  I tried to include runat="server", but
when 
> that's in the the form tag, it dosn't generate an error, but it also
no 
> longer posts to the holidayresponse.aspx page.  It doesn't matter if
the 
> method="post" is removed from the form tag.
> 
> Does anybody have any thoughts on this?  Thanks