I hope this is not a DUMB question:

In the book page 57 it says:

To create this class, we add a class library project called PhilePageBase to our main solution. The default namespace should be Wrox.ThePhile.Web and the class file is called PhilePage.vb.

Where I go to set the default namespace to Wrox.ThePhile.Web?

In properties window I only see Custom Tool Namespace.

I don't think this is it.

Because when I set this and I tried to Imports Wrox.ThePhile.Web from another form I get the squiggly line under it.


I looked in 5 other books to see how and where to set the default namespace and no book mentions this.

How can I successful set the default namespace??????
HELP ME PLEASE :(:(

The term "default namespace" is used by C# programmers - it's one of the project properties in C#.

In VB, you have a "root namespace" for your project, and it should be set to "Wrox". This effectively gets put onto the front of the namespace you specify in PhilePage.vb. So in PhilePage.vb, you don't specify the "Wrox.". He's the firest few lines of PhilePage.vb:

Imports System
Imports System.Web
Imports System.Web.UI
Imports System.Diagnostics

Imports Wrox.WebModules
Imports Wrox.WebModules.Accounts.Business

Namespace ThePhile.Web ' LOOK HERE

  Public Class PhilePage
    Inherits System.Web.UI.Page

I wrote the above code and get a swiggly line at Imports Wrox.WebModules.
What is my problem?

Thank you for your reply. Please help me again.

You don't have a reference to the DLLs of each module. This is a chicken-and-egg problem. You need a reference to each module's DLL to compile the project, but you can't make the DLLs until you first reference them!

The secret lies in the exact order of compilation. At each step, you only need to reference the items that have already been built. This assumes you haven't tampered with the order! It's possible to tamper with the order by accident.

If you do have the DLLs that came in the code download, the whole thing is simple because you will already have DLLs to match the references. At least, this would be fine if those DLLs work for you (this might depend on whether you have the same version of VS as the one used by the authors). As luck would have it, I couldn't use the author's DLLs, so I deleted them all and started again.

This is the hard manual procedure needed if you don't have the DLLs that came in the code download (or if you can't use those DLLs):
First, get in the habit of using Build..Rebuild Solution (at least until you get all the DLLs built). It will probably fail the first time (and maybe the first dozen times). After each failure, you can go to the Solution Explorer, find the references node, open that node, then see which references are broke and set them again. You probably can't fix them all the first time - you can only fix the references for the modules you have already built successfully. Fix as many as you can, and do another Rebuild Solution. Keep doing this until you get them all built.

Eric

Just FYI, you can right-click on the class library Project and then Properties, you'll be able to enter the default namespace there (+Assembly)