The class is derived from the SiteMapProvider class and is the default site map provider for ASP.NET. The class generates site map trees from XML files with the file name extension .sitemap.
Assembly: System.Web (in System.Web.dll)
[AspNetHostingPermissionAttribute(SecurityAction.LinkDemand, Level = AspNetHostingPermissionLevel.Minimal)] [AspNetHostingPermissionAttribute(SecurityAction.InheritanceDemand, Level = AspNetHostingPermissionLevel.Minimal)] public class XmlSiteMapProvider : StaticSiteMapProvider, IDisposable
The class loads site map data from an XML file that follows a known schema. The site map data is bounded by <siteMap> tags and consists of nested <siteMapNode> tags. Two constraints are imposed by the SiteMapProvider and classes on the structure of the site map data:
Only one root node can exist.
For SiteMapNode objects that specify URLs, the URLs must be unique within the scope of the provider. (For nodes that do not specify URLs, all keys must be unique.)
The following code example shows an example of an XML file that can be used with the .
<siteMap> <siteMapNode title="RootNode" description="This is the root node of the site map. There can be only one root node." url="Page1.aspx" > <siteMapNode title="ChildofRootNode" description="Descriptions do not have to be unique." url="Page2.aspx"> <siteMapNode title="ChildOfChildNode" description="SiteMapNode objects can be nested to any level." url="Page3.aspx"/> </siteMapNode> <siteMapNode title="ChildofRootNode" description="Descriptions do not have to be unique." url="Page4.aspx"/> </siteMapNode> </siteMap>
The is the default provider for ASP.NET and it reads XML data from a file named Web.sitemap that is located within the directory structure of the ASP.NET application. By default, the Web.sitemap file is located at the application root; however, if you want to change the name or location of the file from which the loads data, you can override the default configuration in your Web.config file. By overriding the default configuration settings in your Web.config file, you can tailor the behavior of the for each ASP.NET application, as necessary.
The following code example demonstrates an example Web.config file, where the is still used, but a different site map file is used. Because all providers in a SiteMapProviderCollection object must be named uniquely, the one that is specified in the Web.config file uses a name other than the default but is also set as the default provider so that it will be used instead of the that is specified in the default ASP.NET configuration.
You can change the name of the site navigation data file, but you cannot change its extension. The only reads data from files that are named with the file name extension .sitemap.
<siteMap defaultProvider="MyXmlSiteMapProvider" enabled="true"> <providers> <add name="MyXmlSiteMapProvider" description="SiteMap provider that reads in .sitemap files." type="System.Web.XmlSiteMapProvider, System.Web, Version=2.0.3600.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" siteMapFile="CustomWeb.sitemap" /> </providers> </siteMap>
Windows 7, Windows Vista, Windows XP SP2, Windows XP Media Center Edition, Windows XP Professional x64 Edition, Windows XP Starter Edition, Windows Server 2008 R2, Windows Server 2008, Windows Server 2003, Windows Server 2000 SP4, Windows Millennium Edition, Windows 98
The .NET Framework and .NET Compact Framework do not support all versions of every platform. For a list of the supported versions, see .NET Framework System Requirements.