I'm at the end of Chapter 3, where the core is complete and I should be 
able to view the home page draft.  I've eliminated all but one build 
error that turns up on line 10 in PhilePage.cs:

The type or namespace name 'Controls' does not exist in the class or 
namespace 'Wrox.ThePhile.Web'

Here's the first 10 lines:

using System;
using System.Web;
using System.Web.UI;
using System.Diagnostics;

namespace Wrox.ThePhile.Web
{
	public class PhilePage : System.Web.UI.Page
	{
		protected Wrox.ThePhile.Web.Controls.User.SiteHeader 
Header;

The word "Controls" on that last line is where it is choking [vs.net 
underlines it in blue].  I've compared the code to the book numerous 
times.  I have the assembly name and default namespace on the Controls 
module set to Wrox.ThePhile.Web.Controls like the book instructs.  I have 
the build order set to Core > Controls > PhilePageBase > ThePhile.  It's 
as if the Wrox.ThePhile.Web.Controls object doesn't exists / was never 
created.

Any ideas?  What would be the logical way to debug this?

Thank you.

-Russ

Hi Russ

I was the lead technical editor on ASP.NET Website Programming. The 
purpose of the book was to present a complete, working ASP.NET website -- 
and then look at highlights of how we got there, and why we took the 
decisions we did. It shows how to learn from this example, and how to 
reuse the code, so that you can build your own ASP.NET website.

From your message it looks like you have been following the text of the 
chapters and trying to build the site yourself. The book is not intended 
for this purpose. Even if you solve this particular problem the rest of 
the book will end up being pretty frustrating if you take this approach.

I strongly suggest that you get hold of the code download and set up the 
complete site, before exploring the process we went through to build it.

I hope this helps -- thank you for buying the book!

Regards

David

Great, David.  Thank you for the response.  Will do.

But [you knew a 'but' was coming], I'm a little disappointed.  A good 
skim and partial read of the first few pages gives the impression of a 
complete, tutorial-style book.  For example, wording like "We will be 
building a website for DVD and book enthusiasts", "We will build each 
module in standard order", and "...we will now look at how to build our 
solution" definitely sounds like a tutorial to me.

I was excited, thinking I finally found a step-by-step-type book amongst 
this fast-to-press, over-fluffed computer text book world.  Most people, 
myself included, learn much more by _doing_ than by reading paragraphs of 
text.  Glancing through the book I saw step-by-step code examples, 
chronologically building on previous examples, Visual Studio and 
Enterprise Manager screenshots, even the TOC outlined what appeared to be 
a tutorial-style.  There was once a time when computer text books were 
well-written, concise, step-by-step tutorials.  I can think of one 
example, circa 1985: the TurboTutor 2.0 manuals that came with Borland 
Turbo Pascal [Bruce F. Webster, Philippe Kahn, I think?].  Amazingly well-
written books that showed care and diligence and a tutorial style that 
has since been unrivaled.  When you were finished, after typing in all 
the code and compiling and executing each step along the way, you had a 
working application, and a head full of extensive, working understanding 
[not knowledge, "understanding"] that no teacher could ever teach you.

Where have these textbooks gone?  Want to make a zillon dollars, Wrox?  
Bring back this style of book.  Find a dusty, old copy of TurboTutor 2.0, 
and write some new books in that style.  Watch, as programmers worldwide, 
drop their O'Reilly loyalties, and flock to Wrox.  I learned more in 8 
pages of that book than in any computer textbook I've read in the last 10 
years.

"Tell me, and I will forget. Show me, and I may remember. Involve me, and 
I will learn."

Not to be totaly negative, you guys have some fantastic material, as 
modern computer textbooks go.  Keep up the good work.

Thanks.
-Russ


> Hi Russ

> I was the lead technical editor on ASP.NET Website Programming. The 
p> urpose of the book was to present a complete, working ASP.NET website -
- 
a> nd then look at highlights of how we got there, and why we took the 
d> ecisions we did. It shows how to learn from this example, and how to 
r> euse the code, so that you can build your own ASP.NET website.

> From your message it looks like you have been following the text of the 
c> hapters and trying to build the site yourself. The book is not 
intended 
f> or this purpose. Even if you solve this particular problem the rest of 
t> he book will end up being pretty frustrating if you take this approach.

> I strongly suggest that you get hold of the code download and set up 
the 
c> omplete site, before exploring the process we went through to build it.

> I hope this helps -- thank you for buying the book!

> Regards

> David

My only comment to this reply is from the back cover, "ASP.NET Website 
Programming shows you how to build an interactive website from design to 
deployment".

I may have a different take on what "shows you how to build" means. 
Basically from your response, the wording should have been "shows you how 
install a pre-build website and look at the code, but will not show you 
how to implement or use the code". I am sorry if this is harsh, but this 
is a very expensive book. It should have been advertised a bit differently.

Thanks,

Joe

> Hi Russ

> I was the lead technical editor on ASP.NET Website Programming. The 
p> urpose of the book was to present a complete, working ASP.NET website --
 
a> nd then look at highlights of how we got there, and why we took the 
d> ecisions we did. It shows how to learn from this example, and how to 
r> euse the code, so that you can build your own ASP.NET website.

> From your message it looks like you have been following the text of the 
c> hapters and trying to build the site yourself. The book is not intended 
f> or this purpose. Even if you solve this particular problem the rest of 
t> he book will end up being pretty frustrating if you take this approach.

> I strongly suggest that you get hold of the code download and set up the 
c> omplete site, before exploring the process we went through to build it.

> I hope this helps -- thank you for buying the book!

> Regards

> David