Comment exporter une DataGridView vers Excel avec des en-têtes de colonne en C#

What Makes IronXL the Ideal Choice?

IronXL simplifies Excel operations in .NET applications by providing an intuitive API that doesn't require Microsoft Excel installation. Unlike Interop-based solutions, IronXL runs independently, making it perfect for server environments and machines without Office.

The library handles all Excel formats including XLSX, XLS, and CSV, while maintaining data integrity and formatting throughout the export process. Developers can easily copy data, extend sheets, and delete or add rows without relying on Excel being installed.

Setting Up Your Windows Forms Project

First, create a new Windows Forms Application in Visual Studio. Once your project is ready, install IronXL through the NuGet Package Manager. Open the Package Manager Console and run:

Install-Package IronXL.Excel

After installation, add these essential namespaces to your form:

using IronXL;
using System;
using System.Data;
using System.Windows.Forms;

using IronXL;
using System;
using System.Data;
using System.Windows.Forms;

IRON VB CONVERTER ERROR developers@ironsoftware.com

These imports provide access to IronXL's Excel functionality, DataTable operations, and Windows Forms controls needed for the export process.

Creating the DataGridView with Sample Data

Let's build a simple interface with a DataGridView populated with a sample data source. You might also be importing data from a CSV or database, the same DataTable approach below works for imported datasets. Add a new DataGridView and a Button to your form through the Visual Studio designer, then use this code to set up the data:

private void Form1_Load(object sender, EventArgs e)
{
    // Example object usage
    object obj = "Initializing DataTable"; 
    Console.WriteLine(obj);
    // Create a DataTable with sample data
    DataTable dt = new DataTable();
    // Add columns with descriptive headers
    dt.Columns.Add("Product ID", typeof(int));
    dt.Columns.Add("Product Name", typeof(string));
    dt.Columns.Add("Price", typeof(decimal));
    dt.Columns.Add("Stock Quantity", typeof(int));
    // Add sample rows
    dt.Rows.Add(1001, "Laptop", 999.99m, 15);
    dt.Rows.Add(1002, "Mouse", 29.99m, 50);
    dt.Rows.Add(1003, "Keyboard", 79.99m, 30);
    dt.Rows.Add(1004, "Monitor", 299.99m, 12);
    dt.Rows.Add(1005, "Headphones", 89.99m, 25);  
    // Bind the DataTable to DataGridView Control
    dataGridView1.DataSource = dt;
}

private void Form1_Load(object sender, EventArgs e)
{
    // Example object usage
    object obj = "Initializing DataTable"; 
    Console.WriteLine(obj);
    // Create a DataTable with sample data
    DataTable dt = new DataTable();
    // Add columns with descriptive headers
    dt.Columns.Add("Product ID", typeof(int));
    dt.Columns.Add("Product Name", typeof(string));
    dt.Columns.Add("Price", typeof(decimal));
    dt.Columns.Add("Stock Quantity", typeof(int));
    // Add sample rows
    dt.Rows.Add(1001, "Laptop", 999.99m, 15);
    dt.Rows.Add(1002, "Mouse", 29.99m, 50);
    dt.Rows.Add(1003, "Keyboard", 79.99m, 30);
    dt.Rows.Add(1004, "Monitor", 299.99m, 12);
    dt.Rows.Add(1005, "Headphones", 89.99m, 25);  
    // Bind the DataTable to DataGridView Control
    dataGridView1.DataSource = dt;
}

IRON VB CONVERTER ERROR developers@ironsoftware.com

This example creates a DataTable and binds it to the grid. Even with a small amount of data, the approach scales well for larger tables. The column names defined here will become the headers in your Excel file.

The sample data represents a simple product inventory, making it easy to verify the export worked correctly. For more complex data binding scenarios, Microsoft's documentation on DataGridView data binding provides additional examples.

This creates a DataGridView with populated with all the data from our code:

Implementing the Export with Column Headers

Now for the main functionality, exporting the DataGridView to Excel while preserving column headers. Add this method to handle the export button click:

private void btnExport_Click(object sender, EventArgs e)
{
    // Create a new Excel workbook
    WorkBook workbook = WorkBook.Create(ExcelFileFormat.XLSX);
    WorkSheet worksheet = workbook.CreateWorkSheet("Exported Data");
    // Export column headers
    for (int col = 0; col < dataGridView1.Columns.Count; col++)
    {
        worksheet.SetCellValue(0, col, dataGridView1.Columns[col].HeaderText);
    }
    // Export data rows
    for (int row = 0; row < dataGridView1.Rows.Count; row++)
    {
        // Skip the last empty row (used for adding new rows in DataGridView)
        if (dataGridView1.AllowUserToAddRows && row == dataGridView1.Rows.Count - 1)
            continue;
        for (int col = 0; col < dataGridView1.Columns.Count; col++)
        {
            var cellValue = dataGridView1.Rows[row].Cells[col].Value;
            if (cellValue != null)
            {
                worksheet.SetCellValue(row + 1, col, cellValue.ToString());
            }
        }
    }
    // Show save dialog
    using (SaveFileDialog saveFileDialog = new SaveFileDialog
    {
        Filter = "Excel Files|*.xlsx",
        FileName = "DataGridView_Export.xlsx"
    })
    {
        if (saveFileDialog.ShowDialog() == DialogResult.OK)
        {
            workbook.SaveAs(saveFileDialog.FileName);
            MessageBox.Show("Export completed successfully!", "Success",
                            MessageBoxButtons.OK, MessageBoxIcon.Information);
        }
    }
}

