...and VS project structure.

I am nowhere near an experienced vb.net developer yet; so correct me if i am wrong, but i find it confusing the "Wrox.WebModules" namespace code modules physically sits WITHIN the "Wrox.thePhile" namespace code modules, and yet in VS they are organized into separate projects. In 'chapter 2 - Design' they tend to indicate that these are two separate projects/areas (thePhile and WebModules) and that the "WebModules" code can be used/referenced by any other websites code. If so then why embed this code right within 'thePhile's' website folders? Wouldn't it make more sense to have a separate folder directory for the webmodules OUTSIDE thePhile's folder?

When i was reading this i thought it was a great idea. Keeping the Webmodules code (data and business) layer common to other websites while thePhile (presentation layer) can just 'reference' it as required.

Perhaps i am misunderstanding something here or would both methods be okay to implement?

Like i said, i'm not arguing the logic i'm just trying to understand it. :)

J

The folder structure isn't very important - that is, for now. ASP.NET 2.0 makes a radical change - the folder structure will determine the project, and not the other way around. If you just copy a file into a folder under your main folder, it is instantly made part of your project in 2.0.

I'm not sure how practical it is to reuse these modules. It gets sticky when you consider the security authorization code - you have to drag the base class with you and everything in the other rpoject will get ugly as you force it into ThePhile's security model.

Only the File Manager doesn't have a problem being reused, but you must always use Windows Authorization on that module if you want to reuse it.

Eric