Does anyone know what the fix is for this example to work?

Thanks in advance,
Bob


> 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...
> 
> 

This problem with the holiday.aspx page in ASP.NET Using VB.NET has had 
at least a couple of posts in the last several months. This is the first 
I've heard that it worked at all (on a beta release of VS.NET? or the 
framework?). 

I couldn't get the page to work, so I checked the errata for the book and 
it is listed as an error there. The workaround posted (in which one nests 
a <form runat=server> within another <form runat=server> -- or at least 
that's what I remember the 'solution' as being -- the Wrox site is not 
available to me now so I can't check). But this also did not work for me. 
I posted the problem on this forum a couple of months ago and there 
weren't any solutions that I remember. I think I had trouble also with 
any post="whatever" that didn't equal the same page that contained the 
form (postback to itself), which caused me to wonder (and ask on the 
forum) if it was possible to post to another page at all. It would be a 
wonder if this weren't possible with .NET, so I just figured the problem 
was my lack of knowledge and a Wrox example that didn't work right. So I 
just went on working my way through the book hoping for better luck (I 
found and reported another error later on, but the others I found were 
already posted on the errata page at the Wrox site).

Dan

The idea behind ASP.NET is that indeed you can't submit a page to another 
page that does the processing. The way things are set up, the code that 
handles the submitted data should be in the same page as the original form.

However, there are times when this is just not good enough, for example 
when you want to submit info to a complete different website, or to a page 
/ site that doesn't use .NET but PHP / JSP / ASP / WhateverP.

There are a few work arounds. One is mentioned at the following URL:

http://www.aspalliance.com/wisemonk/view.aspx?id=AN012522


HtH

Imar





At 08:15 AM 6/15/2002 +0000, you wrote:
>This problem with the holiday.aspx page in ASP.NET Using VB.NET has had
>at least a couple of posts in the last several months. This is the first
>I've heard that it worked at all (on a beta release of VS.NET? or the
>framework?).
>
>I couldn't get the page to work, so I checked the errata for the book and
>it is listed as an error there. The workaround posted (in which one nests
>a <form runat=server> within another <form runat=server> -- or at least
>that's what I remember the 'solution' as being -- the Wrox site is not
>available to me now so I can't check). But this also did not work for me.
>I posted the problem on this forum a couple of months ago and there
>weren't any solutions that I remember. I think I had trouble also with
>any post="whatever" that didn't equal the same page that contained the
>form (postback to itself), which caused me to wonder (and ask on the
>forum) if it was possible to post to another page at all. It would be a
>wonder if this weren't possible with .NET, so I just figured the problem
>was my lack of knowledge and a Wrox example that didn't work right. So I
>just went on working my way through the book hoping for better luck (I
>found and reported another error later on, but the others I found were
>already posted on the errata page at the Wrox site).
>
>Dan