Tonight we got the following issue on our TeamCity build server which produce different ClickOnce setups :

c:\WINDOWS\Microsoft.NET\Framework\v3.5\Microsoft.Common.targets(3652, 9): error MSB3482: An error occurred while signing: Failed to sign ....\Tests\Output\bin\DeployClickOnce\app.publish\setup.exe. 

Find here a list of all my 38 posts for 2009! In the bold, the posts which got most traffic.

January

In some rare case I have to use Eclipse configured to access our Innoveo Solutions svn server. I also for sure have Visual Studio 2008 with VisualSvn installed which install TortoiseSvn.

Today I faced the following crazy issue, from a file browse window opened through Eclipse, I saw that one file was modified so I did from that file browse window a svn revert using TortoiseSvn which ended to a crazy situation in Eclipse. It was totally messed up.

Tonight I found a little tip that you might already know but for me it was the first time I realize that.

When you want to open the properties of a project in Visual Studio 2008, in the past I was doing a right click on the project then I was searching for couple of seconds the entry properties

The other day I had to re-install my whole server which is hosting Tech Head Brothers. I had also to redo the configuration to have IIS deliver compressed content. I was quite sure to have a post on this but the only thing I could find was “Optimization of a Web Site - Using Content Expiration (IIS 6.0)”

So I started from scratch and after some issues I finally managed to have it running. I started uisng the following post from Scott Forsyth, “IIS Compression in IIS6.0” and I took over those steps from his post:

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.

I am using and enjoying for some time now VisualSVN plugin in Visual Studio 2008. I just discovered a nice feature that is not part of the normal menu but that you can easily add to; the pending changes window:

[](http://weblogs.asp.net/blogs/lkempe/4146938714_6faf5320fe_o1_34010721.png)