How do I make modules for R2?
The new public templates comes with a ps1-file used with EPiServer Installation Manager. This introduces the option of importing .episerverdata files (which is cool! :), but how do I
Did you ever figure out how to do this? As usual the documentation seems to be non-existant. Grrrrrr!
Hi Peter and Thomas.
Have you cheked out this blog post by Fredrik Tjarnberg?
Br, Tore Gjerdrum
No, I hadn't seen that but it looks great. Ive used Wix and PowerShell before so this should work fine.
While I understand the need to go this way for complex installations, most of the stuff we do is pretty simple to deploy with the old zip file and xmlupdate so this now adds a lot of complexity we dont really want.
ZIP Install for CMS 5 R2 is now available at:
Why does the following code change my dynamic content instead of adding a new one? Or is there another way to accomplich this?
I've added this to my web.config.xmlupdate:
<modifications> <add path="/configuration/epi:episerver/epi:dynamicContent/epi:controls"> <add description="My DC" name="MyDC" type="MyNamespace.MyDC, MyAssembly" /> </add></modifications>
You need to include "___keyAttributes" in your xml:
<add path="/configuration/epi:episerver/epi:dynamicContent/epi:controls"> <add description="My DC" name="MyDC" type="MyNamespace.MyDC, MyAssembly" ___keyAttributes="name" /> </add></modifications>
_keyAttributes is a comma separated list of attribute names. When the XML blocks are merged, attribute values of the named attributes are used to identify existing elements in the target document corresponding elements in the source block. If an element with matching attribute values are found in the target document the element will be updated, otherwise a new element will be added.