VS wants to tag our NUnit-based test project so
VS wants to tag our NUnit-based test project so

In Microsoft's own words[1]:

> To support third-party test frameworks, like NUnit and XUnit, Visual
> Studio 2012 loaded Test Explorer on solution open, regardless of
> whether it contained test projects. This added seconds of delay to
> startup and solution open scenarios for all users, majority of whom
> don't use tests.

> In Visual Studio 2013, we changed it so that Test Explorer package
> is loaded only when the solution contains one or more test projects.
> Test projects are identified in two different ways. Projects
> created from one of the built-in unit test project templates are
> identified using project type GUIDs. Other types of projects, such
> as Class Library project with xUnit or NUnit tests, are identified
> by Test Explorer during first test discovery and "tagged" with the
> <Service/> item.

[1] https://connect.microsoft.com/VisualStudio/feedback/details/800245/vs2013rc-adds-to-vs2012-c-project-section-itemgroup

morelinq/MoreLINQ,ddpruitt/morelinq,fsateler/MoreLINQ,ddpruitt/morelinq,fsateler/MoreLINQ,morelinq/MoreLINQ