So Nice I Tried it Twice
Yeah, the disco daze wuz good uns... As long as I'm on the "Papa B Dumb" kick, I'll add a most embarrassing errata for WdfVerifier- this will be there in the official 6001 WDK, much to my eternal shame...
With all the things to test on WdfVerifier, you'd think Papa would make sure that UMDF debugger launching would work with the default debugger locations from installing Debugging Tools For Windows. Papa sure would have said so, right up until he did his late-in-the game manual tests for said WDK.
Papa forgot that if a path has spaces in it, you need to use double quotes around it to form a working command line. Well, actually not even Papa would forget that- as soon as the debugger launched and then complained it couldn't find "Files\Debugging Tools For Windows 64-bit -<debugger switches papa done fergot>" he knew what he'd done, and he knew it wasn't good, and he also knew it was too late to do anything about it but realize he was a dunderhead and that work item he filed for getting some regular automated testing was a lot more necessary than hoped.
Not what anyone should expect from QA. Live I shall, learn- well, we'll find out about that one if I'm lucky enough to get another shot at that sort of thing.
There is a workaround, but it's ugly- install your package (or copy it after installation) to a path with no spaces in it.
It was easy enough to fix, of course- but it won't get out there for a while, now.
On the bright side, at least, I'm not sure anybody actually uses this feature [nobody mentioned this flaw, after all], nor this tool. So p'rhaps 'tis much ado about nothing...
With that thought, I'll go see if there's anything useful I could be doing.
