Welcome Guest Search | Active Topics | Sign In | Register

Menu and SiteMap Localization Options
dan thomas
Posted: Friday, October 10, 2008 7:35:37 AM
Rank: Newbie
Groups: Member

Joined: 10/10/2008
Posts: 5
Is it possible to Localize a Menu bound to an asp.net SiteMap?

The following has a standard dotnet menu and an eo menu. The dotnet menu picks up the localized string XXXXXX the eo menu doesn't.

Web.sitemap:

<siteMap enableLocalization="true">
<siteMapNode roles="*">
<siteMapNode title="$resources:web.sitemap, Menu1Title, Menu Default" description="Menu 1" roles="Role 1">
<siteMapNode title="Menu 1.1" description="Menu 1.1" roles="Role 1" />
<siteMapNode title="Menu 1.2" description="Menu 1.2" roles="Role 1" />
</siteMapNode>
<siteMapNode resourceIdentifier="Menu2Title" title="Menu 2" description="Menu 2" roles="Role 2">
<siteMapNode title="Menu 2.1" description="Menu 2.1" roles="Role 2"/>
<siteMapNode title="Menu 2.2" description="Menu 2.2" roles="Role 2"/>
<siteMapNode title="Menu 2.3" description="Menu 2.3" roles="Role 2"/>
</siteMapNode>
<siteMapNode title="Menu 3" description="Menu 3" >
<siteMapNode title="Menu 3.1" description="Menu 3.1" />
<siteMapNode title="Menu 3.2" description="Menu 3.2" />
<siteMapNode title="Menu 3.3" description="Menu 3.3" />
</siteMapNode>
</siteMapNode>
</siteMap>

Default.aspx:

<%@ Page Language="C#" AutoEventWireup="true" CodeFile="Default.aspx.cs" Inherits="_Default" %>

<%@ Register assembly="EO.Web" namespace="EO.Web" tagprefix="eo" %>

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">

<html xmlns="http://www.w3.org/1999/xhtml">
<head runat="server">
<title></title>
</head>
<body>
<form id="form1" runat="server">

<div>

<asp:XmlDataSource ID="XmlDataSource1"
runat="server" DataFile="Web.sitemap">
</asp:XmlDataSource>


<asp:Menu ID="Menu1" runat="server" DataSourceID="siteMapDataSource">
</asp:Menu>

<asp:XmlDataSource ID="XmlDataSource2"
runat="server" DataFile="Web.sitemap" XPath="/*/*">
</asp:XmlDataSource>


<asp:SiteMapDataSource runat="server" ID="siteMapDataSource" ShowStartingNode="false" />



<eo:Menu ID="menu" runat="server" DataSourceID="XmlDataSource2"
ControlSkinID="Style1" HideRoleDisabledItems="True" Width="120px"
onitemdatabound="menu_ItemDataBound">
<TopGroup Orientation="Horizontal">
<Bindings>
<eo:DataBinding Property="Value" DataField="@title" >

</eo:DataBinding>
</Bindings>
</TopGroup>
</eo:Menu>

</div>
</form>
</body>
</html>


web.config:

.....
<siteMap defaultProvider="XmlSiteMapProvider" enabled="true">
<providers>
<add name="XmlSiteMapProvider"
description="Default SiteMap provider."
type="System.Web.XmlSiteMapProvider "
siteMapFile="Web.sitemap"
securityTrimmingEnabled="true" />
</providers>
</siteMap>
.......


Web.sitemap.resx:

<?xml version="1.0" encoding="utf-8"?>
<root>
<!--
Microsoft ResX Schema

Version 2.0

The primary goals of this format is to allow a simple XML format
that is mostly human readable. The generation and parsing of the
various data types are done through the TypeConverter classes
associated with the data types.

Example:

... ado.net/XML headers & schema ...
<resheader name="resmimetype">text/microsoft-resx</resheader>
<resheader name="version">2.0</resheader>
<resheader name="reader">System.Resources.ResXResourceReader, System.Windows.Forms, ...</resheader>
<resheader name="writer">System.Resources.ResXResourceWriter, System.Windows.Forms, ...</resheader>
<data name="Name1"><value>this is my long string</value><comment>this is a comment</comment></data>
<data name="Color1" type="System.Drawing.Color, System.Drawing">Blue</data>
<data name="Bitmap1" mimetype="application/x-microsoft.net.object.binary.base64">
<value>[base64 mime encoded serialized .NET Framework object]</value>
</data>
<data name="Icon1" type="System.Drawing.Icon, System.Drawing" mimetype="application/x-microsoft.net.object.bytearray.base64">
<value>[base64 mime encoded string representing a byte array form of the .NET Framework object]</value>
<comment>This is a comment</comment>
</data>

