2.5.0

DataSourceLoader.LoadAsync

Usage:

• Refer to the NorthwindController in the Sample project.

Supported LINQ providers:

• EF Core (all versions)
• EF 6
• NHibernate
• DevExpress XPO (starting with 18.2)

Infrastructure to register other LINQ providers:

• IAsyncAdapter.cs
• CustomAsyncAdapters.RegisterAdapter
• Example

2.5.0-rc1

See 2.5.0.

2.4.4

• AJAX via devextreme/core/utils/ajax (#374)
• Disable PaginateViaPrimaryKey without Take (#375)

2.4.3

Per #336 (comment), the Skip > 0 condition is removed, and PaginateViaPrimaryKey works equally for any page, if enabled.

2.4.2

• Fix TypeScript declarations for DevExtreme 18.1 (#368)

2.4.1

CAUTION: this release has a know issue (#368)

Changelog

• Don't assign byKey, totalCount if loadMode=raw (#365)
• Actualize TypeScript declarations (#366)

2.4.0

createStore now accepts the following CustomStore options:

• onLoading, onLoaded
• onInserting, onInserted
• onUpdating, onUpdated
• onRemoving, onRemoved
• onModifying, onModified
• onPush
• loadMode
• cacheRawData

2.3.0

• New CustomFilterCompilers.RegisterBinaryExpressionCompiler extension point to intercept the translation of binary expressions in filter. Enables the scenarios described in #277.

  Examples:

  • [ "Products", "contains", "text" ] → .Products.Any(p => p.Name.Contains("text")) - 'contains' operation on a one-to-many collection.
  • [ "Tags", "contains", "news" ] → .Tags.Contains("news") - 'contains' operation on a collection of strings.

  Use this API in Global.asax or Startup.cs.

• Better error messages (#351)

2.2.1

• Fixed ArgumentOutOfRangeException with PaginateViaPrimaryKey (issue #349)

2.2.0

• New experimental option DataSourceLoadOptionsBase.PaginateViaPrimaryKey (#346)

  With this flag set to true, keys and data are loaded via separate queries. This may result in a more efficient SQL execution plan.

  Thanks to @coeamyd for their initial suggestion, query analysis and testing.
  Related discussion: #336