In TFS 2010, I configured some CI builds that also run MSTest unit tests. This works fine, except for one solution where I usually (but not always) get the following build error (not a test runner):
C: \ Program Files (X86) \ MSBuild \ Microsoft \ VisualStudio \ v10.0 \ TeamTest \ Microsoft.TeamTest.targets (14): The reference to the object is not installed in the object instance.
The value Logging Verbosityfor the assembly definition is set to Diagnostic. Some social.msdn.com posts suggest this to get rid of this random error. If it were by chance, by the way, we could get around this by planning another assembly if it is broken for the above reason. However, this is not so, and it takes too much time to create.
Although this is a build error, it can be fixed by installing Disable Testsat True. However, I want to run a test. Does anyone know how to fix this? Other (working) solutions are often subsets of projects All Projects. All Projectis a pretty big solution.
I have MSBuild's abbreviated output here if it helps:
Run MSBuild for Project
Initial Property Values
AdditionalVCOverrides =
CommandLineArguments = /p:SkipInvalidConfigurations=true
Configuration = Release
GenerateVSPropsFile = True
LogFile =
LogFileDropLocation =
MaxProcesses = 1
OutDir = All Projects-CI\Binaries\Release
Platform = Any CPU
Project = All Projects-CI\Sources\Shared\All Projects.sln
ResponseFile =
RunCodeAnalysis = AsConfigured
Targets =
TargetsNotLogged = String[] Array
ToolPath =
ToolPlatform = Auto
Verbosity = Diagnostic
Built $/.../DataAccessLayer.Testing.csproj for default targets.
C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v10.0\TeamTest\Microsoft.TeamTest.targets (14): Object reference not set to an instance of an object.
source
share