itechcs: Glad I could help! LOL :-)
Yes, Thank you! ^_^
Makes sense that master pages can't be shared across multiple sites. However, couldn't you make each of the two sites it's own VS Project under the same Solution? I've never tried it, but maybe that would allow you to share Master pages?
Nope, as soon as the master page is outside the IIS Web Application, IIS denies it. It does the same thing with Code files. I was unable to have App_Code in my shared directory because IIS does not support having code outside the web application.
However if you mean having the other websites be "child" websites, that is something I haven't really thought of, but I would want anyone browsing into the child website to automagically be redirected to the proper domain name. Shouldn't be too hard to do.
The only problem I am having with this method is that I am picturing a web directory structure like follows:
Which is something else I'd rather not do. At this point I'm having to settle with having my Login Pages be copied onto each web domain/site and also my OGL. Since the login pages won't ever really change (they are only for me and one other person to log in and change/edit content) and since the OGL I can eventually put into a shared DB, it shouldn't be too big a problem. And it should entice me to learn Stored and CLI procedures for SQL sooner rather then later as most of the code I will be sharing is just that, SQL stuff.
Thankfully the larger directories I needed to share can be, like the themes and images.
-Wilson Gearld Mead III
www.rangoric.com (Rather Blah)
blog.rangoric.name (Closer to Not Blah)