Did Microsoft.VisualStudio.QualityTools.UnitTestFramework slip through the cracks?
I've been plagued lately in that whenever I create a new unit test, I have to manually add a reference to the Microsoft.VisualStudio.QualityTools.UnitTestFramework assembly. I'm left scratching my head wondering why I have to do that and if I've done something wrong.
In my spare time this evening, I started searching for a resolution (first via Windows Live then via Google) and finally came across this article from the VSTS Quality Tools team that indicates this was an issue with the July CTP ... way back in August of 2005!
Short solution is to modify the SimpleUnitTest.vstemplate file that lives in %VSINSTALLDIR%\Common7\IDE\ItemTemplates\CSharp\1003\SimpleUnitTest.zip and add an <Assembly>Microsoft.VisualStudio.QualityTools.UnitTestFramework</Assembly> element within the <References> section.
Why am I seeing this same issue with production bits? At a minimum, this post contains the phrases I was searching on and maybe it'll help someone else who adopts the programming-by-searching model of development.