May 2007 - Posts
At my current project we use Team Foundation Server together with the possibility to have a daily build through MSBuild. Over the weekend, the build failed. Because our 'build master' called in sick this morning, I took it upon me to fix the build. But compiling the sources was no problem, because that finished without any errors. And there were no failing (unit)tests. Even better: there were no tests which had run at all! There were 'no test results to display'. The only thing I found in the build log (which is pretty big in a 70+ project solution!) that could indicate a problem was a warning from MSBuild:
MSBUILD : warning : Specified cast is not valid
And, just below that line, the following one:
The previous error was converted to a warning because the task was called with ContinueOnError=true.
After some searching and trying, I found out TFS / MSBuild doesn't like it when your vsmdi file contains a list or sublist that doesn't contain any tests to run. Somehow this feels like a bug, because parsing the testlist fails when it has no members. List != null && List.Count > 0 anyone?
Technorati tags:
MSBuild,
.Net
You've probably noticed it yourself. Bloggingabout.Net seems to be a bit unstable since a week or so. But it's not just us: my rss reader indicates http://weblogs.asp.net has had some problems lately too. Is there any relation between these two sites? Do they happen to use the same database server? Or is it all just purely coincidence...
I don't know what the problem exactly is, but I'm sure our administrator is working hard to get bloggingabout.net up and smoothly running as soon as possible again.
A Halo 3 video has been posted at the Microsoft website, which can be found through the Bungie website. The article containing the link starts out with this next sentence:
Maybe you've heard of him, maybe you haven't... but around Microsoft, Mr. Jukes has established a name for himself as a tireless, hardcore and fanatical player of Halo who isn't too shabby in the video production department either.
You can find the complete article here. But most important: take a look at the video which is available here (right click, save target as). I think it displays great gameplay and nice image rendering. I know one thing for sure: that game will be mine as soon as it's available. What a great time we live in ;).
By the way:
Before you check out Mr. Jukes' Halo 3 video debut, please keep in mind that this video was produced using the internal beta version of Halo 3. This means it's a bit older than what the rest of the world will start playing in the next few days. It also means that it has all sorts of debug text all over it - this won't be in the version you get your hands on. And, this was fully sanctioned and approved by Bungie - unlike some of those other "leaked" videos that have ended up online.
Technorati tags:
Xbox 360,
Games
Thursday the 10th of May LogicaCMG The Netherlands organises an open house for ICT professionals. From 4 pm until 9 pm colleagues will be available to answer any and all questions you might have about (working at) LogicaCMG. People active in all of our competences will be present. The open house is hosted at some of our locations across the country. This time, the lucky locations are: Amstelveen, Arnhem, Eindhoven, Rotterdam and Rijswijk. I myself will be present at our location in Eindhoven. To sign up, just send me your info. Try to add your name, address, phonenumber, e-mail address and if possible your curriculum vitae. You can find more info at http://www.logicacmg.nl/openhuis (Dutch page).
By the way: in Eindhoven the open house is hosted at the 19th floor of our building. With clear weather, it offers a great view of Eindhoven and beyond...
"Unit Test Adapter threw exception: System.Reflection.ReflectionTypeLoadException: Unable to load one or more of the requested types. Retrieve the LoaderExceptions property for more information.."
This error popped up at one of the testers of our project this morning. The unittests he selected worked fine on my machine, but all failed on his with the above message. After searching a bit we found that the only thing which was different between my testrunconfig and his was that he enabled code coverage for the assembly these unittests were pounding away at. As it turns out, this error appears when code coveraging (is that even a word?) a signed assembly without re-signing it.
To re-sing an assembly, open the testrunconfig you are using and go to the 'code-coverage' element in the left pane. Locate the textbox 're-signing key file' and enter the path to the key file which should be used to re-sign the assembly (or browse for it, of course). Hit 'Apply' and then hit 'Close'. You're done now! Happy unittesting....
