smithsson68@gmail.com
Feb 15, 2011
  4649
(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

Please login to comment.
Latest blogs
AEO/GEO: A practical guide

Search changed. People ask AI tools. AI answers. Your content must be understandable, citable, and accessible to both humans and machines. That’s...

Naveed Ul-Haq | Feb 17, 2026 |

We Cloned Our Best Analyst with AI: How Our Opal Hackathon Grand Prize Winner is Changing Experimentation

Every experimentation team knows the feeling. You have a backlog of experiment ideas, but progress is bottlenecked by one critical team member, the...

Polly Walton | Feb 16, 2026

Architecting AI in Optimizely CMS: When to Use Opal vs Custom Integration

AI is rapidly becoming a core capability in modern digital experience platforms. As developers working with Optimizely CMS 12 (.NET Core), the real...

Keshav Dave | Feb 15, 2026

Reducing Web Experimentation MAU Using the REST API

Overview Optimizely Web Experimentation counts an MAU based upon the script snippet rendering for evauluation of web experiement. Therefore when yo...

Scott Reed | Feb 13, 2026