Yes, the output from Razor is parsed by Composite C1 and to be able to pick up on things like embedded function markup and custom html head elements the output needs to be well structured.
I just added support for CDATA sections - think this should serve you quite nicely - if you grab the latest 4,0 sources and compile composite.dll you should have the feature.
I just added support for CDATA sections - think this should serve you quite nicely - if you grab the latest 4,0 sources and compile composite.dll you should have the feature.
<![CDATA[ (markup here) ]]>
The string that goes inside the CDATA declaration will sail through the entire Composite C1 rendering engine untouched and will be emitted 'as is' at the end (the CDATA declaration will be removed at this point). Should save you the ARGH moment.