I don't think it's too late. I would suggest that this issue be documented and *IF* it's an MS bug, a link or reference to a PSS Hotfix be made available. That way those who hit the issue can resolve it on the end where it's being caused.
Funny thing, there is "XML" word used in the VS .NET solution/project file description.
<http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vsintro7/html/vxorimanagingprojectssolutions.asp>
So, Mirosoft does not inform anybody what is the internal format of all those files.
And now, if we would like to inform them about the bug, MS simply can answer that is not a bug because solution/projct files are not XMLs ;-)))
The friendly error/exception message is still a must though and could even reference the known issue.
Agreed.
Best regards
-- Mateusz Łoskot, mateusz (at) loskot (dot) net Registered Linux User #220771, Debian (Sarge)
------------------------------------------------------- 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
