smithsson68@gmail.com
Dec 22, 2009
  9125
(1 votes)

Dynamic Data Store Feature List in EPiServer CMS 6 Release Candidate

The EPiServer CMS 6 Release Candidate is quite near now so I wanted to list the features in the Dynamic Data Store that have made it this far.

Saving Data

+ Save compile-time typed data (normal .NET classes)

+ Save runtime typed data (using EPiServer.Data.Dynamic.PropertyBag class)

Loading Data

+ Load data as the Type is was saved as

+ Load data into a PropertyBag

+ Load data into a different .NET Type to the one that was saved

Finding & Searching Data

+ Simple Find using equality matching for one or more properties

+ LINQ support for more advances scenarios

POCO Support

+ Internally managed identity for object graph support

+ Stateful store instances for CRUD operations

+ Ability to provide identity separate from object when saving

Type to Store Mapping

+ Globally using EPiServer.Data.Dynamic.GlobalTypeToStoreMap

+ Globally using EPiServer.Data.Dynamic.EPiServerDataStoreAttribute

+ Locally using EPiServer.Data.Dynamic.TypeToStoreMapper delegate

Store to Custom Big Table Mapping

+ Using EPiServer.Data.Dynamic.StoreDefinitionParameters

+ Using EPiServer.Data.Dynamic.EPiServerDataTableAttribute and EPiServer.Data.Dynamic.EPiServerDataColumnAttribute

Indexing of Properties

+ Using EPiServer.Data.Dynamic.StoreDefinitionParameters

+ Using EPiServer.Data.Dynamic.EPiServerDataIndexAttribute

Custom Mapping of .NET Type

+ Using System.Runtime.Serialization.DataContractAttribute and DataMemberAttribute

+ Using EPiServer.Data.Dynamic.EPiServerDataContractAttribute and EPiServerDataMemberAttribute

+ Using EPiServer.Data.Dynamic.ITypeHandler

Store Re-mapping

+ Add new properties

+ Remove properties

+ Rename properties

+ Change data type of properties (where convertible)

Type Resolving

+ Automatic .NET Type resolving (e.g. when an assembly gets a new version number)

+ Programmer controlled .NET Type resolving via Assembly redirects

 

I aim to provide some simple How To’s for all of the features over the coming days and weeks.

Dec 22, 2009

Comments

Sep 21, 2010 10:33 AM

The How To´s could be presented at Techforum in Norway 21th of January? We look forward to see and hear you!

Sep 21, 2010 10:33 AM

Indeed! Looking forward to it.
/ Paul Smith

Please login to comment.
Latest blogs
Display Child Pages in Content Delivery API Response

The below example will implement an instance of IContentConverterProvider to customise the serialisation of PageData and output child pages in the...

Minesh Shah (Netcel) | Oct 4, 2022

Bring the Report Center back in Optimizely CMS 12

The Report Center has been a part of Optimizely CMS since its first debut in version 5R2 in 2008, but in CMS 12, it's removed! Don't despair! Make...

Tomas Hensrud Gulla | Oct 4, 2022 | Syndicated blog

Customizing Property Lists in Optimizely CMS

Generic property lists is a cool editorial feature that has gained a lot of popularity - in spite of still being unsupported (officially). But if y...

Allan Thraen | Oct 2, 2022 | Syndicated blog

Optimizely names Luminary Senior Developer, Ynze Nunnink, OMVP

Luminary Senior Developer and Optimizely Lead, Ynze Nunnink has secured the coveted position of Optimizely MVP. Earning a Platinum badge for his...

Ynze | Oct 2, 2022 | Syndicated blog

Content Delivery API – The Case of the Duplicate API Refresh Token

Creating a custom refresh provider to resolve the issues with duplicate tokens in the DXC The post Content Delivery API – The Case of the Duplicate...

David Lewis | Sep 29, 2022 | Syndicated blog

A multi-brand strategy in Optimizely DXP

The Optimizely Digital Experience Platform (DXP) is ideally suited to digital projects featuring multiple websites or applications. Here, we showca...

Ynze | Sep 29, 2022 | Syndicated blog