Edit this page

Getting Started

This article explains how to add a RadSpreadsheet control to a page and wire it with UI.

It contains the following sections:

Assembly References

The assemblies that contain the implementation of RadSpreadsheet and must be referenced in order to use the control are:

  • Telerik.Windows.Controls.dll

  • Telerik.Windows.Controls.GridView.dll

  • Telerik.Windows.Controls.Input.dll

  • Telerik.Windows.Controls.Navigation.dll

  • Telerik.Windows.Controls.Spreadsheet.dll

  • Telerik.Windows.Data.dll

  • Telerik.Windows.Documents.Core.dll

  • Telerik.Windows.Documents.Spreadsheet.dll

For export and import to XLSX:

  • Telerik.Windows.Zip.dll

  • Telerik.Windows.Documents.Spreadsheet.FormatProviders.OpenXml.dll

To export a document to PDF, you will need to add a reference to the corresponding assembly:

  • Telerik.Windows.Documents.Spreadsheet.FormatProviders.Pdf.dll

Note that in order to import/export in XLSX or export to PDF, the format provider must be registered manually. More information on Import/Export can be found here.

If you want to use the sample UI provided in our demos you should add this reference as well:

  • Telerik.Windows.Controls.RibbonView.dll


For a bare-bone Spreadsheet control, you only need a declaration of the telerik schema:

For the UI that enables the full-featured use of the control, you should also declare:


Spreadsheet and RibbonView

Then, all that is left is to add the Spreadsheet component to the page:

        <telerik:RadSpreadsheet x:Name="radSpreadsheet" />

RadSpreadsheet is easy to integrate with all kinds of UI thanks to the commanding mechanism that it employs. If you would like to use the control with a RadRibbonView, which shows the full potential of the control, you can refer to the SDK repository.

You can download a runnable project of RadSpreadsheet wired with a full-featured RadRibbonView from the FirstLook example in our online SDK repository here.

See Also

Was this article helpful? Yes No

Give article feedback

Tell us how we can improve this article