Tonight I was facing an issue with TeamCity 5.0 plugin in Visual Studio 2008.

I was getting the error message ‘​Failed to collect changes error’ in the new Local changes window.

JetBrains just published TeamCity 5.

The wait is over, ladies and gentlemen! The release build is baked, tested, and put on the shelf. Tastes good, so go and grab it now!

Since some time I have the current scenario where I need to have conditional reference in a project. Basically the application must reference an assembly in one case in other it should reference another one. This was working correctly from an MSBuild point of view as the first implemented solution let me compile and run the application on my development machine and it was also working for our TeamCity build server. So everything was fine in this perfect word expect one thing!

The issue was the following; Visual Studio was showing two references of the ‘same assembly’ with different path. Not really an issue you would say because the correct one was used at compile time and at run time in all configurations. So the issue was that this had an impact of ReSharper. And this is I cannot accept because it affect my productivity.

Laurent Bugnion just published MVVM Light Toolkit V3 Alpha 3 which support WPF 4 and Silverlight 4!

I published, yesterday a short post in French on my Tech Head Brothers portal about Silverlight 4 Beta, Drop Target et MVVM which shows the usage of this new version of EventToCommand combined with Silverlight 4 Drop Target.