When publishing dynamic component presentations using SDL Tridion 2011 SP1, I mainly use REL as an output format, however now I want to publish a DCP that contains an ASP.NET control tag. So I changed the output format of the template to ASCX and set up a repository for presentations of ASCX components to go to the file system in my web application. I see ascx files on disk, and as expected, I can see the control tag inside.
If I create an aspx page containing the same control tags, the output will be what I expect, however, when the presentation of the ASCX component is done by the component view assembler, instead of outputting the result from the control tag, it is empty. Plain text appears in DCP.
The functionality I need is very similar to the Trimion Dynamic Component control, and I already tried one of them with this architecture and succeeded. I even got to the point that both my tag and the tridion were placed one after another in the template. In this case, I see the output of the tridion tag, but not from my own, even if the links are connected in the same web.config.
So, I see that it is possible that the Tridion component view assembler executes ASCX DCP and successfully executes its child controls. Are there perhaps requirements for creating such a control to ensure that it appears in this way?
UPDATE:
DCP is published to the ascx file on my site. For testing purposes, I now publish tridion control in the same DCP, so the output on disk looks like this:
<tridion:DynamicComponentLink PageURI="tcm:34-667-64" ComponentURI="tcm:34-876"
TemplateURI="tcm:34-864-32" LinkText="Some page" runat="server" />
<xxx:ComponentLinkQS runat="server" ComponentUri="tcm:34-945"
QueryString="item=876" Text="Some page" />
DCP ComponentPresentationAssembler, , - . <xxx:ComponentLinkQS/> ASPX, .