Registers the Bonus Skins for runtime use. Setting this property to true results in loading the DevExpress. If the assembly is successfully loaded, the Bonus Skins are registered for runtime use.
If assembly loading fails, no exception is thrown. If the Bonus Skins are already registered, setting the EnableBonusSkins property to false has no effect. At design time, you can add the DefaultLookAndFeel component onto the form and use its smart tag menu to register the Bonus Skins.
See the Skins topic for more details on the skinning functionality. General Information WinForms Controls. XtraWizard ASP. View this topic on docs. LookAndFeel Namespace Skins. Copyright c Developer Express Inc. All rights reserved. General Information.
WinForms Controls. NET Core Support. What's Installed. Build an Application. Controls and Libraries. Common Features. Get More Help. DefaultLookAndFeel Class.
DefaultLookAndFeel Members. DefaultLookAndFeel Constructor. DefaultLookAndFeel Properties.In the Project Manager dialog, switch to the "Export" tab and click "Create Resources" to save skins included in the project to a selected folder. Each skin is saved as a pair of. Rename this folder, right-click it and select "Add Existing Items" to add.
All docs. General Information. NET Subscription Overview. Common Tools Project Converter. Assembly Deployment Tool. Localization Service. Quality Assurance and Productivity. CodeRush Classic. TestCafe Studio. Controls WinForms. UWP Windows Tools WinForms Skin Editor. WPF Theme Designer. Coded UI Test Extension. Frameworks and Libraries. XPO Profiler. Core Libraries. Controls and Extensions ASP. NET Core Controls.DevExpress WinForms controls include many ready-to-use paint themes or skins for changing DevExpress forms' and controls' appearance.
You can see the different skins by running WinForms Demo Applications and switching between the available themes using a Skin Selector. This topic describes the available raster and vector skins, how to apply a skin to the entire application and individual controls, how to alter a skin's color palette and how to create a custom skin.
Vector skins utilize vector images for all UI elements to improve the display quality on high-resolution devices. Each vector skin can have multiple palettes swatches that are skin color themes. RibbonControl provides the "Skin Palette Gallery" item that allows users to switch palettes at runtime. Starting with version You can repaint vector skins and change their palettes in the updated WinForms Skin Editor. See the Working with Vector Skins article to learn more.
The following gallery demonstrates the default skins that are part of the DevExpress. Utils library all projects that use DevExpress WinForms controls require this library :. Add the DevExpress. BonusSkins assembly to your project to use additional skins that are not included in the basic set described above. If this command is not available, then the bonus themes have already been registered. Certain DevExpress Project Templates automatically register bonus skins.
To register bonus skins in code, first ensure that your project references the DevExpress. BonusSkins assembly. Then call the DevExpress. Register method before the main application form runs. You can apply bonus skins once they are registered.
The following code sets the Pumpkin bonus skin as the application's default skin:. Invoke the DevExpress Project Settings page and select a desired theme to apply it to the entire application. Alternatively, call the UserLookAndFeel. Default static object's UserLookAndFeel. SetSkinStyle method. To apply a vector skin in code, use the UserLookAndFeel.
This parameter allows you to apply a pre-defined color palette swatch to a skin. DevExpress forms and message boxes have skinned title bars and borders by default.
You can disable default title bar skinning using a compatibility option see Version Compatibility: Default Property Values or the WindowsFormsSettings. DisableFormSkins method. DevExpress Toolbars and Menus and Ribbon provide pre-defined skin selector items - SkinBarSubItem and SkinRibbonGalleryBarItem - which are automatically populated with available skin items and allow end-users to switch an application theme at any time.
It is hidden if a traditional raster skin is currently active. Note that this item is only available in the Ribbon Control and does not support the Bar Manager. To change skin selectors' item captions and icons, handle the static DevExpress. CreateGalleryItem event. You can also manually obtain the list of available skin styles and create a custom UI element to switch between them.The following tutorials guide you through the basics of creating custom skins in the DevExpress Skin Editor.
Click "New Project" and check one or multiple DevExpress skins to serve as templates for your custom skin. Enter the project name and click "Create Project". If the "Create light skins" Editor setting is enabled default statenewly created skins contain no skin elements and their settings are automatically copied from template skins.
To be able to modify an inactive element, you first need to click "Activate" to add this element to the skin. This technique allows you to dramatically reduce the skin size, and is helpful for light skin modifications. Otherwise, if you need to heavily modify a skin, enable the "Create full skins" setting.
In this case, new skins include all skin elements hard-copied from parent skins. If you created a light skin, along with the assembly that contains your custom skin, you should also add the assembly that contains the base skin to the project. For example, if you create a light skin based on a bonus skin, you should add the DevExpress.
You can add bonus skins in the DevExpress Project Settings page. Each selected skin opens in a separate tab where you can start applying changes right away. You might also want to have the same skins available in their original state in separate tabs so you can restore elements quickly should anything go wrong with customization.
Drawing custom skins requires you to modify bitmaps associated with skin elements using an external graphics editor. Click "Settings To restore a skin element bitmap, switch to a backup tab and locate this element on a list to the left side of the Skin Editor.
Right-click the element and select "Graphics Copy Go back to a tab with your custom skin, right-click the same element and select "Graphics Paste" to restore element bitmaps. In the same manner, you can also copy and paste element properties size settings, colors, content margins, etc. To be able to test your custom skin, create an assembly and register it in your sample application as written in this article.
After you have set everything up, click "Create Assembly" and re-start your sample application each time you need to test a modified skin. The Skin Editor can also run any Visual Studio project and paint it with your custom skin.
This allows you to preview a skin in a real-life application without the necessity to export the Skin project into a library and reference it from that application. See the WindowsFormsSettings. AllowSkinEditorAttach property to learn more.
All docs. General Information. NET Subscription Overview. Common Tools Project Converter. Assembly Deployment Tool. Localization Service. Quality Assurance and Productivity. CodeRush Classic. TestCafe Studio.You must have a valid license to legally distribute applications that use DevExpress components.
This topic covers the DevExpress redistribution policy and contains a list of redistributable assemblies. When you deploy a WinForms project that uses DevExpress WinForms controls, you should copy the corresponding assembly files onto an end-user machine.
In most cases, you may only use some assemblies in your project. Use the Assembly Deployment Tool to analyze your project and obtain the list of assemblies that should be deployed in your particular case.
Distributing any DevExpress design-time assemblies ending with ". Below is a full list of redistributable DevExpress WinForms assemblies. By default, these assemblies are located in the following folder of your development machine after installation. All DevExpress Charting controls contain classes shared via the same charting engine. These classes, along with a codebase, are intended for internal use, but also provide the basic functionality for ASP.
This assembly is also required when deploying an application containing the WPF Spreadsheet control with a chart. Contains classes that are used to parse and highlight code within the Script Editor. Required for the End-User Report Designer. Implements the most basic functionality common to all DevExpress controls. This includes classes for data binding, skinning, printing, exporting, as well as many other auxiliary types and resources.
Contains internal classes that implement the basic functionality for DevExpress diagram controls. The DevExpress Image Gallery, which stores images for use in various controls and components. Deploy this library when providing context-dependent images to controls and components using the Image URI feature. Contains classes that provide communication with Entity Framework Core data sources.
Contains classes that provide communication with Windows Communication Foundation services. Contains classes that support exporting reports to the. Contains the classes that support the main functionality of the eXpress Persistent Objects Library.
Contains extra skins such as "Metropolis" and "McSkin". Contains skinnable DevExpress counterparts for standard WinForms open file, save file and folder browser dialogs.Enables the title bar skinning feature for DevExpress forms and message boxes. Starting from version You can change this default behavior with the dedicated compatibility option see Version Compatibility: Default Property Valuesor with the WindowsFormsSettings. DisableFormSkins method.
The form title bar skinning feature paints the title bar and border of DevExpress forms and message boxes according to the current skin. Typically, these methods should be called at application startup. In this instance, the DevExpress. This forces the form's title bar to be repainted:. When a Windows Aero scheme is applied for instance, in Windows Vistathe title bar skinning feature is not applied to RibbonForm s unless the RibbonForm.
Export and Apply Custom Skins
AllowFormGlass option is set to False. General Information WinForms Controls. XtraWizard ASP. View this topic on docs. Copyright c Developer Express Inc. All rights reserved. General Information.
WinForms Controls. NET Core Support.
What's Installed. Build an Application. Controls and Libraries. Common Features.This document explains how to export your custom skins and use them within Visual Studio projects. When your skin is ready or when you want to test it in a live application, invoke the main Skin Editor Menu and launch the Project Manager.
Switch to the "Export" tab and click "Create Assembly" to generate a. This file will be saved to the root folder of the project.
Repeat these steps every time you modify a skin and need to test the modifications in a separate application. You can also run the "SkinEditor. This command line returns 1 if building the project succeeds, and 0 if it fails. Example: SkinEditor. To utilize skins from a custom library, you first need to register it. To do that, click the "Create Assembly" button and copy the code that is automatically generated by the Project Manager.
Open the Visual Studio project with which you want to test your skin. In the Solution Explorer window, right-click a "References" folder and click "Add Reference"then select the.
Paste the code copied from the Project Manager to the "Program. The SkinManager. RegisterAssembly method is used to register the custom assembly. After the custom skin is registered, you can apply it similarly to standard DevExpress skins. To apply a skin in code, add the following line to the same "Program" file that contains registration code. All docs.
General Information. NET Subscription Overview. Common Tools Project Converter. Assembly Deployment Tool. Localization Service. Quality Assurance and Productivity. CodeRush Classic. TestCafe Studio. Controls WinForms. UWP Windows Tools WinForms Skin Editor. WPF Theme Designer. Coded UI Test Extension. Frameworks and Libraries. XPO Profiler.