Log In
Home
Support
Demos
Documentation
Blogs
Training
Webinars
[Expand]General Information
[Expand]WinForms Controls
[Collapse]ASP.NET Controls and MVC Extensions
 [Expand]Prerequisites
 [Expand]What's Installed
 [Expand]Common Concepts
 [Collapse]ASP.NET WebForms Controls
  [Expand]Reporting
  [Expand]Chart Control
  [Expand]Grid View
  [Expand]Card View
  [Expand]Vertical Grid
  [Expand]Spreadsheet
  [Expand]Rich Text Editor
  [Expand]Image and Data Browsing
  [Expand]Docking and Popups
  [Expand]Site Navigation and Layout
  [Expand]File Management
  [Expand]Multi-Use Site Controls
  [Collapse]Scheduler
   [Expand]Product Information
    Getting Started
   [Expand]Fundamentals
   [Expand]Concepts
   [Collapse]Visual Elements
    [Collapse]ASPxScheduler
      All-Day Area
      Appointments
      Dialog Forms
      Day Headers
      More Buttons
      Navigation Buttons
      Resource Headers
      Resource Navigator
      Time Cells
      Time Ruler
      Time Scales
      View Navigator
      View Selector
      View Visible Interval
      Time Marker
      Time Indicator
      ToolTip
     ASPxDateNavigator
   [Expand]Design-Time Features
   [Expand]Examples
   [Expand]End-User Capabilities
   [Expand]Member Tables
  [Expand]HTML Editor
  [Expand]Pivot Grid
  [Expand]Tree List
  [Expand]Gauges
  [Expand]Data Editors
  [Expand]Spell Checker
  [Expand]Query Builder
 [Expand]ASP.NET MVC Extensions
 [Expand]Localization
 [Expand]Redistribution and Deployment
  Get More Help
 [Expand]API Reference
[Expand]ASP.NET Bootstrap Controls
[Expand]ASP.NET Core Bootstrap Controls
[Expand]WPF Controls
[Expand]Xamarin Controls
[Expand]Windows 10 App Controls
[Expand]Document Server
[Expand]Reporting
[Expand]Report Server
[Expand]Dashboard
[Expand]eXpressApp Framework
[Expand]CodeRush
[Expand]CodeRush Classic
[Expand]Cross-Platform Core Libraries
[Expand]Tools and Utilities
 End-User Documentation

Dialog Forms

The default forms are normally delivered via the ASPxScheduler assembly because it is better for performance and more efficient than storing all forms. Forms should only be copied locally if they need to be modified. Once modified, these forms will be used by the ASPxScheduler within the web project.

You can retrieve default templates and copy them to your web project to make them available for customization. To do this, click the ASPxScheduler control's Smart Tag to invoke the actions list. In this list, click the 'Copy Default Dialog Forms to the Project...' link.

An alert dialog is invoked, warning you that this action will extract default dialog forms from the resources. If you do not plan to modify default forms, click No.

A DevExpress subfolder will be added to this project to store the ASPxScheduler dialogs and forms.

The OptionsForms and OptionsToolTips attributes of the SchedulerControl will be updated to point to the local copies of the forms.

If you are working with a Web application project, Microsoft Visual Studio will warn you that the added files (dialog and forms) will be converted to Web application project files.

Click Yes in the dialog to continue.

Although the default location of the copied dialog forms is a DevExpress folder, you can move them to any folder within the site. If you move the files from the DevExpress subfolder, use the ASPxScheduler.OptionsForms and ASPxScheduler.OptionsToolTips properties, and specify the new location of the files. You can have different customized forms for different ASPxScheduler instances.

Expanded See Also

How would you rate this topic?​​​​​​​