Main Menu

Daily using/supporting

Get Firefox browser!
Get Thunderbird!
Get Opera browser!
Get The Gimp!
Get Inkscape!
Get LibreOffice!
Get Videolan!
Get Linux!
Get Mandriva!
Get Joomla!
Hacker Emblem

Popular Tags

Archives

Which topics would you like us to cover more?

Latest comments

Latest tweets

about 1 day ago Using REDIPS.drag to add drag and drop to your .Net webapplication #li #dib0 http://t.co/n8zY3s7d
about 7 days ago http://t.co/cknQcDbo #Kindle
about 15 days ago Freedom isn't the ability to choose what to do or say, but the ability to choose what not to do or say #freedom
about 29 days ago http://t.co/61KTQknI #Kindle
12 Apr 2012 Force the use of a networking adapter using C# #li #dib0 http://t.co/ZTJOPzOz
9 Apr 2012 http://t.co/k9yliR2t #Kindle
9 Apr 2012 Mandriva 2010.2 and USB devices in Virtualbox http://t.co/fwq9gbHB
9 Apr 2012 Execute a http request to you own site with PHP http://t.co/DIvWPrpd
Twitter
Prev Next
Home Architecture, security and coding VS2008 project using private unittests don't build with TFS2010
VS2008 project using private unittests don't build with TFS2010
Written by Division by Zero   
Tuesday, 29 June 2010 13:50

Today we ran into problems while testing our daily builds on TFS 2010. Apparently there is a known issue building Visual Studio 2008 projects that contain unittests using private accessors. That's a setback for us, because we use those a lot. The error we got is:

TF270015: MSTest.exe returned an unexpected exit code. Expected '0', actual '1'

We'll probably have to wait for the first service pack, or wait until we are able to convert to Visual Studio 2010 and hope that solves this problem.

Update 01-07-2010: After a lot of testing it became clear that the private accessors aren't the problem. It seems there is a bug in the way TFS 2010 handles the output of MSBUILD.EXE version 2008. If we create new build definitions, the MSBUILD version 2010 will build exactly right. With the old build definitions it will only build correctly if all unittests run successfully, resulting in a return code 0 and integrating the results. If one of the unittests fail the 2008 version of MSBUILD will result in return code 1 and fail the build. I was told that Microsoft is working on a patch to fix this. Here is an answer on the MSDN forums that states the same.

Update 27-09-2010: There finally is a hotfix for this problem.

Tags:

Related Articles
 

Add comment


Security code
Refresh

Beware of bugs in the above code; I have only proved it correct, not tried it. - Donald E. Knuth


© 2009 - 2012, Division by Zero

Template based on the empire template by joomlashack 

Valid XHTML 1.0 Strict  Valid CSS!  Creative Commons License
This work by Division by Zero is licensed under a Creative Commons Attribution-Noncommercial-Share Alike 3.0 Netherlands License.