Skip to main content

Script Editor

  • 3 minutes to read


To make sure that your application properly implements script security, both the execution of all report scripts and the capability to view and edit scripts in the Web Report Designer are disabled by default.

To learn how to enable scripting in the Web Report Designer, see Scripts Security.

The Script Editor allows end-users to write code for specific event handlers in the End-User Report Designer to adjust the behavior of report controls, bands, or a report itself. This topic describes the basic principles of using scripts in XtraReports, the Script Editor interface and shows how scripting can be used in a report.


The Script Editor provides end-users with the capability to write and execute scripts at runtime when a report is generated. Note that although it’s possible to add scripts in both the Visual Studio IDE and in the End-User Report Designer, this feature is primarily intended to be used by advanced end-users who want to slightly customize a report in the End-User Report Designer.

The Script Editor supports C#, Visual Basic .NET and JScript .NET scripting languages. This means that the scripting language is independent from the language used to create the report. The language is specified by the XtraReport.ScriptLanguage property. The selected scripting language must be the same for all scripts used in a report.


The Script Editor supports intelligent code completion that makes it easier and faster for end-users to write scripts. Context-aware hints are displayed on pressing CTRL+spacebar. This feature is only supported for the C# and Visual Basic .NET script languages.


Intelligent code completion is available only for .NET Framework and DevExpress libraries deployed with the application and cannot be provided for custom assemblies.

Maintaining Scripts

Each report element has its own set of events that can be handled by the Script Editor. To handle an event of a report element, do the following.

  1. Click the Scripts button () located on the End-User Report Designer’s Main Toolbar.
  2. In the displayed Script Editor, specify the report control and its event by the toolbar. The toolbar contains all scripts written for all report elements, and allows you to quickly navigate through them by choosing the required report element in the corresponding drop-down list and specifying one of its available events in another menu.


    After the event is specified, a code template is generated in the current scripting language.

  3. To check for errors in the report’s script, click the Validate button (aspx-script-editor-validate).

    If an error is found, the string containing this error is marked with an aspx-script-editor-error icon. When a mouse pointer hovers over this icon, the text of the error is displayed.


See Also