I might as well handles the two "90% issues" together.
A lot of people ask about the license for the bag-o-tricks.
Here's the story.
Most of the code in the bag-o-tricks was written while I was at Microsoft. I never took the time to formally license it while at Microsoft.
Given the type of code and how it's been released, I think it's more than safe to consider it under the Microsoft Public License.
I say "I think" because I'm not a lawyer and I'm not 100% sure how to deal with code that I wrote while at Microsoft--and therefor, technically, "owned" by Microsoft.
I'd bet $10 you won't get sued if you use it any way you see fit. But that's as far as I'll stick my neck out. Being on the other side of the fence from the MSFT legal department is a bit...uh...interesting.
Everything that's new since I left I've put under the MIT license, which I find pretty good.
I'm trying to keep a clear firewall between that code, even going so far as to keep the namespaces separate.
I hope this helps a little. I know folks are looking to use individual controls in their commercial applications.
While I can't give you a 100% guarantee about the code, I can say I'm pretty sure you have nothing to worry about.
I'm not sure if that sounds more like lawyer speak or marketing speak.
Happy hacking (except where prohibited)