HGo*_*mez 5 c# xml asp.net wcf document
我在C#中编写了一个简单的WCF Web服务,它从数据库中返回记录.
WCF使用以下方法:getQuestionnaireForID?id=(questionnaireID).Webservice从数据库返回所有正确的记录,但它们看起来顺序错误.
这是我希望XML的顺序:
<QuestionnaireXML xmlns="http://schemas.datacontract.org/2004/07/QuestionnaireDescriptor" xmlns:i="http://www.w3.org/2001/XMLSchema-instance">
<QuestionnaireName>Sample Questionnaire</QuestionnaireName>
<Questions>
<Question>
<QuestionID>297</QuestionID>
<QuestionName>What is your favorite type of tree?</QuestionName>
<Answers>
<Answer>
<AnswerTitle>Beech</AnswerTitle>
</Answer>
<Answer>
<AnswerTitle>Oak</AnswerTitle>
</Answer>
</Answers>
</Question>
<Question>
<QuestionID>298</QuestionID>
<QuestionName>Windows or Mac?</QuestionName>
<Answers>
<Answer>
<AnswerTitle>Mac</AnswerTitle>
</Answer>
<Answer>
<AnswerTitle>Windows</AnswerTitle>
</Answer>
</Answers>
</Question>
</Questions>
</QuestionnaireXML>
Run Code Online (Sandbox Code Playgroud)
但相反,它目前按以下顺序返回:
<QuestionnaireXML xmlns="http://schemas.datacontract.org/2004/07/QuestionnaireDescriptor" xmlns:i="http://www.w3.org/2001/XMLSchema-instance">
<QuestionnaireName>Hello sir how do you do today?</QuestionnaireName>
<Questions>
<Question>
<Answers>
<Answer>
<AnswerTitle>Beech</AnswerTitle>
</Answer>
<Answer>
<AnswerTitle>Oak</AnswerTitle>
</Answer>
</Answers>
<QuestionID>297</QuestionID>
<QuestionName>What is your favorite type of tree?</QuestionName>
</Question>
<Question>
<Answers>
<Answer>
<AnswerTitle>Mac</AnswerTitle>
</Answer>
<Answer>
<AnswerTitle>Windows</AnswerTitle>
</Answer>
</Answers>
<QuestionID>298</QuestionID>
<QuestionName>Windows or Mac?</QuestionName>
</Question>
</Questions>
</QuestionnaireXML>
Run Code Online (Sandbox Code Playgroud)
我不确定这是由于没有样式的XML文档还是因为我的循环顺序错误.这是我的WCF xml描述符.
[DataContract]
public class QuestionnaireXML
{
OsqarSQL getData;
DataTable DT;
private String _questionnaireName;
private List<Question> _Question = new List<Question>();
public QuestionnaireXML(int QuestionnaireID)
{
// Loop through datatable for questionIDs and load the questions
getData = new OsqarSQL();
_questionnaireName = getData.GetQuestionnaireName(QuestionnaireID);
DT = getData.GetQuestionIDWCF(QuestionnaireID);
for (int i = 0; i < DT.Rows.Count; i++)
{
_Question.Add(new Question(Int32.Parse(DT.Rows[i][0].ToString())));
}
}
// Define DataMembers for XML output
[DataMember]
public String QuestionnaireName
{
get { return _questionnaireName; }
set { _questionnaireName = value; }
}
[DataMember]
public List<Question> Questions
{
get { return _Question; }
set { _Question = value; }
}
}
[DataContract]
public class Question
{
private Int32 _questionId;
private String _questionName;
OsqarSQL getData;
DataTable DT;
DataTable AT;
private List<Answer> _Answer = new List<Answer>();
public Question(int QuestionID)
{
getData = new OsqarSQL();
DT = getData.GetQuestionNameWCF(QuestionID);
_questionId = (int)DT.Rows[0][0];
_questionName = DT.Rows[0][1].ToString();
AT = getData.GetAnswerTitle(QuestionID);
for (int i = 0; i < AT.Rows.Count; i++)
{
_Answer.Add(new Answer(Int32.Parse(AT.Rows[i][0].ToString())));
}
}
// Define DataMembers for XML output
[DataMember]
public Int32 QuestionID
{
get { return _questionId; }
set { _questionId = value; }
}
[DataMember]
public String QuestionName
{
get { return _questionName; }
set { _questionName = value; }
}
[DataMember]
public List<Answer> Answers
{
get { return _Answer; }
set { _Answer = value; }
}
}
[DataContract]
public class Answer
{
private Int32 _answerId;
private String _answerTitle;
OsqarSQL getData;
DataTable DT;
// Constructor Logic
public Answer(int AnswerID)
{
getData = new OsqarSQL();
DT = getData.GetAnswerTitleWcf(AnswerID);
_answerTitle = DT.Rows[0][1].ToString();
}
// Define DataMembers for XML output
[DataMember]
public String AnswerTitle
{
get { return _answerTitle; }
set { _answerTitle = value; }
}
}
Run Code Online (Sandbox Code Playgroud)
我该如何解决这个问题?在尝试解析XML时会导致问题吗?
这是我希望XML的顺序:
为什么?这有必要吗?我打赌,几乎可以肯定没必要.
默认情况下,WCF DataContractSerializer按字母顺序序列化.您会注意到您看到的XML具有按字母顺序排列的节点.列出您的类属性的顺序无关紧要.
如有必要,您可以使用该Order属性指定元素的顺序(请参阅MSDN数据成员顺序).
另一种选择是使用XMLSerializer,它更灵活但不像DataContractSerializer那么简单.
除非真正需要重新订购这些元素,否则我不会关心它.