Getting Started

This tutorial will walk you through the creation of a sample application that contains RadToolBar.

Assembly References

In order to use the RadToolBar control in your projects, you have to add references to the following assemblies:

  • Telerik.Windows.Controls
  • Telerik.Windows.Controls.Navigation

Add RadToolBar to the Project

Before proceeding with adding RadToolBar to your project, make sure the required assembly references are added to the project.

You can add RadToolBar manually by writing the XAML code in Example 1. You can also add the control by dragging it from the Visual Studio Toolbox and dropping it over the XAML view.

Example 1: Adding RadToolBar in XAML

<telerik:RadToolBar /> 

In order to use RadToolBar in XAML you have to add the namespace declaration shown in Example 2:

Example 2: Declaring Telerik Namespace

If you run the application you will see an empty toolbar as demonstrated in Figure 1.

Figure 1: The empty toolbar generated by the code in Example 1

Empty RadToolBar

Populating with Data

In order to populate the RadToolBar control with data in XAML, you can add a few RadButtons to it and set their Content property as in Example 3.

Example 3: Adding RadButtons in XAML

    <telerik:RadButton Content="FILE" /> 
    <telerik:RadButton Content="EDIT " /> 
    <telerik:RadButton Content="VIEW" /> 
    <telerik:RadButton Content="BUILD" /> 
    <telerik:RadButton Content="DEBUG" /> 
    <telerik:RadButton Content="HELP" /> 
Running the application will result in a populated RadToolBar as shown in Figure 2.

Figure 2: RadToolBar with static items

Populated RadToolBar

Adding static items in XAML is good for scenarios when you know in advance the contents toolbox. However, in most cases, you have to bind your RadToolBar to a collection of objects. You can achieve this through the ItemsSource property of the control.

You can have a look at the following blog post for a good example of how to bind the control.

See Also

In this article
Not finding the help you need? Improve this article