Wrox Programmer Forums
BOOK: Beginning ASP.NET 2.0 BOOK VB ISBN: 978-0-7645-8850-1; C# ISBN: 978-0-470-04258-8
This is the forum to discuss the Wrox book Beginning ASP.NET 2.0 by Chris Hart, John Kauffman, David Sussman, Chris Ullman; ISBN: 9780764588501
Welcome to the p2p.wrox.com Forums.

You are currently viewing the BOOK: Beginning ASP.NET 2.0 BOOK VB ISBN: 978-0-7645-8850-1; C# ISBN: 978-0-470-04258-8 section of the Wrox Programmer to Programmer discussions. This is a community of software programmers and website developers including Wrox book authors and readers. New member registration was closed in 2019. New posts were shut off and the site was archived into this static format as of October 1, 2020. If you require technical support for a Wrox book please contact http://hub.wiley.com
Old January 26th, 2006, 01:34 PM
Authorized User
Join Date: Jan 2006
Posts: 10
Thanks: 0
Thanked 0 Times in 0 Posts
Default Chapter 9 (Looping) Try It Out


I would like to preface my question by letting you know that I am prety much an uber-n00b when it comes to ASP.NET; however, I thought I would ask this question anyway.

I am working on the Try It Out on p. 325. I attempted to type the code out, and while doing so received several (Type 'Item' is not defined) warnings. For instance:

Dim conn As New SqlConnection(ConfigurationManager.ConnectionStrin gs("WroxUnited").ConnectionString)

The Intellisense kept giving me warnings that these items were undefined. I continued on with the exercise, and see that item 4. says to add the two import statements at the top of the page.

This got rid of the warnings as soon as I typed them. I guess my question would be: Why not have these as item 3, and type the code in item 4? Maybe I am missing something, but it seems if they had been switched I would not have received those warnings...It was kind of frustrating.

I don't mean to come across as being critical. I love the book, and am attempting a cover to cover read. So far it has been great...

Old January 27th, 2006, 12:06 PM
Wrox Author
Join Date: Jun 2004
Posts: 59
Thanks: 0
Thanked 0 Times in 0 Posts

   Nope you're absolutely correct. I've been updating the book for C# (my chapters only) and I've noted the occasional oddity like this and tried to iron them out. It's not really and error, but hopefully we can get it corrected in a reprint. It would make more sense to do it the other way around.


Chris Ullman
Programmer/Technical Author
Old January 27th, 2006, 01:54 PM
Authorized User
Join Date: Dec 2003
Posts: 46
Thanks: 0
Thanked 1 Time in 1 Post

You're right, it's dumb, and I take full responsibility for this one, and why I put them that way around I'll never know. You can blame one, or all of:

1. Gross stupidity
2. I have no idea what I was doing
3. The technical editor is blind
4. Too much malt whisky

These sort of things are interesting in hindsight; it's such a simple thing, it's always surprising when it slips through. And there's no need to apologise - you should be critical of things like this. Errors do creep into manuscripts, but this sort of thing brings more confusion that an error because it's less obvious as to whether there really is a problem or not.

So sorry for confusing you, and as Chris says, we'll try and get this corrected in reprints and the C# version


Similar Threads
Thread Thread Starter Forum Replies Last Post
Looping ssaranam SQL Server 2005 2 April 17th, 2008 01:40 AM
Looping deepsea007 XSLT 1 June 14th, 2007 12:13 PM
Looping..? dedex C# 2 January 6th, 2005 11:24 PM
Chapter 3: Looping through folders error DolphinBay BOOK: Beginning VB.NET 2nd Edition/Beginning VB.NET 2003 2 April 7th, 2004 05:41 AM
Chapter 3: Looping through folders error DolphinBay VB.NET 2002/2003 Basics 1 January 23rd, 2004 10:37 AM

Powered by vBulletin®
Copyright ©2000 - 2020, Jelsoft Enterprises Ltd.
Copyright (c) 2020 John Wiley & Sons, Inc.