M
mike
I'm using ASP.NET 2.0 and IIS 6
I've got a business with 2 sites requiring separate intranet info.
Currently, I have 2 separate intranet sites set up in IIS. This leads
to having to double up on shared pages which I'd rather not have. Both
sites use a master page and a Menu control bound to a SiteMap.
When a user loads the intranet home page, I want the appropriate Master
Page to load. As both sites are on different subnets, I can detect the
site through Request.UserHostAddress and deliver the appropriate Master
Page.
My question is whether I can maintain 2 separate SiteMap files in the
one web site and associate one with each Master Page or will ASP.NET
crack it?
I've got a business with 2 sites requiring separate intranet info.
Currently, I have 2 separate intranet sites set up in IIS. This leads
to having to double up on shared pages which I'd rather not have. Both
sites use a master page and a Menu control bound to a SiteMap.
When a user loads the intranet home page, I want the appropriate Master
Page to load. As both sites are on different subnets, I can detect the
site through Request.UserHostAddress and deliver the appropriate Master
Page.
My question is whether I can maintain 2 separate SiteMap files in the
one web site and associate one with each Master Page or will ASP.NET
crack it?