smithsson68@gmail.com
Feb 15, 2011
visibility 4828
star star star star star
(1 votes)

Dynamic Data Store : Easier Store Creation and Remapping (for CMS 6 R1)

As mentioned in my previous blog entry

Dynamic Data Store : Easier Store Creation and Remapping, I have developed an open-source version of the code which works with CMS 6 R1 (and Community 4 R1).

The main differences are:

  • The DdsAutoCreateAttribute class should be used instead of the EPiServerDataStoreAttribute / AutomaticallyCreateStore property
  • The DdsAutoRemapAttribute class should be used instead of the EPiServerDataStoreAttribute / AutomaticallyRemapStore property
  • The DdsAutoPropertyRenameAttribute class should be used instead of the EPiServerDataPropertyRenameAttribute
  • The namespace to include for the System.Type extensions (GetStore(), CreateStore(), GetOrCreateStore()) is EPiServer.Samples.DdsExtensions

Unlike the CMS 6 R2 built-in version, this version uses an initialization module which runs on application start to scan for the above attributes. What this means is that it will add some time to your site’s start-up time and if you exclude your assemblies (containing your Types decorated with the attributes) from the assembly scanning list in the EPiServerFramework.config (see this blog entry for more info about this) then your Types will not be found by the scan and therefore their stores will not be auto created or auto mapped.

Also note that the initialization module is coded to throw an exception if run against a CMS 6 R2 site, i.e. a version of the EPiServer.Data assembly with version number 6.2.217.x or higher. This is because you should use the built-in functionality supplied by the EPiServer.Data assembly is this case.

The source code and example of how to use it can be found here on the Code section of EPiServer World.

A binary ready to drop in the bin folder can be found here.

Enjoy!

Feb 15, 2011

Comments

error Please login to comment.
Latest blogs
Composition Over Inheritance: Why Your Content Contract Is Not a Base Class

Inside the structural conformance pattern in SaaS CMS — from server-side inheritance to pipeline governance. A contract in Optimizely SaaS CMS is...

Vipin Banka | Sep 19, 2026

Optimizely Opti ID Integration: Why the API Key Was Missing from the DXP Management Portal

While working on an Optimizely CMS 12 Opti ID integration recently, we ran into an issue that initially appeared to be related to SSO authenticatio...

Madhu | Sep 18, 2026 |

Extending a Contract: What You Can Override

Contracts share fields across content types — but not every field setting can be overridden. Push the same contract onto several components, and CM...

Chirag Khanna | Sep 18, 2026 |

Building a Blazor Server UI Inside the Optimizely CMS 13 Admin Shell

What I learned shipping a Blazor Server UI inside Optimizely CMS 13 — Razor components in a NuGet package, the Blazor hub next to MapContent(),...

Stanisław Szołkowski | Sep 17, 2026 |