在ASP.NET Core中用LINQ to XML生成订单父子表XML

Hey there! It looks like you've got the basics of generating XML for your orders down, but you're stuck on nesting the associated OrderItems as child entities. Let's walk through how to adjust your code to get that parent-child structure working.

First, let's break down the issue: you're already fetching both orders and order items from your repositories, but you aren't linking them together or embedding the items under their corresponding order in the XML. Here's how to fix that:

Modified Code with OrderItems Included #

[HttpGet("{id}")]
public async Task<IActionResult> CreateXml(Guid id)
{
    // Fetch all orders and filter down to the target(s) matching your ID
    var allOrders = await _ordersRepository.GetOrders();
    var targetOrders = allOrders.Where(x => x.RolCodEst == id).ToList();
    
    // Fetch all order items to match with orders
    var allOrderItems = await _orderItemsRepository.GetOrderItems();

    // Build the XML with nested order items
    var ordersXml = new XElement("doc",
        from order in targetOrders
        select new XElement("table", new XAttribute("name", "orders"),
            new XElement("row",
                // Order fields (keep your existing ones)
                new XElement("field", new XAttribute("name", "Id"), order.Id),
                new XElement("field", new XAttribute("name", "Year"), order.Year),
                
                // Add nested table for order items
                new XElement("table", new XAttribute("name", "order_items"),
                    from item in allOrderItems
                    // Match items to their parent order (adjust "OrderId" to your actual foreign key field)
                    where item.OrderId == order.Id
                    select new XElement("row",
                        // Add your OrderItem fields here (customize based on your entity)
                        new XElement("field", new XAttribute("name", "Id"), item.Id),
                        new XElement("field", new XAttribute("name", "ProductName"), item.ProductName),
                        new XElement("field", new XAttribute("name", "Quantity"), item.Quantity),
                        new XElement("field", new XAttribute("name", "UnitPrice"), item.UnitPrice)
                    )
                )
            )
        )
    );

    // Remaining code to save and return the XML stays mostly the same
    XDocument xdoc = new XDocument(new XDeclaration("1.0", "ISO-8859-1", null), ordersXml);
    string timestamp = DateTime.Now.ToString("yyyyMMddhhmmss");
    var xmlDir = Path.Combine(_hosting.ContentRootPath, "Xml");
    
    if (!Directory.Exists(xmlDir))
        Directory.CreateDirectory(xmlDir);
    
    string filePath = Path.Combine(xmlDir, $"0_dati_{timestamp}.xml");
    xdoc.Save(filePath);
    
    return Ok(ordersXml);
}

Key Changes Explained #

• Linking Orders to Items: We use where item.OrderId == order.Id to filter order items that belong to the current order. Make sure OrderId matches the actual foreign key property on your OrderItem entity.
• Nested Table Structure: Inside each order's <row> element, we add a new <table> for order_items, which contains all the corresponding item rows. This creates the parent-child relationship in the XML.
• Optional Efficiency Boost: If your repository supports eager loading (like Entity Framework Core's Include), you can fetch orders with their items in one query instead of two. For example:

  var targetOrders = await _ordersRepository.GetOrders()
      .Include(o => o.OrderItems) // Bring in associated items directly
      .Where(x => x.RolCodEst == id)
      .ToList();
  

  Then you can replace allOrderItems with order.OrderItems in the XML generation loop, which is cleaner and more efficient.

Customization Tips #

• Adjust the <field> elements for order_items to match the actual properties on your OrderItem entity (e.g., add Discount, TotalPrice, etc.).
• If id should only return a single order, replace Where with FirstOrDefaultAsync and add a check for null to return a NotFound response if the order doesn't exist.

内容的提问来源于stack exchange，提问作者gigiLaTrottola