Sometimes you want to able to save data that is not a page or a content block. Examples could be data like comments created by visitors or orders in your webshop. An easy way to save such data is using EPiServers build-in Dynamic Data Store.
In this post I take a look at what blob storage exactly is, why it could be interesting and how it works in EPiServer. By default EPiServer uses blob storage to store all its content. Further I take a look at how to access stored media assets from code and show them in a view and how to save an uploaded image as a blob in the Media panel.
In this tutorial we will add Twitter Bootstrap to our EPiServer project and we will create some base classes and our first ViewModel. Further I will explain the purpose of these base classes and the need for a ViewModel. Most of this is standard ASP.NET MVC so if you are already familiar with that you can probably skip this post.
Since a couple of weeks when I started with EPiServer I experimented a lot. Here is a quick summary of some code fragments that I found on the internet that can be very usefull in some cases. I am not going into detail about these code fragments because honestly I dont understand all of it (yet).
Welcome to my first blog where I will start explaining how to create a simple website that uses EPiServer 7.5 as CMS. In the next tutorials I will extend the functionality of the website and I will dive deeper in more advance topics related to EPiServer. I assume that you have basic knowledge about the CMS itself. In other words that you know how to work with the CMS itself.