smithsson68@gmail.com
Feb 15, 2011
  4251
(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
Opti ID overview

Opti ID allows you to log in once and switch between Optimizely products using Okta, Entra ID, or a local account. You can also manage all your use...

K Khan | Jul 26, 2024

Getting Started with Optimizely SaaS using Next.js Starter App - Extend a component - Part 3

This is the final part of our Optimizely SaaS CMS proof-of-concept (POC) blog series. In this post, we'll dive into extending a component within th...

Raghavendra Murthy | Jul 23, 2024 | Syndicated blog

Optimizely Graph – Faceting with Geta Categories

Overview As Optimizely Graph (and Content Cloud SaaS) makes its global debut, it is known that there are going to be some bugs and quirks. One of t...

Eric Markson | Jul 22, 2024 | Syndicated blog

Integration Bynder (DAM) with Optimizely

Bynder is a comprehensive digital asset management (DAM) platform that enables businesses to efficiently manage, store, organize, and share their...

Sanjay Kumar | Jul 22, 2024

Frontend Hosting for SaaS CMS Solutions

Introduction Now that CMS SaaS Core has gone into general availability, it is a good time to start discussing where to host the head. SaaS Core is...

Minesh Shah (Netcel) | Jul 20, 2024

Optimizely London Dev Meetup 11th July 2024

On 11th July 2024 in London Niteco and Netcel along with Optimizely ran the London Developer meetup. There was an great agenda of talks that we put...

Scott Reed | Jul 19, 2024