This example illustrates how to setup SchedulerControl binding at runtime. Note that all appointment mappings and even SQL queries along with their parameters are adjusted in code without the use of the VS designer. This is the most flexible database-binding technique because it allows you to modify data-binding options and SQL queries with ease. For instance, we keep the time of modification along with the modified row by inserting a GETDATE function result into a TimeStamp column. Here are to corresponding SQL queries:

[SQL]
INSERT INTO CarScheduling (StartTime, EndTime, Subject, TimeStamp) VALUES (@StartTime, @EndTime, @Subject, GetDate())

UPDATE CarScheduling SET StartTime = @StartTime, EndTime = @EndTime, Subject = @Subject, TimeStamp = GetDate() WHERE ID = @ID

DELETE FROM CarScheduling WHERE ID = @ID

To test this example locally, setup "SchedulerBindDynamically" sample database in your SQL Server instance. Utilize the SchedulerBindDynamically.sql file attached to this example to generate a sample database and table schema.

Note:
We do not use the SqlCommandBuilder Class capabilities to generate SQL queries as it is shown in the How to bind SchedulerControl to MS SQL Server database at runtime code example. The DbCommandBuilder.ConflictOption Property option of this class allows you to enable optimistic concurrency to prevent a concurrency violation error. Since we do not use this functionality, you might encounter this error when using this example. Fortunately, there are some ways that allows you to avoid this error. You can find them in the Introduction to Data Concurrency in ADO.NET MSDN article.

See Also:
Updating Data Sources with DataAdapters

Getting Started

This example demonstrates how to export RichEditControl's document in a custom document format using a DocumentIterator object and a custom document visitor. The DocumentIterator is created to iterate through document elements. The custom document visitor is used to export document elements to a lightweight markup language (Markdown)/

The document visitor is implemented according to the Visitor pattern (by implementing the IDocumentVisitor interface). In this example, the custom document visitor is inherited from the DocumentVisitorBase class. The DocumentVisitorBase class implements the IDocumentVisitor interface by default. Thus, you can override only required methods of the DocumentVisitorBase class for custom document processing.

The document iterator moves over each document structure item and passes a custom document visitor object to the current item. The custom document visitor builds a string with lightweight markup for the currently processed document item.

This example contains a Customers grid with a hyperlink column. When a hyperlink is clicked, a popup window is opened to display detail data - orders - of a given customer. Orders is the GridView extension in the content of the PopupControl.

See also:
How to display detail data within a popup window using ContentUrl (MVC)
How to display detail data within a popup window

detailGrid.PerformCallback();

This example demonstrates how to use a custom font distributed with the application in XtraReport.

The main idea of this approach is to use the PrivateFontCollection class to store custom font families. Use the Families property to access the FontFamily objects of your private fonts.

In this example, the static "FontCollection" property is used to store the report's private fonts. Then, in the report constructor, the private font families are used to specify fonts of the report controls.

This is a cross-platform approach, so it can be used for all technologies supported by XtraReports. However, there are some notes:

ASP.NET
The private font will be available only on your web server, so it won't be displayed in ASPxDocumentViewer by default if it is not installed on the client machine.

However, you can register this custom font on your webpage, for example by using the @font-face CSS rule. In this case, add this rule to your webpage with the viewer and set your ASPxDocumentViewer.SettingsReportViewer.UseIFrame property to the "false" value to prevent your report from being rendered in an iframe. This approach is demonstrated in this example.

WPF
The font cannot be registered globally by using the PrivateFontCollection in WPF, so the explicit reference to the embedded font is required there. The E5083: How to display a report that uses a private font (distributed with the application) in DocumentPreview code example demonstrates how to work around this limitation.

See also:
How to: Create a Private Font Collection (MSDN)

