Workbooks pour .NET

The API mirrors the shape of an Excel workbook, so the code reads much like the document it produces. First you create a workbook, then you write values into cells, and finally you save. This example builds a small sales sheet, adds a real Excel table and calculates a formula.

using Xceed.Workbooks.NET;

// Apply your trial or purchased key once, at application startup.
Licenser.LicenseKey = "your-license-key";

using( var workbook = Workbook.Create( "SalesReport.xlsx" ) )
{
  var sheet = workbook.Worksheets[ 0 ];
  sheet.Name = "Q1 Sales";

  sheet.Cells[ "A1" ].Value = "Region";
  sheet.Cells[ "B1" ].Value = "Revenue";

  sheet.Cells[ "A2" ].Value = "North America";
  sheet.Cells[ "B2" ].Value = 128400d;
  sheet.Cells[ "A3" ].Value = "Europe";
  sheet.Cells[ "B3" ].Value = 96750d;

  sheet.Cells[ "A5" ].Value = "Total";
  sheet.Cells[ "B5" ].Formula = "=SUM(B2:B3)";

  // Turn the range into a genuine Excel table, not just formatted cells.
  sheet.Tables.Add( "SalesTable", "A1", "B3", TableStyle.TableStyleMedium9, true );

  workbook.CalculateFormulas();
  workbook.Save();
}

Reading an existing file follows the same pattern. You call Workbook.Load au lieu de Workbook.Create, change what you need, then call Sauvegarde to write a new copy. Because Workbook implements IDisposable, the using block closes the file for you.

Before you pick an Excel library for .NET, check that it covers the frameworks you actually ship on. This one ships two builds in a single NuGet package, so the right assembly resolves automatically for your target framework.

Developers usually arrive here after hitting a wall with one of two alternatives. The table below sets out the practical differences.

Interop also routes every call through a desktop application, so throughput drops sharply under load. A managed Excel library for .NET avoids that bottleneck entirely, which keeps generation predictable on a busy server.

Do I need Microsoft Excel installed to use Xceed Workbooks for .NET?

No. Xceed Workbooks for .NET writes the Office Open XML .xlsx format directly, so it needs no Excel installation, no Office licence and no COM Interop on the machine that runs your code. Consequently you can generate spreadsheets on a web server or inside a container.

Which .NET versions does Xceed Workbooks for .NET support?

The package targets .NET Framework 4.0 and up as well as .NET 5.0 and up, which covers .NET 5, 6, 7, 8 and 9. It also works with ASP.NET and ASP.NET Core, and it supports C#, VB.NET and Managed C++.

Does Xceed Workbooks for .NET run on Linux and in Docker?

Yes, on .NET 5 and later. The package depends on Xceed.Drawing.NET, which ships SkiaSharp Linux native assets, so drawing and image support work inside Linux containers without extra system packages.

Can it read and edit an existing Excel file, or only create new ones?

It does both. Call Workbook.Load to open an existing .xlsx file, modify cells, tables, formulas or formatting, then call Save or SaveAs. Many teams use this to populate a spreadsheet that a colleague designed in Excel.

Does Xceed Workbooks for .NET calculate Excel formulas?

Yes. You assign a formula through the Formula property on a cell, then call CalculateFormulas on the workbook or the worksheet. The library evaluates the supported formulas and stores the results in the saved file.

How much does Xceed Workbooks for .NET cost, and is there a free trial?

A free 45-day trial is available and needs no credit card. Paid subscriptions begin with the Small Business licence for companies under 1 million USD in annual revenue, followed by the Standard licence and the Blueprint licence, which adds full source code.