我正在使用MVC Web API,其中一個函數需要將SQL DB結果轉換爲XML文件。以特定格式獲取XML c#
private string DbToXml(int fileID)
{
DataSet ds = new DataSet("Requirements");
string connetionString = ConfigurationManager.ConnectionStrings["DemoConnectionString"].ConnectionString;
string XML;
using (SqlConnection connection = new SqlConnection(connetionString))
{
string sql = "SELECT RequirementLabel as ID, VagueWord, Suggestion, Explanation, VaguePhrase, ContentText, VagueTypeText FROM [Test].[dbo].[Vague_Terms_View] where FileID=" + fileID;
string XML_Output_Path = System.Configuration.ConfigurationManager.AppSettings.Get("XML_Output_Path");
connection.Open();
SqlDataAdapter adapter = new SqlDataAdapter(sql, connection);
adapter.Fill(ds, "Requirement");
var sb = new StringBuilder();
XmlWriter xmlWrite = XmlWriter.Create(sb);
ds.WriteXml(xmlWrite);
XML = ds.GetXml();
}
我從下面的代碼中獲得XML,這是正確的。
<?xml version="1.0" encoding="utf-8"?>
<Requirements>
<Requirement>
<ID>Req97</ID>
<VagueWord>or</VagueWord>
<Suggestion>Keep each requirement in a single sentence.</Suggestion>
<Explanation>Suggests that you are combining requirements. Requirements that contain conjunctions/disjunctions (AND/OR) are dangerous and can lead to downstream problems in defining scope of the requirement.</Explanation>
<VaguePhrase>Marketing or Servicing</VaguePhrase>
<ContentText>If a user is identified as Marketing or Servicing, then the Campaign Management (CM) hyperlink should be displayed.</ContentText>
<VagueTypeText>Not Standard</VagueTypeText>
</Requirement>
<Requirement>
<ID>Req97</ID>
<VagueWord>should</VagueWord>
<Suggestion>Use 'shall/must/will' for requirements,</Suggestion>
<Explanation>Is often ambiguous, or inappropriate. Some readers will interpret these as optional or advisory, others as required.</Explanation>
<ContentText>If a user is identified as Marketing or Servicing, then the Campaign Management (CM) hyperlink should be displayed.</ContentText>
<VagueTypeText>Not Standard</VagueTypeText>
</Requirement>
<Requirement>
<ID>Req98</ID>
<VagueWord>Unless</VagueWord>
<Suggestion>Specify each conditions explicitly. One condition per requirement.</Suggestion>
<Explanation>Is an escape clause. Requirements with escape clauses are not testable. The word implies additional condition to the requirement.</Explanation>
<ContentText>Unless Sleep, Latency, Noise, or apply conditions are present, the data transmissions will contain the code for Normal Operation.</ContentText>
<VagueTypeText>Not Standard</VagueTypeText>
</Requirement>
</Requirements>
但現在我需要轉換XML,檢查需求節點內的ID元素。如果它在Requirement節點下面重複,則將其重命名爲Requirement節點內的所有其他元素,以便追加id = 1,數字依此類推。 以上XML的預期輸出如下所示。
<?xml version="1.0" encoding="utf-8"?>
<Requirements>
<Requirement>
<ID "id=1">Req97</ID>
<VagueWord "id=1">or</VagueWord>
<Suggestion "id=1">Keep each requirement in a single sentence.</Suggestion>
<Explanation "id=1">Suggests that you are combining requirements. Requirements that contain conjunctions/disjunctions (AND/OR) are dangerous and can lead to downstream problems in defining scope of the requirement.</Explanation>
<VaguePhrase "id=1">Marketing or Servicing</VaguePhrase>
<ContentText "id=1">If a user is identified as Marketing or Servicing, then the Campaign Management (CM) hyperlink should be displayed.</ContentText>
<VagueTypeText "id=1">Not Standard</VagueTypeText>
</Requirement>
<Requirement>
<ID "id=2">Req97</ID>
<VagueWord "id=2">should</VagueWord>
<Suggestion "id=2">Use 'shall/must/will' for requirements,</Suggestion>
<Explanation "id=2">Is often ambiguous, or inappropriate. Some readers will interpret these as optional or advisory, others as required.</Explanation>
<ContentText "id=2">If a user is identified as Marketing or Servicing, then the Campaign Management (CM) hyperlink should be displayed.</ContentText>
<VagueTypeText "id=2">Not Standard</VagueTypeText>
</Requirement>
<Requirement>
<ID>Req98</ID>
<VagueWord>Unless</VagueWord>
<Suggestion>Specify each conditions explicitly. One condition per requirement.</Suggestion>
<Explanation>Is an escape clause. Requirements with escape clauses are not testable. The word implies additional condition to the requirement.</Explanation>
<ContentText>Unless Sleep, Latency, Noise, or apply conditions are present, the data transmissions will contain the code for Normal Operation.</ContentText>
<VagueTypeText>Not Standard</VagueTypeText>
</Requirement>
</Requirements>
@C更快,我認爲將需要實現自己的序列。我嘗試了過去,這並不容易,你會得到一個性能問題。我會盡力與您分享我的代碼。 –
您的'id'屬性值需要用引號來表示這個有效的xml。爲什麼最後的節點沒有'id'屬性?如果不想完成您的示例,只需將其保持一致即可。 – Filburt
@fabiosilvalima請分享代碼,如果你有...這將是很大的幫助.. !!! –