|Number of votes:||0|
As promised by Daniel in part one, here is part two!
In this post I’ll try to explain how we could automatically deploy our mapped properties that we use to get strongly typed properties (see Daniels post) in our templates by using some reflection, conventions and attributes.
First we create a new Web Form/Page Template in Visual Studio and change the inheritance from EPiServer.TemplatePage to our own extended class TemplatePage<T>.
To add properties we create a class-file for the properties that we will use in our template. Neither the PageType or associated properties has to be present in EPiServer.
PageTypeBuilder is the tool responsible for creating and updating PageTypes and properties in EPiServer.
To execute it, we need to add some code when the application starts, for instance in a PlugIn or in Global.asax.
PropertiesBase is added as a generic type and the BuildPageTypes method takes a params string with names of assemblies to scan for mapping classes.
The tool will look for classes that are subclasses of T (= PropertiesBase) and build PageTypes out of these. Each class will become a PageType and each property will be added as a EPiServer property.
For global default settings a PageTypeBuilderSettings object is used. Here it’s possible to add virtual path, default tab, if unmapped properties should be deleted or not and if existing properties should be updated.
But what about Help texts, Tabs and Descriptions? The tool will guess/use conventions for these. The class name - “Properties” will be the name for the PageType (class “StartProperties” = PageType “Start”), if no Tab name is specified, the property will be added to the “Information” tab (if not overridden by the global settings) and so forth.
To override this and to add additional information we could decorate our mapping classes with attributes. Attributes could be Name of the page/property, Edit Heading, Tab, Default value, Language specific and some others. Pretty much the same as we have in Admin mode.
If we have properties that are shared between templates these could be added to either the PropertiesBase class or to another class that inherits PropertiesBase and then use this class as subclass for our mappings. Since we don’t want this class to be a PageType there is a [Ignore] attribute that could come in handy.
The sort order of the properties will be the same as the order in our mapping classes.
some pictures might say more than 1000 words…
For mapping class we use this:
Since we add, update and delete properties when the application starts we will not depend on a specific database. This could be useful in a continuous integration scenario where the development database differs from the database used for test and of course if all developers in a team have their own (local) database.
This tool is pretty much a “proof of concept” that could be used to complement our way to handle strongly typed properties. It' can not (yet) handle all features of PageTypes that exists in EPiServer (dynamic properties to mention one) but will ease the pain of creating PageTypes and adding properties ;)
So, what do you think?