This example illustrates a simple implementation of a new ASPxGridView Batch Editing Mode functionality available starting with version 13.2:
ASP.NET WebForms & MVC: GridView Batch Edit (What's new in 13.2)

This example is a standalone DB-independent solution of the online Batch Editing demo. Refer to the demo's Description for more information.

Handle the ASPxGridView RowInserting/RowUpdating/RowDeleting events if you want to submit a batch of modifications individually via a corresponding CRUD procedure.
Handle the ASPxGridView.BatchUpdate event if you want to submit a batch of modifications at once via a corresponding BatchUpdate procedure.

Note that this example uses a custom local data source stored in Session. The grid is bound to a list of objects of the GridDataItem type. The GridDataItem class here is implemented specially for this local data source. If you're using another data source, you can use the same approach to save the inserted/modified data in the RowInserting/RowUpdating/RowDeleting/BatchUpdate events without adding this class and modify your data by creating the corresponding requests to the data source in these event handlers

This example illustrates the use of a DevExpress.XtraRichEdit.Utils.RichEditImage.Uri property to retrieve original location of an image and store it in src attribute when a document is saved in HTML format.

The following example shows how to override an initial or user-defined dashboard parameter value by changing it in the ASPxDashboard.CustomParameters event handler.
The dashboard in this example has a CustomerIdDashboardParameter parameter with a certain initial value. At runtime, its value is changed in the ASPxDashboard.SetInitialDashboardState event handler. This value is displayed in the Parameters dialog and can be changed by the end-user,
However, by handling the ASPxDashboard.CustomParameters event, we can validate the parameter value and ignore the value provided by the end-user.To accomplish this, the data is obtained using a custom SQL query with a parameter named CustomerIdParameter. The query parameter is bound to the CustomerIdDashboardParameter dashboard parameter. The value of this parameter is changed at runtime by handling the ASPxDashboard.CustomParameters event which is raised before the ASPxDashboard sends a query to a database. Thus, only the value passed in the ASPxDashboard.CustomParameters event is in effect.

This example demonstrates how to paint two triangles on a map using the choropleth colorizer.

[JavaScript]
function onFocusedCellChanging(s, e){if(e.cellInfo.column.name == 'command')
        e.cancel = true;elseif(e.cellInfo.column.fieldName == 'SupplierID')
        e.cancel = true;elseif(e.cellInfo.column.fieldName == 'UnitsInStock'&& (e.cellInfo.rowVisibleIndex < 3 || e.cellInfo.rowVisibleIndex > 7))
        e.cancel = true;elseif(e.cellInfo.column.fieldName == 'UnitPrice'&& s.batchEditApi.GetCellValue(e.cellInfo.rowVisibleIndex, 'UnitPrice')> 22)
        e.cancel = true;}

Note: the FocusedCellChanging event can't prevent editor focusing if the ASPxGridView.SettingsEditing -> BatchEditSettings -> EditMode property is set to Row.

In the 12.1 version we implemented a Master-Detail feature, and now we provide it out of the box. We have added a new solution, which shows how to use our new approach.

With later versions of our controls you can use the previous workaround:

To accomplish this, it is necessary to use one GridControl as a template for a data row of another GridControl.

Limitations of the previous approach:

Vertical scrolling is performed per master row. For an example on how to implement vertical scrolling of details, please see 'Persistent Row State' in the DXGrid's demo.

Scenario:

There is an enumeration type decorated with the FlagsAttribute, which means that an enumeration can be treated as a set of flags. There is also a property of this enumeration type inside the business class. This is helpful when several predefined enumeration values can be stored using this data property. In the UI, this data property is usually represented via an editor with multiple check boxes:

Steps To Implement:

Since there is no standard  PropertyEditor for enumerations that would allow you to store several values at once, it is common to implement custom Property Editors for this task. A custom PropertyEditor will take data property value as its input and represent it in the UI using a custom visual control. There will be one PropertyEditor for WinForms (based on the CheckedComboBoxEdit control from the XtraEditors Suite) and one for ASP.NET (based on the ASPxGridLookup control from our ASPxGridView and Editors Suite), because there is no platform-agnostic way to achieve such a look and feel.

Consider following the steps below to implement and use editors from this example in your project.
1. Implement an enumeration type decorated with the FlagsAttribute as shown in the E689.Module\BusinessObjects\DemoObjects.xx file;
2. Copy the E689.Module.Win\Editors\EnumPropertyEditorEx.xx file into YourSolutionName.Module.Win project;
3. Copy the E689.Module.Web\Editors\ASPxEnumPropertyEditorEx.xx file into YourSolutionName.Module.Web project;
4. Build the solution and invoke the Model Editor for the ModelDesignedDiffs.xafml files from YourSolutionName.Module.Win and YourSolutionName.Module.Web projects.

5. Locate the BOModel | YourClassName | Members | YourEnumerationProperty node and set its PropertyEditorType property to the corresponding EnumPropertyEditorEx types.

See Also:

Implement Custom Property Editors
How to represent a enumeration property via radio buttons or check boxes on the Web

This example demonstrates how to save TreeListNode.CheckState in a bound mode. It is necessary to create an instance of the SaveCheckHelper class and pass TreeList and a field, containing CheckState, to a datasource bound to TreeList.

In recent versions of our components, use the TreeList.CheckBoxFieldName property to bind built-in checkboxes to a field in the data source.

This example demonstrates how to customize a color of the GridControl's refreshing bar (shown on Android) and refreshing icon (shown on iOS). A complete description is available in the How to: Customize Refresh Indicators topic.

This example demonstrates how to implement a helper that removes all expressions referencing a certain property from the CriteriaOperator. For example, you may want to programmatically remove fragments like "[SavedPassword] = '***'" from filter expressions that persist on client computers, because you decided to remove the SavedPassword property from the model for security reasons.

Although this task can be accomplished using regular expressions, this approach is too complicated and is applicable only to CriteriaOperator expressions that follow a certain pattern. This example uses a different technique, which allows you to support expressions of any complexity with minimum effort.

The solution demonstrated in this example uses the concept described in this Knowledge Base article: Implementation of the base class for a CriteriaOperator expression patcher. The DevExpress.Data.Filtering.Helpers.ClientCriteriaLazyPatcherBase.AggragatesCommonProcessingBase class is used in this example as a base class for the CriteriaPatcherSkipProperties class (in version 17.2 and earlier use the CriteriaPatcherBase class implemented in the example).

To remove any reference to a specific property from the CriteriaOperator expression, override the CriteriaPatcherBase.VisitProperty method, and return null (Nothing in Visual Basic) if the property name matches the name of a property that should be removed.

[C#]
protectedoverrideCriteriaOperatorVisitProperty(OperandPropertytheOperand){if(PropertiesToremove.Contains(theOperand.PropertyName))returnnull;returntheOperand;}

[VB.NET]
ProtectedOverridesFunction VisitProperty(ByVal theOperand As OperandProperty) As CriteriaOperatorIf PropertiesToremove.Contains(theOperand.PropertyName) ThenReturnNothingEndIfReturn theOperandEndFunction

However, this is incomplete. The expression will contain invalid statements if you simply remove properties from it: "() = #2015-12-30# And StartsWith([City], 'q')". To delete invalid statements from the expression, override the VisitAggregate, VisitFunction, VisitGroup, VisitIn, VisitUnary, VisitBinary, and VisitBetween methods. The implementation of overridden methods is demonstrated in the CriteriaPatcherSkipProperties.cs and CriteriaPatcherSkipProperties.vb files.

See also:
Implementation of the base class for a CriteriaOperator expression patcher

How to create a custom converter to convert the CriteriaOperator to the System.String type

This example illustrates one of the possible approaches to implementing an identifier field with sequential values. Alternate approaches are listed in the An overview of approaches to implementing a user-friendly sequential number for use with an XPO business class KB article.

Scenario
This is a variation of the How to generate and assign a sequential number for a business object within a database transaction, while being a part of a successful saving process XPO example, which was specially adapted for XAF applications.

In particular, for better reusability and more smooth integration with the standard XAF CRUD Controllers, all the required operations to generate sequences are managed within the base persistent class automatically when a persistent object is being saved. For more developer convenience, this solution is organized as a reusable XAF module - GenerateUserFriendlyId.Module. This module consists of several key parts:

    - Sequence and SequenceGenerator are auxiliary classes that take the main part in generating user-friendly identifiers. Take special note that the SequenceGenerator.Initialize method must be called during your XAF application startup for the correct operation.

    - UserFriendlyIdPersistentObject is a base persistent class that subscribes to XPO's Session events and delegates calls to the core classes above. Normally, you must inherit your own business classes from this base class to get the described functionality in your project.

    - IUserFriendlyIdDomainComponent is a base domain component that should be implemented by all domain components that require the described functionality.

Check the original example description first for more information on the demonstrated scenarios and functionality.

Steps to implement
1. Copy and include the GenerateUserFriendlyId.Module project into your solution and make sure it is built successfully.  Invoke the Module or Application Designer for the YourSolutionName.Module/Module.xx  or YourSolutionName.Wxx/WxxApplication.xx files by double-clicking it in Solution Explorer. Invoke the Toolbox (Alt+X+T) and then drag & drop the GenerateUserFriendlyIdModule component into the modules list on the left.

2. For apps with no security or with the Client-Side Security (XPObjectSpaceProvider or SecuredObjectSpaceProvider):
In the YourSolutionName.Wxx/WxxApplication.xx files, modify the CreateDefaultObjectSpaceProvider method to call the SequenceGenerator.Initialize method as shown in the Demo.Wxx\WxxApplication.xx files:

[C#]
protectedoverridevoidCreateDefaultObjectSpaceProvider(CreateCustomObjectSpaceProviderEventArgsargs){IXpoDataStoreProviderdataStoreProvider=XPObjectSpaceProvider.GetDataStoreProvider(args.ConnectionString,args.Connection,true);// Web:// IXpoDataStoreProvider dataStoreProvider = GetDataStoreProvider(args.ConnectionString, args.Connection);GenerateUserFriendlyId.Module.SequenceGenerator.Initialize(dataStoreProvider);...}

For apps with the Middle Tier Security (DataServerObjectSpaceProvider):
In the YourSolutionName.ApplicationServer project, locate and modify the serverApplication_CreateCustomObjectSpaceProvider or CreateDefaultObjectSpaceProvider  methods to call the SequenceGenerator.Initialize method in the same manner.

3. If you are using pure XPO classes, then inherit your required business classes from the module's UserFriendlyIdPersistentObject one and use the derived SequenceNumber property as required:

[C#]
publicclassContact:GenerateUserFriendlyId.Module.BusinessObjects.UserFriendlyIdPersistentObject{[PersistentAlias("concat('C', ToStr(SequentialNumber))")]publicstringContactId{get{returnConvert.ToString(EvaluateAlias("ContactId"));}}

If you are using DC interfaces, then implement the IUserFriendlyIdDomainComponent interface by your custom domain component:

[C#]
publicinterfaceIDocument:GenerateUserFriendlyId.Module.BusinessObjects.IUserFriendlyIdDomainComponent{[Calculated("concat('D', ToStr(SequentialNumber))")]stringDocumentId{get;}

Additionally for DC, use the UserFriendlyIdPersistentObject as a base class during your custom domain component registration, e.g.:

[C#]
XafTypesInfo.Instance.RegisterEntity("Document",typeof(IDocument),typeof(GenerateUserFriendlyId.Module.BusinessObjects.UserFriendlyIdPersistentObject));

Note that the sequential number functionality shown in this example does not work with DC shared parts , because it requires a custom base class, which is not allowed for shared parts.

4. For more information, download and review the Address, Contact, and IDocument types within the Demo.Module project. These are test business objects that demonstrate the use of the described functionality for XPO and DC respectively. A required format for the user-friendly identifier property in these end classes is defined within an aliased property (ContactId in the example above) by concatenation of a required constant or dynamic value with the SequentialNumber property provided by the base UserFriendlyIdPersistentObject class. So, if you need to have a different format, modify the PersistentAliasAttribute expression as your business needs dictate.

IMPORTANT NOTES

1. As an alternative, you can implement much simpler solutions at the database level or by using the built-in DistributedIdGeneratorHelper.Generate method. Refer to the An overview of approaches to implementing a user-friendly sequential number for use with an XPO business class article for more details.

2.  In the Integrated Mode and middle-tier Application Server scenario the newly generated sequence number will appear in the DetailView only after a manual refresh (i.e., it will be empty right away after saving a new record), because the sequence is generated on the server side only and is not passed to the client. You can download a ready test project for these configurations here. See also the "Refresh the Identifier field value in UI" section in this KB article.
3. You can specify or seed the initial sequence value manually: either by editing the Sequence table in the database or using the standard XPO/XAF means by manipulating the Sequence objects, e.g.:

[C#]
using(IObjectSpaceos=Application.CreateObjectSpace(typeof(Sequence))){Sequencesequence=os.FindObject<Sequence>(CriteriaOperator.Parse("TypeName=?",typeof(E2829).FullName));sequence.NextSequence= 5;os.CommitChanges();}

See also:
How to create multiple sequences based on the a class property value, not one sequence per class type


Your feedback is needed!
We would greatly appreciate it if you share your feedback here in comments or rather participate in this short survey (~3 min).