Chapter 4 error

Sarah-WCHM · July 6th, 2004, 01:55 PM

I am working my way through the book and doing all of the exercises and Try-It-Outs as I come to them. While the one on p. 122 is not necessary for my intended use of ASP.Net it is still frustrating. I can't get the exercise to work and when I use the code from the download instead of my own code I get the same error -- that the date is not recognized as valid but ONLY when the date is a 2005 date. Nothing happens when I use a 2004 date (as intended, I believe).

Has anybody else experienced this particular bug?

Hal Levy · July 6th, 2004, 03:16 PM

The code on page 122 in the c# Book is missing opening CurlyQ on the if (IsPostBack) line. I assume your problem is with TIO #1.

The code below works. Place it inside of the <script> tags.

This should be confirmed and moved to the erata page?

Code:

void Page_Load()
{
    if (IsPostBack)
    {
        DateTime datInput;
        datInput = Convert.ToDateTime(txtIn.Text);
        if (
            datInput >=Convert.ToDateTime("1/1/2005")
            &&
            datInput <=Convert.ToDateTime("12/31/2005")
        )
        lblOut.Text = "Date inside year 2005." + datInput;
     }
}

Is your problem something else?

Hal Levy
Web Developer, PDI Inc.

NOT a Wiley/Wrox Employee

Sarah-WCHM · July 6th, 2004, 04:40 PM

Thanks for the prompt response! The error WAS that particular one, combined with another--the date format on my computer is set to Canada, which reverses the month & day. Fixing both fixed my problem. Again, thanks!

Hal Levy · July 7th, 2004, 08:35 AM

Sarah,

Good point there- perhaps the eratta should also list that the date must be in the same format as your local settings...

Hal Levy
Web Developer, PDI Inc.

NOT a Wiley/Wrox Employee

paulus · July 25th, 2004, 08:52 AM

Hi There, just came across the same problem. Glad you took the time to solve it. I am only starting out, but this makes me wonder: ASP.NET is meant for web development. As coders cannot expect the rest of the world to conform to US date/time notation, how do we ensure that end users do not get errors like this one?

Hal Levy · July 28th, 2004, 09:57 AM

1. Pick a standard and tell your users what that standard is.
2. Create cases based on regional settings and write different code for each region.

Hal Levy
Web Developer, PDI Inc.

NOT a Wiley/Wrox Employee