I haven't tried it but just as a thought, what if you moved the
processing from pre-execute to the main web site's code-behind. I
presume you're publishing ASPX and not HTML.
What I mean is you could pu the following into your template...
<asp:XmlDataSource runat="server" id="myXml">
<Data><Root><![CDATA[<%txt_RedDot_Placeholder%>]]></Root></Data>
</asp:XmlDataSource>
Then in your code behind, or in-line somewhere else in the file, you
can get the value of the field by...
XmlDocument xdoc = new XmlDocument();
xdoc.LoadXml( myXml.Data );
string myString =
((XmlCDataSection)xdoc.DocumentElement.FirstChild).Data;
Then you can manipulate it as you see fit.
HTH.
Regards,
Richard Hauer
====================
5 Limes Pty Limited
www.5Limes.com.au
reddotrich wrote:
> Hi Tony,
>
> Thanks for your advice, we did start down the road of xml files,
> partly to try and stay within the Red Dot publishing methodology, but
> switched to WCF as a more on demand solution and a more direct route
> into the rest of our publishing structure. The reason we want to
> remove the render tag was because we have been advised it may improve
> the efficency of our publishing. At this point it was meant to be
> only a quick refinment rather than a re-work of the publishing
> process.
>
> Cheers
>
> Rich.
>
> On Jun 29, 10:29 am, Tony Gayter <[email protected]> wrote:
> > Why don t you make the templates in reddot ouput the data from reddot into
> > xml files and then you can remove all c# preexecute from teh cms and you
> > could then have teh c# fully in visual studio with full dubugging?
> >
> > We use this method by outputting the static pages for the site and also
> > outputting the data as xml so that c# can read this data and use it
> > elsewhere for things like paginated/filtered lists etc....
> >
> > In some cases we mix both and output an xml datasource into the published
> > page so its not two seperate files.
> >
> > On 29 June 2010 09:00, reddotrich <[email protected]> wrote:
> >
> >
> >
> > > Hi,
> >
> > > We are putting it in a c# object in order to get it out of Red Dot.
> > > Our website is run off a db and uses objects to pass the data around.
> > > The most important reason is that only part of the site is edited in
> > > Red Dot, so we need to combine the data from Red Dot with the data
> > > from the other sources that is already in the database, as we are all
> > > ASP.Net C# programmers, the easiest thing to do seemed a WCF service.
> > > We do not use the files that Red Dot publishes to build our site at
> > > all, we just use the data. We do realise that we are breaking the
> > > classic CMS publishing model that Red Dot is based on, but it seemed
> > > like the best solution at the time given our knowledge base and time
> > > constraints, but we are open to suggestions.
> >
> > > Rich
> >
> > > On Jun 28, 8:44 pm, TonyGayter <[email protected]> wrote:
> > > > Understanding why you have to write this out into c# in the first plac
> > > > would
> > > > be the first question I would ask.
> >
> > > > On Jun 28, 4:49 pm, reddotrich <[email protected]> wrote:
> >
> > > > > All,
> >
> > > > > I have been looking at simplifying my templates recently, in order to
> > > > > attempt to streamline our publish. It has been recommended that we
> > > > > take out the render tags from our pre-execute code, however I am
> > > > > struggling to find an alternative option.
> >
> > > > > We get our data out of Red Dot by adding it to c# objects in pre-
> > > > > execute code blocks, however the text editor fields do not play nice
> > > > > with c# strings, so we used the Escape:HtmlEncode render tag to get
> > > > > round this as it returns text that we can place in a string.
> >
> > > > > I have looked at the htmlConvertTable as an option, but this happens
> > > > > too late in the page life cycle, so would be applied to the field
> > > > > after our pre-execute code. Does anyone have any suggestions?
> >
> > > > > extract from one of our templates from within a pre-execute block
> > > > > blog.Description = @"<%!!
> >
> > > Escape:HtmlEncode(Context:CurrentPage.Elements.GetElement(String:txt_BlogText).Value)
> > > !!
> > > > > %>";
> >
> > > > > Rich- Hide quoted text -
> >
> > > > - Show quoted text -
> >
> > > --
> > > You received this message because you are subscribed to the Google Groups
> > > "RedDot CMS Users" group.
> > > To post to this group, send email to [email protected].
> > > To unsubscribe from this group, send email to
> > > [email protected]<reddot-cms-users%[email protected]>
> > > .
> > > For more options, visit this group at
> > >http://groups.google.com/group/reddot-cms-users?hl=en.- Hide quoted text -
> >
> > - Show quoted text -
--
You received this message because you are subscribed to the Google Groups
"RedDot CMS Users" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/reddot-cms-users?hl=en.