There are any number of "resheader" rows that contain simple
name/value pairs.

Each data row contains a name, and value. The row also contains a
type or mimetype. Type corresponds to a .NET class that support
text/value conversion through the TypeConverter architecture.
Classes that don't support this are serialized and stored with the
mimetype set.

The mimetype is used for serialized objects, and tells the
ResXResourceReader how to depersist the object. This is currently not
extensible. For a given mimetype the value must be set accordingly:

Note - application/x-microsoft.net.object.binary.base64 is the format
that the ResXResourceWriter will generate, however the reader can
read any of the formats listed below.

mimetype: application/x-microsoft.net.object.binary.base64
value : The object must be serialized with
: System.Runtime.Serialization.Formatters.Binary.BinaryFormatter
: and then encoded with base64 encoding.

mimetype: application/x-microsoft.net.object.soap.base64
value : The object must be serialized with
: System.Runtime.Serialization.Formatters.Soap.SoapFormatter
: and then encoded with base64 encoding.

mimetype: application/x-microsoft.net.object.bytearray.base64
value : The object must be serialized into a byte array
: using a System.ComponentModel.TypeConverter
: and then encoded with base64 encoding.
-->
<xsd:schema id="root" xmlns="" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:msdata="urn:schemas-microsoft-com:xml-msdata">
<xsd:import namespace="http://www.w3.org/XML/1998/namespace" />
<xsd:element name="root" msdata:IsDataSet="true">
<xsd:complexType>
<xsd:choice maxOccurs="unbounded">
<xsd:element name="metadata">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="value" type="xsd:string" minOccurs="0" />
</xsd:sequence>
<xsd:attribute name="name" use="required" type="xsd:string" />
<xsd:attribute name="type" type="xsd:string" />
<xsd:attribute name="mimetype" type="xsd:string" />
<xsd:attribute ref="xml:space" />
</xsd:complexType>
</xsd:element>
<xsd:element name="assembly">
<xsd:complexType>
<xsd:attribute name="alias" type="xsd:string" />
<xsd:attribute name="name" type="xsd:string" />
</xsd:complexType>
</xsd:element>
<xsd:element name="data">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="value" type="xsd:string" minOccurs="0" msdata:Ordinal="1" />
<xsd:element name="comment" type="xsd:string" minOccurs="0" msdata:Ordinal="2" />
</xsd:sequence>
<xsd:attribute name="name" type="xsd:string" use="required" msdata:Ordinal="1" />
<xsd:attribute name="type" type="xsd:string" msdata:Ordinal="3" />
<xsd:attribute name="mimetype" type="xsd:string" msdata:Ordinal="4" />
<xsd:attribute ref="xml:space" />
</xsd:complexType>
</xsd:element>
<xsd:element name="resheader">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="value" type="xsd:string" minOccurs="0" msdata:Ordinal="1" />
</xsd:sequence>
<xsd:attribute name="name" type="xsd:string" use="required" />
</xsd:complexType>
</xsd:element>
</xsd:choice>
</xsd:complexType>
</xsd:element>
</xsd:schema>
<resheader name="resmimetype">
<value>text/microsoft-resx</value>
</resheader>
<resheader name="version">
<value>2.0</value>
</resheader>
<resheader name="reader">
<value>System.Resources.ResXResourceReader, System.Windows.Forms, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</value>
</resheader>
<resheader name="writer">
<value>System.Resources.ResXResourceWriter, System.Windows.Forms, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</value>
</resheader>
<data name="Menu1Title" xml:space="preserve">
<value>XXXXXXX</value>
</data>
</root>
eo_support
Posted: Friday, October 10, 2008 7:48:09 AM
Rank: Administration
Groups: Administration

Joined: 5/27/2007
Posts: 24,194
Hi,

I believe SiteMap localization is supported and implemented by the SiteMapProvider, not by the control, so our Menu should pick it up automatically. I noticed that in your code your asp:Menu is bound to the SiteMapDataSource, which does go through SiteMapProvider; while our menu is bound to XmlDataSource, which does not go through SiteMapProvider. So that might be the problem. Try to set our menu's DataSourceID to siteMapDataSource and it should work.

Thanks
dan thomas
Posted: Friday, October 10, 2008 7:52:54 AM
Rank: Newbie
Groups: Member

Joined: 10/10/2008
Posts: 5
nice one - changing the datasource worked - should have spotted that really - thanks


You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.