Hi,
I'm having some trouble understanding how I should arrange the projects in the book.

At chapter 2 page 33 I created a new C# Class Library and named it Core. Then in chapter 3 the book wants me to create a Class Library project called PhilePageBase to the main solution.

What is the main solution? Do I have to create a project called ThePhile and then put the Core project inside it? Do I have to move the Core project into folder ThePhile/Modules?

Thanx for any help!

Hi again,

In chapter 3 at page 61 it says {..} that is part of our main solution that already contains our Core project and our ThePhile web application project.

What is "ThePhile" web application project? Do I have to create that to continue with the book?

Hi again :)

At page 63 it says: To build the code for this, we're going to GO BACK to our main web application project(ThePhile), and create a new directory(IF YOU HAVN'T ALREADY) called Controls.

When in the book does it say anything about creating a web application called ThePhile?!

This book sucks!!!

I encourage you to get the code download. Create the database by restoring from the backup file in the code download (don't use the sql script), then you should upgrade the whole solution to VS 2003 (assuming you're using this).

The book is NOT a complete step-by-step reference. They only point out certain things that are interesting. The code download has a lot more than what is covered in the book.

Eric

I'm going through the book and creating the solution piece by piece, using the download code as a guide. I've noticed some of the oddities you have pointed out. The Core thing was confusing to me. I have my main solution file, yet for some reason they want Core to have its own solution file as well. The Nav thing is weird. You don't really need the Nav control in its own project. - just add it to the web project and code it up.

And you are right - the book never expressly tells you to create a web project.

Solution files in VS are only convenient ways to organize projects, at least prior to ASP.NET 2.0 (which changes the rules a bit). Projects are used to organize files that will be compiled into a separate assembly. You can create as many solutions as you want, and they will hold 0 or more projects.

I typically like one overall solution that has all the other projects inside it - so I can rebuild the entire group.

And I typically have one smaller solution file to match each project. These are used if I just want to work with one project at a time - less clutter that way.

Don't get me started on the goofy Nav box! That's the first thing I factored out in my version of ThePhile. I went with a more conventional menu along the left edge. You can download my whole project if you want - search in this forum for ThePhileII.

Eric