structure for project consisting of MANY other projects

I thought I had a nice structure layout for my new solution, it was going to
be like this:
ManfStudio
    Shell
        trunk
        tags
        branches
    Common
        trunk
        tags
        branches
    Modules
        Inventory
            trunk
            tags
            branches
        FuncTest
            trunk
            tags
            branches

and on and on....

The problem I have encountered is that everytime I branch off the shell
trunk I need to update the shell's project references to common, all
modules, services, etc. This is getting very tedious already.

When you guys have a structure like this, what is the common way to lay it
out?

Thanks for any suggestions.

Regards,
Steve Klett
Received on Tue Apr 4 03:37:10 2006