Although the Visual Studio project files look like XML, and will usually parse with an XML parser, they're not actually legal XML because of things like this. (It should've been obvious they weren't being done with a real XML generator when you look at their layout... no XML generator I've ever seen would create such ridiculously white-space heavy elements.)
I think there are three options: 0. Don't use filenames that cause the problem. 1. Scan the file contents before parsing, and fix up errors like this, THEN use the XML parser to parse the fixed-up version. 2. Write a new parser and avoid the XML parser altogether. Option 0 isn't very good, but obviously is the easiest choice if it's something you have control over. It's also coincidentally the only option available to someone who isn't willing to get in and fix the solution task. Long term, option 1 seems best at first glance. While the document isn't XML, it would take very little work to make it XML. Although it will, on first glance seem kind of messy, it surely is a LOT less work than actually writing a parser. In fact, option 1 seems to me like it could be done in an afternoon by a properly motivated individual. ;) - Brad -- Brad Wilson http://www.dotnetdevs.com/ http://dotnetguy.techieswithcats.com/ "Why do I think that people who live and breathe SQL are from a distant alien culture?" - Stuart Celarier on the WTOT mailing list ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ Nant-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-users
