[Expand]General Information
[Collapse]WinForms Controls
  .NET Core Support
 [Expand]What's Installed
 [Expand]Build an Application
 [Collapse]Controls and Libraries
  [Expand]Forms and User Controls
  [Expand]Messages, Notifications, and Dialogs
  [Expand]Editors and Simple Controls
  [Expand]Ribbon, Bars and Menu
  [Expand]Application UI Manager
  [Expand]Docking Library
  [Expand]Data Grid
  [Expand]Vertical Grid
  [Expand]Property Grid
  [Expand]Pivot Grid
  [Expand]Tree List
  [Expand]Gantt Control
  [Expand]Chart Control
  [Expand]Map Control
  [Expand]Rich Text Editor
  [Expand]Spell Checker
  [Expand]Form Layout Managers
  [Expand]Navigation Controls
   [Expand]Product Information
   [Expand]Getting Started
   [Collapse]Fundamental Concepts
     Document Creation Approaches
     Classes Hierarchy: Bricks
     Class Hierarchy: Printing
  [Expand]PDF Viewer
  [Expand]TreeMap Control
  [Expand]Sunburst Control
 [Expand]Common Features
  Get More Help
 [Expand]API Reference
[Expand]ASP.NET Controls and MVC Extensions
[Expand]ASP.NET Bootstrap Controls
[Expand]ASP.NET Core Bootstrap Controls
[Expand]WPF Controls
[Expand]Xamarin Controls
[Expand]Windows 10 App Controls
[Expand]Office File API
[Expand]Report and Dashboard Server
[Expand]eXpressApp Framework
[Expand]eXpress Persistent Objects
[Expand]CodeRush Classic
[Expand]Cross-Platform Core Libraries
[Expand]Tools and Utilities
 End-User Documentation
View this topic on docs.devexpress.com (Learn more)

Classes Hierarchy: Bricks

This document introduces the class hierarchy of bricks, available in the XtraPrinting Library. For more information on the brick concept, refer to the Bricks document.

The brick genealogy begins with the abstract BrickBase class. It provides essential properties and methods, which are common to all bricks. The BrickBase class has two inheritors - the Brick class and Page& class.

This basic hierarchy is represented in the scheme below.

The Brick class is the base for all the varieties of bricks.

The Brick class inheritance hierarchy is illustrated in the following diagram:


The CompositeBrick class is used for internal purposes only. This brick combines multiple visual bricks and defines how to render contained bricks on a page.

The EmptyBrick class is not displayed within reports, and is used for service purposes only. It allows you to combine bricks across separate groups.

The UserVisualBrick and UserPageBrick classes represent a user implementation of the IBrick interface added to a report via the IBrickGraphics.DrawBrick method. Also, you can create your own brick, which can inherit from any brick.

For more information about particular brick types, refer to the corresponding topics.

Expanded See Also

Is this topic helpful?​​​​​​​