November Happy Hour will be moved to Thursday December 5th.
AI OnAI Off
Modules and web.config.xmlupdate
Hey there
Did you ever figure out how to do this? As usual the documentation seems to be non-existant. Grrrrrr!
Cheers
Jan 06, 2009 6:18
Hi Peter and Thomas.
Have you cheked out this blog post by Fredrik Tjarnberg?
http://labs.episerver.com/en/Blogs/Fredrik-Tjarnberg/Dates/112488/12/Module-Installation-EPiServer-CMS-5-R2---Getting-started/
Br, Tore Gjerdrum
Jan 06, 2009 10:09
Yes, I know. http://world.episerver.com/Forum/Pages/Thread.aspx?id=26873&epslanguage=en also contains tips on how to include web.config.xmlupdate into the package.
#26886
Jan 07, 2009 12:20
Hi
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.
Cheers
Jan 10, 2009 22:14
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>
Oct 20, 2009 16:07
You need to include "___keyAttributes" in your xml:
<modifications>
<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.
Oct 21, 2009 8:32
This thread is locked and should be used for reference only. Please use the Episerver CMS 7 and earlier versions forum to open new discussions.
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
- register my module for use in the installation manager?
- merge web.config changes like using the .xmlupdate-file in R1?
Shouldnt there be an option of "install custom module" in EPiServer Installation Manager where I could point to an exisiting .zip-archive and let the Manager do the rest, or do I have to write my own powershell-script?