Spence continues his take on undocumented interfaces. I'd also like to extend the argument to the use of reflection to get at values and data-structures that, for reasons known only to themselves, designers of libraries chose to remain private.

Before casting any stones, I'll confess that for one project due to the lack of machine parsable data from the XML Validating Reader Schema Exception (lets face it, the Message property is totally unparsable) I had to resort to reflection in the callback to access data in the schema exception that wasn't and still isn't exposed (in FW 1.1)  (res and args[]) to enable me to generate both machine and human friendly parse failures. I've haven't checked FW2.0 to see if these values are still present and if not this may present a problem for the dev's maintaining this code under FW2.0 in the future.

Anyone else for humble pie?