private void btnExport_Click(object sender, EventArgs e)
{
    // Create a new Excel workbook
    WorkBook workbook = WorkBook.Create(ExcelFileFormat.XLSX);
    WorkSheet worksheet = workbook.CreateWorkSheet("Exported Data");
    // Export column headers
    for (int col = 0; col < dataGridView1.Columns.Count; col++)
    {
        worksheet.SetCellValue(0, col, dataGridView1.Columns[col].HeaderText);
    }
    // Export data rows
    for (int row = 0; row < dataGridView1.Rows.Count; row++)
    {
        // Skip the last empty row (used for adding new rows in DataGridView)
        if (dataGridView1.AllowUserToAddRows && row == dataGridView1.Rows.Count - 1)
            continue;
        for (int col = 0; col < dataGridView1.Columns.Count; col++)
        {
            var cellValue = dataGridView1.Rows[row].Cells[col].Value;
            if (cellValue != null)
            {
                worksheet.SetCellValue(row + 1, col, cellValue.ToString());
            }
        }
    }
    // Show save dialog
    using (SaveFileDialog saveFileDialog = new SaveFileDialog
    {
        Filter = "Excel Files|*.xlsx",
        FileName = "DataGridView_Export.xlsx"
    })
    {
        if (saveFileDialog.ShowDialog() == DialogResult.OK)
        {
            workbook.SaveAs(saveFileDialog.FileName);
            MessageBox.Show("Export completed successfully!", "Success",
                            MessageBoxButtons.OK, MessageBoxIcon.Information);
        }
    }
}

IRON VB CONVERTER ERROR developers@ironsoftware.com

This export method performs several crucial steps:

1. Creating the Workbook: WorkBook workbook = WorkBook.Create(ExcelFileFormat.XLSX) initializes a new Excel file in memory
2. Adding a Worksheet: The CreateWorkSheet method adds a named sheet to hold your data
3. Exporting Headers: The first loop iterates through DataGridView columns, extracting the HeaderText property and writing it to row 0
4. Exporting the Data: The nested loops process each table cell, with null checking to prevent errors
5. User-Friendly Saving: SaveFileDialog lets users choose the file location and name

The key to preserving headers lies in accessing the dataGridView1.Columns[i].HeaderText property, which contains the display text for each column header. You can add a comment above each export step to clarify the purpose for other developers or for future maintenance.

Handling Common Excel File Data Export Scenarios

When working with real-world data, you'll encounter various scenarios that requ

ire special handling:

• Empty Cells: The null check in our code prevents errors when cells contain no data. Empty cells appear as blank in Excel, maintaining the grid structure.
• Mixed Data Types: IronXL automatically handles different data formats. Numbers remain numeric in Excel, allowing calculations, while text stays as strings.
• Special Characters: Column headers with special characters export correctly. IronXL handles encoding automatically, preserving characters like &, <, >, and accented letters.

When exporting documents, errors can occur. Use try-catch-finally for robust handling:

try 
{
    // Export code here
}
catch (Exception ex)
{
    MessageBox.Show($"Export failed: {ex.Message}", "Error", 
                   MessageBoxButtons.OK, MessageBoxIcon.Error);
}

try 
{
    // Export code here
}
catch (Exception ex)
{
    MessageBox.Show($"Export failed: {ex.Message}", "Error", 
                   MessageBoxButtons.OK, MessageBoxIcon.Error);
}

IRON VB CONVERTER ERROR developers@ironsoftware.com

IronXL preserves details of your Excel sheet such as formatting, headers, and special characters. For more advanced scenarios, you can check the IronXL documentation as a reference for tasks such as file security, cell styling, or formula preservation.

Conclusion

Exporting DataGridView to Excel with column headers is straightforward with IronXL. The library handles the complex Excel file operations while you focus on your application logic. Whether you choose direct cell-by-cell export or the DataTable approach, your column headers will transfer perfectly to Excel. This makes it easy to convert your DataGridView data to Excel format without losing out on any informative headers or lose data.

We hope this article helped you implement a reliable solution for your DataGridView exporting needs, and you can go on confidently with the skills you learned here today to export your DataGridView's to Excel format. If you’re looking for a reliable C# exporting DataGridView to Excel with column headers solution, IronXL provides a clean, dependency-free way to achieve it.

Ready to implement this in your project? Start with IronXL's free trial to explore its full capabilities. For production use, licensing starts at competitive rates with comprehensive support included.