Blog

This is my first post using Windows Live Writer Beta 2. I must say, it looks nicer than the first beta (having a Windows Vista-proof UI), but that’s not all… Some of the features that were added are pretty darn cool (auto-ping on post, table editing) or just plain good (use the same window for multiple posts, finally!). I am missing the spelling checker though… My first feeling: this is a pretty big step ahead for Windows Live Writer.

I took the test Adel blogged about. And guess what? I’m binary! Does this mean I’m 1337? 😉 Which Programming Language are You?

I ran into a nice little riddle on thinkgeek.com{.} today (in the shirts section). If you enjoy silly humor: take a look over there. How many people can read hex if only you and dead people can read hex? For the answer, select the box below… 57006. (dead is 57005 in hex. Add 1 for you and there you are: 57006)

Yesterday, I posted about a problem with MSBuild building our solution. We solved it, so I wanted to let you in on the secretsolution. We use the Enterprise Library V1.2 in some of our projects. And because some of the projects are being re-used from other internal projects, not all the references in thos projects were checked for versions. As it turned out, another project had a reference to an enterprise library assembly with a runtime version of .

As I mentioned before, bloggingabout.net got a bit unstable recently. Our administrator saw this, and migrated us to a new host. All DNS servers should be updated by now, so the new host is fully operational. This should make us fully stable again. Together with this move, he also updated our community to Community Server 2007. And because we were into making changes, I updated the look of my blog (again… 😉 ).

Our current project uses the possibilities of MSBuild to have a daily build on a TFS server. This has been working up until yesterday somewhere around noon. Nobody knows what exactly happened, but it stopped working after our successful build of 11:42 am. _Our problem: _ Compilation of one project (of a total of 71 projects) is failing. The project builds successful on the local machines of all the developers. It references EnterpriseLibrary.

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!

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 https://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.

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.

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.

“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.

It took me a while, but in the end everything worked out and life’s good… Most important changes are I have my very own server now, containing all the general stuff like mail, music, development stuff and that kind of data. My workstation received a small update (I was able to upgrade based on the ‘old’ machine of a friend) and is now running Vista quite smoothly. To be honest, I haven’t found any major issues yet.