Hi,

I'm writing a .NET winforms app that serves as an email client. Users can
store message templates. This is done via an XML document for loading and
saving the templates. When the template is loaded, it's displayed in the
message textbox. Currently, this is the end of the XML phase. Now the user
can edit the textbox before sending the message and the content of the
textbox will be sent when the user hits send.

Now to thicken the plot, emails (and templates) can contain "replacables."
For example, I could have %Relevant Product% and before the message is sent,
it will contain, in place of that, the value "Wrench". I'm doing this by
simply calling string.replace several times (once for each replacable). The
list of values is populated every time the application is started (a textfile
is generated by another app which starts the mail client and I parse the
values and place them in a templated list object.)

This "replacables" approach is somewhat limiting. Some replaceables are
built from other replaceables. Example: %Customer Full Name% consists of:
%Customer First Name% %Customer Last Name%

Is there a way to instead, implement an XML based solution? My primary
concern is that once the template is loaded, I have no say as to what
characters my users will type into the textbox of the message so they might
not conform to XML standards. Any thoughts?

Thanks...

Hi Ben,

Based on my understanding, you have put the whole Xml into a Textbox and
let your user edit it to complete the template.

Xml is used for storing data. It is not suitable for data conversion.
Although we can use XSLT to do the conversion, as far as I can see, it
won't be better than using the String.Replace method.

If you have nested replacables, you have to call the replace procedure
recursively to make sure that all the tags have been replaced.

If anything is unclear, please feel free to let me know.

Kevin Yu
Microsoft Online Community Support

==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
==================================================

(This posting is provided "AS IS", with no warranties, and confers no
rights.)