I'm trying to make a website like this
Base/Root web site/folder/web application project
this will contain all my web service references, my root web.config, my base classes, my root master page. it's namespace will be mycompany.myroot
then I want to create, say, 10 separate web application projects that reference the base web application project for things like web.config settings, virtual path provider, themes and styles, etc. They'll also have a nested master pages referencing the root master page. it's namespace will be mycompany.myroot.mysubapp
My question is is this the best way to do this? and how does it look as far as referencing each other and folder structure? Here's my best guess.
you have a WAP of root, namespace company.root, folder company/root
you have a WAP of subapp, namespace company.root.subapp1, folder company/subapp1
to work on subapp you have a solution referencing subapp1 and root
to work on root you have a solution of root and you have another build solution that references root and ALL subapps, everything.
Is this best practice? Will this work? How do I get subapp1's web.config to inherit from root's web.config
basically in deployment, subapp1 will be a subfolder of root...but during development I would like them separated as different WAPs but function as if they're subfolders of root correctly (i.e. using root's web service clients and web.config settings and such)
One question I'm not sure on the answer to is, how do i get myapp1's webconfig to inherit root's web.config during development
I'm using VS2008.TFS
Thanks,