Subweb / Subprojects VS2005

I have a web site which we use to service many customers. The base part of
the web site is the same for every customer. Then there are sub-webs for
each customer that contain customer specific pages only. How do we structur
e
the projects such that I don't need to build one solution which contains the
base web and every customer web while maintaining session accross all the
webs? One of the frustrating things about VS is that if it finds a sub web
it tries to compile it. So i remove the sub-web and everything compiles, bu
t
now how do I test the sub-web when I can't navigate through the base web?
More info...each web (base and customer) has a bunch of supporting
assemblies (service, data, rules, etc). The base web should not change ver
y
frequently but each sub-web (customer specific) will be on a different
release cycle. So I need to keep them separate.
I have read the Guthrie articles on VS2005 projects and while they get me
pretty close, they don't seem to address my issues.
I refuse to belive that this problem is uniqute and hopefully someone on the
ASP.NET / VS team has thought about this scenario. Any help would be much
appreciated.
Thanks,
curtSilence sucks, if I am off my rocker just tell me so ;-).
Thanks,
curt
"Curt Koppang" wrote:

> I have a web site which we use to service many customers. The base part o
f
> the web site is the same for every customer. Then there are sub-webs for
> each customer that contain customer specific pages only. How do we struct
ure
> the projects such that I don't need to build one solution which contains t
he
> base web and every customer web while maintaining session accross all the
> webs? One of the frustrating things about VS is that if it finds a sub we
b
> it tries to compile it. So i remove the sub-web and everything compiles,
but
> now how do I test the sub-web when I can't navigate through the base web?
> More info...each web (base and customer) has a bunch of supporting
> assemblies (service, data, rules, etc). The base web should not change v
ery
> frequently but each sub-web (customer specific) will be on a different
> release cycle. So I need to keep them separate.
> I have read the Guthrie articles on VS2005 projects and while they get me
> pretty close, they don't seem to address my issues.
> I refuse to belive that this problem is uniqute and hopefully someone on t
he
> ASP.NET / VS team has thought about this scenario. Any help would be much
> appreciated.
> Thanks,
> curt

Subweb in ASP.Net?

I'm not realy sure if this is called a "subweb" or not, but here's what I
want to do:
I have a website, smccabe.net
The pages on this site are accessed by the form
http://smccabe.net/somepage.aspx
What I would like to do is create a page accessed with the form:
http://somepage.smccabe.net
How do you do this with ASP.Net?
Thanks!
--SeldenYes, that form of addressing is called a subweb and requires the use of host
headers. Its an IIS configuration.
<%= Clinton Gallagher
NET csgallagher AT metromilwaukee.com
URL http://clintongallagher.metromilwaukee.com/
MAP http://wikimapia.org/#y=43038073&x=...38&z=17&l=0&m=h
"Selden" <seldenm@.msn.com> wrote in message
news:_663h.18156$gU6.7744@.tornado.socal.rr.com...
> I'm not realy sure if this is called a "subweb" or not, but here's what I
> want to do:
> I have a website, smccabe.net
> The pages on this site are accessed by the form
> http://smccabe.net/somepage.aspx
> What I would like to do is create a page accessed with the form:
> http://somepage.smccabe.net
> How do you do this with ASP.Net?
> Thanks!
> --Selden
>
Selden,
Actually, it's not really a subweb. A "subweb" would be
http://smccabe.net/somepage/ in IIS terminology. Usually when IIS refers to
a subweb it is referring to a logical entity packed as a FrontPage subweb,
which is basically a directory that has been compartmentalized for use by
the FrontPage Server Extensions and FrontPage publishing.
What you are referring to is a subdomain. You would first have to setup
the DNS settings in order to handle the subdomain so it points somewhere.
It's possible that you could have the server automatically point the entry
so that it exists within your site, but at a directory different from the
root. In orther words http://somepage.smccabe.net would map to
http://smccabe.net/somepage/ In some scenarious this becomes unstable
because you would have subdirectories of your root web being seen by the
application possibly as the root level of the site.
Basically, this is a server setup that you wouldn't do in ASP.Net.
Has to be configured through DNS and IIS itself.
Hope this helps,
Mark Fitzpatrick
Former Microsoft FrontPage MVP 199...2006
"Selden" <seldenm@.msn.com> wrote in message
news:_663h.18156$gU6.7744@.tornado.socal.rr.com...
> I'm not realy sure if this is called a "subweb" or not, but here's what I
> want to do:
> I have a website, smccabe.net
> The pages on this site are accessed by the form
> http://smccabe.net/somepage.aspx
> What I would like to do is create a page accessed with the form:
> http://somepage.smccabe.net
> How do you do this with ASP.Net?
> Thanks!
> --Selden
>
Thanks, you've cleared it up perfectly!
"Mark Fitzpatrick" <markfitz@.fitzme.com> wrote in message
news:u4y8q$FAHHA.204@.TK2MSFTNGP04.phx.gbl...
> Selden,
> Actually, it's not really a subweb. A "subweb" would be
> http://smccabe.net/somepage/ in IIS terminology. Usually when IIS refers
> to a subweb it is referring to a logical entity packed as a FrontPage
> subweb, which is basically a directory that has been compartmentalized for
> use by the FrontPage Server Extensions and FrontPage publishing.
> What you are referring to is a subdomain. You would first have to setup
> the DNS settings in order to handle the subdomain so it points somewhere.
> It's possible that you could have the server automatically point the entry
> so that it exists within your site, but at a directory different from the
> root. In orther words http://somepage.smccabe.net would map to
> http://smccabe.net/somepage/ In some scenarious this becomes unstable
> because you would have subdirectories of your root web being seen by the
> application possibly as the root level of the site.
> Basically, this is a server setup that you wouldn't do in ASP.Net.
> Has to be configured through DNS and IIS itself.
>
> --
> Hope this helps,
> Mark Fitzpatrick
> Former Microsoft FrontPage MVP 199...2006
>
> "Selden" <seldenm@.msn.com> wrote in message
> news:_663h.18156$gU6.7744@.tornado.socal.rr.com...
>

