Re: Error and Fatal Error
If only it were that simple, Toby.
The problem is that there are tags in the strings - it is XML.
System.Security.SecurityElement.Escape and HtmlEncode
would change the angle brackets in the tags too.
It comes down to this: If you want to handle a string in code
as a string don't let XML get anywhere near it. Once you
turn it into anything like XML you will have to cater for endless
overheads if you ever have to parse it as a string and then
later as XML again.
The danger now to the app is that the use of XML internally
has bound that app to all sorts of unexpected complexities
which might make it expensive to maintain (in terms of the
skills required for developers hired to maintain it). That's the
real truth about the cost of implementation of XML - it is
higher many expect and can be a gotcha which causes
I do think the W3C could aleviate this cost of implementation
though. MicroXML might be one way; improved parser
conformance requirements another. It probably comes down
to bottom line considerations though like 'Who would pay for
this?'. So I'll stick with it as it is, warts and all, and hope
developer colleagues are willing to put up with the challenges.
Stephen D Green
On 18 July 2011 16:19, Toby Considine <Toby.Considine@gmail.com> wrote:
As the originator is a .NET programmer
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]
PURCHASE STYLUS STUDIO ONLINE TODAY!
Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!
Download The World's Best XML IDE!
Accelerate XML development with our award-winning XML IDE - Download a free trial today!
Subscribe in XML format