The book did not mention removing the namespace portion of the code before creating the MyBasePage. If the template retains the namespace portion, subfolders such as About and Reviews would contain namespaces Site.About and Site.Reviews. But by including the namespace, the code is not in scope with the BasePage class which is in the Site namespace.

I removed the namespace in the template I created for MyBasePage and the "Try it Out" on pages 249-252 creates an issue because of the Default classes all being in the Site namespace.

The book mentions on pages 251 & 252 that the Visual Basic versions will cause errors due to the Default reserved word, but I'm using C#. The errors I'm getting are due to the Default class being in the same namespace. I also happened to notice that the code I downloaded from WROX has the Default class described as _Default in the Default.aspx.cs in the main folder. I'm confused how this could work together.

Have I missed an important issue? I was expecting to see some posts about this here, which leads me to believe that I've missed something.

Hi Eric,

You could leave the namespace in the template, and then simply add a using statement for the namespace of the base page.

That way, your pages will have unique names, while you can still bring in the BasePage in scope.

Hope this helps,

Imar


---------------------------------------
Imar Spaanjaars
http://Imar.Spaanjaars.Com
Everyone is unique, except for me.
Author of Beginning ASP.NET 3.5 : in C# and VB, ASP.NET 2.0 Instant Results and Dreamweaver MX 2004
Want to be my colleague? Then check out this post.