我调用一个方法来获取我的页面[参见GetPages（String xmlFullFilePath）]。 FromXElement方法应该将LitePropertyData元素反序列化为强类型LitePropertyData对象。相反，它在以下行失败：
return (T)xmlSerializer.Deserialize(memoryStream);
并给出以下错误：
<LitePropertyData xmlns=''> was not expected.
我做错了什么？我已经包含了我调用的方法和xml数据：
public static T FromXElement<T>(this XElement xElement)
{
using (var memoryStream = new MemoryStream(Encoding.ASCII.GetBytes(xElement.ToString())))
{
var xmlSerializer = new XmlSerializer(typeof(T));
return (T)xmlSerializer.Deserialize(memoryStream);
}
}
public static List<LitePageData> GetPages(String xmlFullFilePath)
{
XDocument document = XDocument.Load(xmlFullFilePath);
List<LitePageData> results = (from record in document.Descendants("row")
select new LitePageData
{
Guid = IsValid(record, "Guid") ?
record.Element("Guid").Value :
null,
ParentID = IsValid(record, "ParentID") ?
Convert.ToInt32(record.Element("ParentID").Value) :
(Int32?)null,
Created = Convert.ToDateTime(record.Element("Created").Value),
Changed = Convert.ToDateTime(record.Element("Changed").Value),
Name = record.Element("Name").Value,
ID = Convert.ToInt32(record.Element("ID").Value),
LitePageTypeID = IsValid(record, "ParentID") ?
Convert.ToInt32(record.Element("ParentID").Value) :
(Int32?)null,
Html = record.Element("Html").Value,
FriendlyName = record.Element("FriendlyName").Value,
Properties = record.Element("Properties") != null ? record.Element("Properties").Element("LitePropertyData").FromXElement<List<LitePropertyData>>() :
new List<LitePropertyData>()
}).ToList();
return results;
}
这是xml：
<?xml version="1.0" encoding="utf-8"?> <root> <rows>
<row>
<ID>1</ID>
<ImageUrl></ImageUrl>
<Html>Home page</Html>
<Created>01-01-2012</Created>
<Changed>01-01-2012</Changed>
<Name>Home page</Name>
<FriendlyName>home-page</FriendlyName>
</row>
<row xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<Guid>edeaf468-f490-4271-bf4d-be145bc6a1fd</Guid>
<ID>8</ID>
<Name>Unused</Name>
<ParentID>1</ParentID>
<Created>2006-03-25T10:57:17</Created>
<Changed>2012-07-17T12:24:30.0984747+01:00</Changed>
<ChangedBy />
<LitePageTypeID xsi:nil="true" />
<Html>
What is the purpose of this option? This option checks the current document for accessibility issues. It uses Bobby to provide details of whether the current web page conforms to W3C's WCAG criteria for web content accessibility.
Issues with Bobby and Cynthia
Bobby and Cynthia are free services that supposedly allow a user to expose web page accessibility barriers. It is something of a guide but perhaps a blunt instrument. I tested a few of the webpages that I have designed. Sure enough, my pages fall short and for good reason. I am not about to claim that Bobby and Cynthia are useless. Although it is useful and commendable tool, it project appears to be overly ambitious. Nevertheless, let me explain my issues with Bobby and Cynthia:
First, certain W3C standards for designing web documents are often too strict and unworkable. For instance, in some versions W3C standards for HTML, certain tags should not include a particular attribute, whereas in others they are requisite if the document is to be ???well-formed???. The standard that a designer chooses is determined usually by the requirements specification document. This specifies which browsers and versions of those browsers that the web page is expected to correctly display. Forcing a hypertext document to conform strictly to a specific W3C standard for HTML is often no simple task. In the worst case, it cannot conform without losing some aesthetics or accessibility functionality.
Second, the case of HTML documents is not an isolated case. Standards for XML, XSL, JavaScript, VBScript, are analogous. Therefore, you might imagine the problems when you begin to combine these languages and formats in an HTML document.
Third, there is always more than one way to skin a cat. For example, Bobby and Cynthia may flag those IMG tags that do not contain a TITLE attribute. There might be good reason that a web developer chooses not to include the title attribute. The title attribute has a limited numbers of characters and does not support carriage returns. This is a major defect in the design of this tag. In fact, before the TITLE attribute was supported, there was the ALT attribute. Most browsers support both, yet they both perform a similar function. However, both attributes share the same deficiencies. In practice, there are instances where neither attribute would be used. Instead, for example, the developer would write some JavaScript or VBScript to circumvent these deficiencies. The concern is that Bobby and Cynthia would not notice this because it does not ???understand??? what the JavaScript does.
</Html>
<FriendlyName>unused</FriendlyName>
<IsDeleted>false</IsDeleted>
<Properties>
<LitePropertyData>
<Description>Image for the page</Description>
<DisplayEditUI>true</DisplayEditUI>
<OwnerTab>1</OwnerTab>
<DisplayName>Image Url</DisplayName>
<FieldOrder>1</FieldOrder>
<IsRequired>false</IsRequired>
<Name>ImageUrl</Name>
<IsModified>false</IsModified>
<ParentPageID>3</ParentPageID>
<Type>String</Type>
<Value xsi:type="xsd:string">smarter.jpg</Value>
</LitePropertyData>
<LitePropertyData>
<Description>WebItemApplicationEnum</Description>
<DisplayEditUI>true</DisplayEditUI>
<OwnerTab>1</OwnerTab>
<DisplayName>WebItemApplicationEnum</DisplayName>
<FieldOrder>1</FieldOrder>
<IsRequired>false</IsRequired>
<Name>WebItemApplicationEnum</Name>
<IsModified>false</IsModified>
<ParentPageID>3</ParentPageID>
<Type>Number</Type>
<Value xsi:type="xsd:string">1</Value>
</LitePropertyData>
</Properties>
<Seo>
<Author>Phil Carney</Author>
<Classification />
<Copyright>Carnotaurus</Copyright>
<Description>
What is the purpose of this option? This option checks the current document for accessibility issues. It uses Bobby to provide details of whether the current web page conforms to W3C's WCAG criteria for web content accessibility.
Issues with Bobby and Cynthia
Bobby and Cynthia are free services that supposedly allow a user to expose web page accessibility barriers. It is something of a guide but perhaps a blunt instrument. I tested a few of the webpages that I have designed. Sure enough, my pages fall short and for good reason. I am not about to claim that Bobby and Cynthia are useless. Although it is useful and commendable tool, it project appears to be overly ambitious. Nevertheless, let me explain my issues with Bobby and Cynthia:
First, certain W3C standards for designing web documents are often too strict and unworkable. For instance, in some versions W3C standards for HTML, certain tags should not include a particular attribute, whereas in others they are requisite if the document is to be ???well-formed???. The standard that a designer chooses is determined usually by the requirements specification document. This specifies which browsers and versions of those browsers that the web page is expected to correctly display. Forcing a hypertext document to conform strictly to a specific W3C standard for HTML is often no simple task. In the worst case, it cannot conform without losing some aesthetics or accessibility functionality.
Second, the case of HTML documents is not an isolated case. Standards for XML, XSL, JavaScript, VBScript, are analogous. Therefore, you might imagine the problems when you begin to combine these languages and formats in an HTML document.
Third, there is always more than one way to skin a cat. For example, Bobby and Cynthia may flag those IMG tags that do not contain a TITLE attribute. There might be good reason that a web developer chooses not to include the title attribute. The title attribute has a limited numbers of characters and does not support carriage returns. This is a major defect in the design of this tag. In fact, before the TITLE attribute was supported, there was the ALT attribute. Most browsers support both, yet they both perform a similar function. However, both attributes share the same deficiencies. In practice, there are instances where neither attribute would be used. Instead, for example, the developer would write some JavaScript or VBScript to circumvent these deficiencies. The concern is that Bobby and Cynthia would not notice this because it does not ???understand??? what the JavaScript does.
</Description>
<Keywords>unused</Keywords>
<Title>unused</Title>
</Seo>
</row> </rows> </root>
修改
以下是我的实体：
public class LitePropertyData
{
public virtual string Description { get; set; }
public virtual bool DisplayEditUI { get; set; }
public int OwnerTab { get; set; }
public virtual string DisplayName { get; set; }
public int FieldOrder { get; set; }
public bool IsRequired { get; set; }
public string Name { get; set; }
public virtual bool IsModified { get; set; }
public virtual int ParentPageID { get; set; }
public LiteDataType Type { get; set; }
public object Value { get; set; }
}
[Serializable]
public class LitePageData
{
public String Guid { get; set; }
public Int32 ID { get; set; }
public String Name { get; set; }
public Int32? ParentID { get; set; }
public DateTime Created { get; set; }
public String CreatedBy { get; set; }
public DateTime Changed { get; set; }
public String ChangedBy { get; set; }
public Int32? LitePageTypeID { get; set; }
public String Html { get; set; }
public String FriendlyName { get; set; }
public Boolean IsDeleted { get; set; }
public List<LitePropertyData> Properties { get; set; }
public LiteSeoPageData Seo { get; set; }
/// <summary>
/// Saves the specified XML full file path.
/// </summary>
/// <param name="xmlFullFilePath">The XML full file path.</param>
public void Save(String xmlFullFilePath)
{
XDocument doc = XDocument.Load(xmlFullFilePath);
XElement demoNode = this.ToXElement<LitePageData>();
demoNode.Name = "row";
doc.Descendants("rows").Single().Add(demoNode);
doc.Save(xmlFullFilePath);
}
}
答案 0 :(得分：1)
我的建议是在.NET中创建对象，然后将其序列化为XML，并查看.NET创建的有效xml的格式。然后让你的XML看起来像那样。
此方法将LitePageData对象转换为XML。如果要检查它，可以将有效的xml保存到文件中，或者只是将其转储出来。
public static XElement GetXElementFromLitePageData(LitePageData objectToSerialize)
{
var xmlSerializer = new XmlSerializer(typeof(LitePageData));
var doc = new XDocument();
using (XmlWriter xmlWriter = doc.CreateWriter())
{
xmlSerializer.Serialize(xmlWriter, objectToSerialize);
}
return doc.Root;
}
答案 1 :(得分：1)
我实现了您的类，然后序列化了页面数据对象，并能够序列化为xml并返回。 如果您可以在.NET中创建对象，然后序列化它，您应该获得有效的XML。当您尝试反序列化时，请确保您的XML格式如下。
我对你没有提供但被引用的实体采取了一些自由：
[Serializable]
public class LitePropertyData
{
public virtual string Description { get; set; }
public virtual bool DisplayEditUI { get; set; }
public int OwnerTab { get; set; }
public virtual string DisplayName { get; set; }
public int FieldOrder { get; set; }
public bool IsRequired { get; set; }
public string Name { get; set; }
public virtual bool IsModified { get; set; }
public virtual int ParentPageID { get; set; }
public LiteDataType Type { get; set; }
public object Value { get; set; }
}
[Serializable]
public enum LiteDataType
{
String,
NotString,
}
[Serializable]
public class LitePageData
{
public String Guid { get; set; }
public Int32 ID { get; set; }
public String Name { get; set; }
public Int32? ParentID { get; set; }
public DateTime Created { get; set; }
public String CreatedBy { get; set; }
public DateTime Changed { get; set; }
public String ChangedBy { get; set; }
public Int32? LitePageTypeID { get; set; }
public String Html { get; set; }
public String FriendlyName { get; set; }
public Boolean IsDeleted { get; set; }
public List<LitePropertyData> Properties { get; set; }
public LiteSeoPageData Seo { get; set; }
}
[Serializable]
public class LiteSeoPageData
{
public string Author { get; set; }
public string Classification { get; set; }
public string CopyRight { get; set; }
public string Description { get; set; }
public string Keywords { get; set; }
public string Title { get; set; }
}
该计划如下：
static void Main(string[] args)
{
var type = LiteDataType.String;
var data1 = new LitePropertyData
{
Description = "LitePropertyData Description",
DisplayEditUI = true,
OwnerTab = 1,
DisplayName = "LitePropertyData Display Name",
FieldOrder = 2,
IsRequired = true,
Name = "LitePropertyData Name",
IsModified = false,
ParentPageID = 3,
Type = type,
Value = "LitePropertyData value"
};
var data2 = new LitePropertyData
{
Description = "LitePropertyData Description2",
DisplayEditUI = false,
OwnerTab = 4,
DisplayName = "LitePropertyData Display Name2",
FieldOrder = 5,
IsRequired = false,
Name = "LitePropertyData Name2",
IsModified = false,
ParentPageID = 6,
Type = type,
Value = "LitePropertyData value2"
};
var seo = new LiteSeoPageData
{
Author = "Seo Author",
Classification = "Seo class",
CopyRight = "Seo copyright",
Description = "Seo desc",
Keywords = "Seo keywords",
Title = "Seo Title"
};
var pageData = new LitePageData
{
Guid = Guid.NewGuid().ToString(),
ID = 7,
Name = "page data name",
ParentID = null,
Created = DateTime.Now,
CreatedBy = "me",
Changed = DateTime.UtcNow,
LitePageTypeID = 9,
Html = "this is not html",
FriendlyName = "casper",
IsDeleted = false,
Properties = new List<LitePropertyData> { data1, data2 },
Seo = seo
};
XElement xml = GetXElementFromLitePageData(pageData);
Save(@"C:\Users\Public\Documents\pageData2.xml", xml);
LitePageData deserializedPageData = GetLitePageDataFromXElement(xml);
Console.ReadLine();
}
/// <summary>
/// Saves the specified XML full file path.
/// </summary>
/// <param name="xmlFullFilePath">The XML full file path.</param>
public static void Save(String xmlFullFilePath, XElement xml)
{
var doc = new XDocument();
doc.Add(xml);
doc.Save(xmlFullFilePath);
}
public static XElement GetXElementFromLitePageData(LitePageData objectToSerialize)
{
var xmlSerializer = new XmlSerializer(typeof(LitePageData));
var doc = new XDocument();
using (XmlWriter xmlWriter = doc.CreateWriter())
{
xmlSerializer.Serialize(xmlWriter, objectToSerialize);
}
return doc.Root;
}
public static LitePageData GetLitePageDataFromXElement(XElement xml)
{
var xmlSerializer = new XmlSerializer(typeof(LitePageData));
return (LitePageData)xmlSerializer.Deserialize(xml.CreateReader());
}
这是xml：
<?xml version="1.0" encoding="utf-8"?>
<LitePageData xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<Guid>d5a94c0e-b39a-4bd0-9db3-4aa9c4273144</Guid>
<ID>7</ID>
<Name>page data name</Name>
<ParentID xsi:nil="true" />
<Created>2012-07-18T22:00:33.4522654-04:00</Created>
<CreatedBy>me</CreatedBy>
<Changed>2012-07-19T02:00:33.4532679Z</Changed>
<LitePageTypeID>9</LitePageTypeID>
<Html>this is not html</Html>
<FriendlyName>casper</FriendlyName>
<IsDeleted>false</IsDeleted>
<Properties>
<LitePropertyData>
<Description>LitePropertyData Description</Description>
<DisplayEditUI>true</DisplayEditUI>
<OwnerTab>1</OwnerTab>
<DisplayName>LitePropertyData Display Name</DisplayName>
<FieldOrder>2</FieldOrder>
<IsRequired>true</IsRequired>
<Name>LitePropertyData Name</Name>
<IsModified>false</IsModified>
<ParentPageID>3</ParentPageID>
<Type>String</Type>
<Value xsi:type="xsd:string">LitePropertyData value</Value>
</LitePropertyData>
<LitePropertyData>
<Description>LitePropertyData Description2</Description>
<DisplayEditUI>false</DisplayEditUI>
<OwnerTab>4</OwnerTab>
<DisplayName>LitePropertyData Display Name2</DisplayName>
<FieldOrder>5</FieldOrder>
<IsRequired>false</IsRequired>
<Name>LitePropertyData Name2</Name>
<IsModified>false</IsModified>
<ParentPageID>6</ParentPageID>
<Type>String</Type>
<Value xsi:type="xsd:string">LitePropertyData value2</Value>
</LitePropertyData>
</Properties>
<Seo>
<Author>Seo Author</Author>
<Classification>Seo class</Classification>
<CopyRight>Seo copyright</CopyRight>
<Description>Seo desc</Description>
<Keywords>Seo keywords</Keywords>
<Title>Seo Title</Title>
</Seo>
</LitePageData>
答案 2 :(得分：0)
我重构了将属性获取到GetProperties方法的逻辑。然后在调用新方法之前注释掉原始代码以在GetPages方法中填充Properties：
public static List<LitePropertyData> GetProperties(XElement record)
{
if (record.Element("Properties") == null) return new List<LitePropertyData>();
if (record.Descendants("Properties")== null) return new List<LitePropertyData>();
if (record.Descendants("Properties").Descendants("LitePropertyData") == null) return new List<LitePropertyData>();
List<LitePropertyData> properties =
(from property in record.Descendants("Properties").Descendants("LitePropertyData")
select new LitePropertyData
{
Description = property.Element("Description").Value,
DisplayEditUI = property.Element("DisplayEditUI").Value.ToBoolean(),
DisplayName = property.Element("DisplayName").Value,
FieldOrder = property.Element("FieldOrder").Value.ToInt32(),
IsModified = property.Element("IsModified").Value.ToBoolean(),
IsRequired = property.Element("IsRequired").Value.ToBoolean(),
Name = property.Element("Name").Value,
OwnerTab = property.Element("OwnerTab").Value.ToInt32(),
ParentPageID = property.Element("ParentPageID").Value.ToInt32(),
Type = (LiteDataType)property.Element("Type").Value.ToInt32(),
Value = property.Element("Value").Value,
}).ToList();
return properties;
}
/// <summary>
/// Gets the pages.
/// </summary>
/// <param name="xmlFullFilePath">The XML full file path.</param>
/// <returns></returns>
public static List<LitePageData> GetPages(String xmlFullFilePath)
{
XDocument document = XDocument.Load(xmlFullFilePath);
List<LitePageData> results = (from record in document.Descendants("row")
select new LitePageData
{
Guid = IsValid(record, "Guid") ?
record.Element("Guid").Value :
null,
ParentID = IsValid(record, "ParentID") ?
Convert.ToInt32(record.Element("ParentID").Value) :
(Int32?)null,
Created = Convert.ToDateTime(record.Element("Created").Value),
Changed = Convert.ToDateTime(record.Element("Changed").Value),
Name = record.Element("Name").Value,
ID = Convert.ToInt32(record.Element("ID").Value),
LitePageTypeID = IsValid(record, "ParentID") ?
Convert.ToInt32(record.Element("ParentID").Value) :
(Int32?)null,
Html = record.Element("Html").Value,
FriendlyName = record.Element("FriendlyName").Value,
Properties = GetProperties(record),
//record.Element("Properties") != null ? record.Element("Properties").FromXElement<List<LitePropertyData>>() :
// new List<LitePropertyData>()
}).ToList();
return results;
}