.Net user control not rendering in node, rendering fine in template?
I've created a .net user control in vs2010, all works fine in test .aspx page. Built control and moved .ascx file to usercontrols directory and assembly to bin directory. Created macro to render control. Checked use in editor, added macro to node, re-published node, macro doesn't render but in view source, i see something starting with
<?UMBRACO_MACRO ... />
However, if i put the same macro into a template, it renders the user control as expected.
Is it possible to get this to work by inserting the macro into a specific node or is there something about the template that is different to make the user control render?
umbraco v 4.0.4.2 (Assembly version: 1.0.3811.17115)
I spun up a new runway site, added my user control + macro and it rendered fine. Tracked the issue to a piece of xslt in the original site. Created a new doc type bypassing the xslt and the macro (and control) rendered as expected.
.Net user control not rendering in node, rendering fine in template?
I've created a .net user control in vs2010, all works fine in test .aspx page. Built control and moved .ascx file to usercontrols directory and assembly to bin directory. Created macro to render control. Checked use in editor, added macro to node, re-published node, macro doesn't render but in view source, i see something starting with
<?UMBRACO_MACRO ... />
However, if i put the same macro into a template, it renders the user control as expected.
Is it possible to get this to work by inserting the macro into a specific node or is there something about the template that is different to make the user control render?
umbraco v 4.0.4.2 (Assembly version: 1.0.3811.17115)
thanks in advance
//Mike
Should render the same in template and in RTE.
Do you have parameters for the macro ... be sure you check the Show box for each parameter to allow entry when adding to a node.
Daniel
I spun up a new runway site, added my user control + macro and it rendered fine. Tracked the issue to a piece of xslt in the original site. Created a new doc type bypassing the xslt and the macro (and control) rendered as expected.
Appreciate the response though,
//Mike
Very glad you figured it out... awesome...
is working on a reply...