Wrox Programmer Forums
BOOK: ASP.NET Website Programming Problem-Design-Solution
This is the forum to discuss the Wrox book ASP.NET Website Programming: Problem - Design - Solution, Visual Basic .NET Edition by Marco Bellinaso, Kevin Hoffman; ISBN: 9780764543869
Welcome to the p2p.wrox.com Forums.

You are currently viewing the BOOK: ASP.NET Website Programming Problem-Design-Solution section of the Wrox Programmer to Programmer discussions. This is a community of software programmers and website developers including Wrox book authors and readers. New member registration was closed in 2019. New posts were shut off and the site was archived into this static format as of October 1, 2020. If you require technical support for a Wrox book please contact http://hub.wiley.com
Old September 1st, 2004, 12:32 PM
Registered User
Join Date: Aug 2004
Posts: 6
Thanks: 0
Thanked 0 Times in 0 Posts
Default thePhile (VB) file folder structure...

...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. :)


Old September 1st, 2004, 08:24 PM
Friend of Wrox
Join Date: Jun 2003
Posts: 917
Thanks: 0
Thanked 0 Times in 0 Posts

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.


Similar Threads
Thread Thread Starter Forum Replies Last Post
All file name in selected folder VB.net Venkatesan VS.NET 2002/2003 0 February 8th, 2007 02:17 AM
Still confused Folder structure eureka BOOK: ASP.NET Website Programming Problem-Design-Solution 5 September 14th, 2004 11:37 PM
Namespace vs. Folder Structure (Help Englere) groupmatch BOOK: ASP.NET Website Programming Problem-Design-Solution 14 September 8th, 2004 08:05 AM
C# folder and project structure organicglenn BOOK: ASP.NET Website Programming Problem-Design-Solution 3 September 7th, 2004 09:47 PM

Powered by vBulletin®
Copyright ©2000 - 2020, Jelsoft Enterprises Ltd.
Copyright (c) 2020 John Wiley & Sons, Inc.