Last updated: Dec 09 2016
Configuring dynamic content (Legacy)
Note: Dynamic content is deprecated. Use blocks instead. While existing solutions will continue to work, you should not build new solutions on this API. It will be phased out in the future.
If you use the DynamicContentPlugIn attribute, you do not need to manually register your plug-in in this way. If you do not use the attribute, you need to register the plug-in in the episerver section of web.config as shown in the following example:
<episerver> <dynamicContent> <controls> <add description="My example dynamic content class" name="ExampleDynamicContent" type="MyNamespace.MyDynamicContent, MyDll" /> </controls> </dynamicContent> ... </episerver>