Well, I couldn 't let it go. I'm attaching my code here, if anyone's interested. I can't use XML assertions that don't support namespaces, basically; I want my XPath expressions to be correct. No "*::MyAttribute" or "*::@*[namespace-uri() = 'urn:tony:nassar']" please!
I'm actually using this code at work; I haven't implemented the Resolver feature, but at some point I'll have to, because I like to embed my XSLTs as resources when I can, and the XslTransform object won't be able to find them. Why can't I use the usual XPath and XmlAssert assertions? Precisely because they don't know the proper "evaluation context" for a test or fixture (or suite, or whatever). Since they're static classes, I do *not* want to load that information into them; it would break concurrently-running tests that expect some other evaluation context (usu. the default). --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "MbUnit.User" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/MbUnitUser?hl=en -~----------~----~----~----~------~----~------~--~---
