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

I had the same problem with the beta 3 of .NET Web Server.  Check the

version number of ASP.NET in the Release Candidate.  The beta 2 version

of VS.NET is higher than the version that comes with the beta 3 .NET Web

Server.  I'm running version 1.0.2914, and the example runs perfectly

with that version (VS.NET beta 2).



> -----Original Message-----

> From: Brant Henne [mailto:brant.henne@a...]

> Sent: Tuesday, January 08, 2002 2:03 PM

> To: aspx_beginners

> Subject: [aspx_beginners] .NET Release Candidate 1 flubbing up html

forms!

> 

> 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



> to unsubscribe send a blank email to leave-aspx_beginners-

> 793387L@p...