You canot do this using the SiteMapDataSource control because you cannot
specify which XML file it uses for it's data, it has to use web.sitemap.
However the menu control can use any XML data source, not just the
SiteMapDataSource control, so you could for example use a different
XMLDataSource control in each master page and point that at whatever Site Map
XML file you want. I have even seen an SQL based site map datasource control
that someone created.
"mike" wrote:
> 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?
>
>
|