burningice wrote:
we did some mistakes.
XDT used to be a proprietary Microsoft technology that was just recently open sourced, so it haven't been easy for anyone to support this syntax but hopefully it can make it soon till the C1 Package Manager.I was thinking to use something like this:
- http://petemontgomery.wordpress.com/2010/09/20/microsoft-xdt-language/
- https://code.google.com/p/xdt/
we did some mistakes.
I have no idea though how to remove elements on installation, neither with XSL or xml merging (XmlFileMergePackageFragmentInstaller)We have found some leads like XSLT identity operation overloading (something with copy), but again we have some other tasks.
In regards to CompositeC1Contrib.RazorFunctions, do you have any specific reason for keep using it with C1 4.0?Nope. The error was introduced
- in one case by our client who is learning to use Composite C1, so he installed RazorFunctions wtih C1 v4.beta.
Suggestion: maybe Note/Warning that the package is obsolete on the compositec1contrib.codeplex.com site or
even better during package install -
in other case by our junior dev working on process steps for C1 web sites (he did batch install with AutoInstallPackages with throwing in several packages)