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要素をチェックする必要があります。それが要件ノードの下で繰り返されている場合は、それを名前変更し、要件ノード内の他のすべての要素を追加してid = 1とし、numberも同様に変更します。 上記の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あなたが持っている場合、コードを共有してください...それは大きな助けになるでしょう.. !!! –