File: Microsoft.VisualStudio.QualityTools%20-%20readme.txt

package info (click to toggle)
mono-reference-assemblies 3.12.1%2Bdfsg-2
  • links: PTS, VCS
  • area: main
  • in suites: stretch
  • size: 604,240 kB
  • ctags: 625,505
  • sloc: cs: 3,967,741; xml: 2,793,081; ansic: 418,042; java: 60,435; sh: 14,833; makefile: 11,576; sql: 7,956; perl: 1,467; cpp: 1,446; yacc: 1,203; python: 598; asm: 422; sed: 16; php: 1
file content (21 lines) | stat: -rw-r--r-- 988 bytes parent folder | download | duplicates (36)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
Visual Studio 2010 changes the .csproj file's reference to Microsoft.VisualStudio.QualityTools.UnitTestFramework
aggressively upon each edit of test projects. In particular, it changes the following:

    <Reference Include="Microsoft.VisualStudio.QualityTools.UnitTestFramework" Condition=" '$(BuildPlatform)' == 'DESKTOPCLR' " />

into

    <Reference Include="Microsoft.VisualStudio.QualityTools.UnitTestFramework" />

dropping the conditional include. In order to reach a fixpoint when opening the project, we choose to include
a file with the name Microsoft.VisualStudio.QualityTools.UnitTestFramework.dll in every reference assemblies
folder. This file actually contains the testing suite used and ***IS NOT NECESSARILY*** the same as the one
used for desktop CLR (which has that name).

In particular, for Silverlight, this file is a rename of

    Microsoft.VisualStudio.QualityTools.UnitTesting.Silverlight.dll

into

    Microsoft.VisualStudio.QualityTools.UnitTestFramework.dll