Posts under CMS
How to store custom data in Episerver – Part IV: Migrate to Entity Framework
In the previous parts of this series, I demonstrated how you can store custom data in Episerver using the Dynamic Data Store and how to make the most out of it. However, DDS has many serious drawbacks. In this blog post, I want to present to you an alternative solution which works much better: Entity
How to store custom data in Episerver – part III: Separate custom big tables
In the first two parts of this series, I wrote about how you can store your data using Dynamic Data Store (Part I) and how Episerver implemented DDS (Part II). Now we’ll learn about a more effective way of storing your data in Dynamic Data Store. By default, Episerver keeps data of all stores in one big
How to choose the perfect CMS for your media site [with use cases]
If you’re an aspiring media or publishing company then you’re probably on the lookout for the best content management system (CMS) that can help you manage your content efficiently. So, what is the perfect CMS for your media site? This, of course, depends on your needs, your budget, how urgent you need it and the
How to store custom data in Episerver – Part II: Dynamic Data Store implementation
In Part I, I wrote about the basic usage of Episerver’s Dynamic Data Store (DDS). Now you can find out how Episerver implemented its solution of storing data and how exactly yours is stored. Behind the Episerver code You already know how to retrieve and update data using DDS, but what exactly happens in your database
How to store custom data in Episerver – Part I: Dynamic Data Store basics
When you work with Episerver you might need to store extra data in your database. A simple example would be when you want to save statistics of your page views. You could think: “Hey! I can have another hidden property on my PageData object and store page views count in it.” Let me stop you