Subweb in ASP.Net?

I'm not realy sure if this is called a "subweb" or not, but here's what I
want to do:

I have a website, smccabe.net

The pages on this site are accessed by the form
http://smccabe.net/somepage.aspx
What I would like to do is create a page accessed with the form:

http://somepage.smccabe.net
How do you do this with ASP.Net?

Thanks!
--SeldenYes, that form of addressing is called a subweb and requires the use of host
headers. Its an IIS configuration.

<%= Clinton Gallagher
NET csgallagher AT metromilwaukee.com
URL http://clintongallagher.metromilwaukee.com/
MAP http://wikimapia.org/#y=43038073&x=...38&z=17&l=0&m=h
"Selden" <seldenm@.msn.comwrote in message
news:_663h.18156$gU6.7744@.tornado.socal.rr.com...

Quote:

Originally Posted by

I'm not realy sure if this is called a "subweb" or not, but here's what I
want to do:
>
I have a website, smccabe.net
>
The pages on this site are accessed by the form
http://smccabe.net/somepage.aspx
>
What I would like to do is create a page accessed with the form:
>
http://somepage.smccabe.net
>
How do you do this with ASP.Net?
>
Thanks!
--Selden
>
>

Selden,
Actually, it's not really a subweb. A "subweb" would be
http://smccabe.net/somepage/ in IIS terminology. Usually when IIS refers to
a subweb it is referring to a logical entity packed as a FrontPage subweb,
which is basically a directory that has been compartmentalized for use by
the FrontPage Server Extensions and FrontPage publishing.

What you are referring to is a subdomain. You would first have to setup
the DNS settings in order to handle the subdomain so it points somewhere.
It's possible that you could have the server automatically point the entry
so that it exists within your site, but at a directory different from the
root. In orther words http://somepage.smccabe.net would map to
http://smccabe.net/somepage/ In some scenarious this becomes unstable
because you would have subdirectories of your root web being seen by the
application possibly as the root level of the site.

Basically, this is a server setup that you wouldn't do in ASP.Net.
Has to be configured through DNS and IIS itself.

--
Hope this helps,
Mark Fitzpatrick
Former Microsoft FrontPage MVP 199?-2006

"Selden" <seldenm@.msn.comwrote in message
news:_663h.18156$gU6.7744@.tornado.socal.rr.com...

Quote:

Originally Posted by

I'm not realy sure if this is called a "subweb" or not, but here's what I
want to do:
>
I have a website, smccabe.net
>
The pages on this site are accessed by the form
http://smccabe.net/somepage.aspx
>
What I would like to do is create a page accessed with the form:
>
http://somepage.smccabe.net
>
How do you do this with ASP.Net?
>
Thanks!
--Selden
>
>

Thanks, you've cleared it up perfectly!

"Mark Fitzpatrick" <markfitz@.fitzme.comwrote in message
news:u4y8q$FAHHA.204@.TK2MSFTNGP04.phx.gbl...

Quote:

Originally Posted by

Selden,
Actually, it's not really a subweb. A "subweb" would be
http://smccabe.net/somepage/ in IIS terminology. Usually when IIS refers
to a subweb it is referring to a logical entity packed as a FrontPage
subweb, which is basically a directory that has been compartmentalized for
use by the FrontPage Server Extensions and FrontPage publishing.
>
What you are referring to is a subdomain. You would first have to setup
the DNS settings in order to handle the subdomain so it points somewhere.
It's possible that you could have the server automatically point the entry
so that it exists within your site, but at a directory different from the
root. In orther words http://somepage.smccabe.net would map to
http://smccabe.net/somepage/ In some scenarious this becomes unstable
because you would have subdirectories of your root web being seen by the
application possibly as the root level of the site.
>
Basically, this is a server setup that you wouldn't do in ASP.Net.
Has to be configured through DNS and IIS itself.
>
>
--
Hope this helps,
Mark Fitzpatrick
Former Microsoft FrontPage MVP 199?-2006
>
>
>
"Selden" <seldenm@.msn.comwrote in message
news:_663h.18156$gU6.7744@.tornado.socal.rr.com...

Quote:

Originally Posted by

>I'm not realy sure if this is called a "subweb" or not, but here's what I
>want to do:
>>
>I have a website, smccabe.net
>>
>The pages on this site are accessed by the form
>http://smccabe.net/somepage.aspx
>>
>What I would like to do is create a page accessed with the form:
>>
>http://somepage.smccabe.net
>>
>How do you do this with ASP.Net?
>>
>Thanks!
> --Selden
>>
>>

>
>