Storing XML as a text nodes in another XML (which causes the escaping to happen) is usually not the right way to do things. Is there a way in Linq to XML to deal with this?įirst I would try to get the input as a real XML. How can I get around the escape characters?Īt one point, in the stored procedure that is creating the XML, I was replacing the escape character, but I stopped. I know my code is working because when I manually correct these escape characters, I'm able to pick up these elements. I'm unable to pick up the Property elements within Properties due to the escape characters. PropertyID="14" PropertyName="ErrorMessage"/& gt PropertyID="17" PropertyName="Width"/& gt & lt Property PropertyID="11" PropertyName="ID"/& gt & lt Property PropertyID="12" PropertyName="TextMode"/& gt & lt Property & lt Property PropertyID="1" PropertyName="SelectedDate"/& gt & lt Property I'm using Linq to XML and within my XDocument I have some XML that looks like:
0 Comments
Leave a Reply. |