While I was upgrading Castle Windsor to support .NET 4.0 build scripts, I came across an interesting depricated API. If you have set Warnings are Errors in your project settings, you'll definetly get bitten by this once you upgrade your project from .NET 3.5 to .NET 4.0, if you're using SecurityManager that is.

When creating Line of Business (LoB) applications with Silverlight, the only choice to get the data to the application is through webservices. People having their Silverlight application hosted on the same webserver as the service have almost no problem, but things get interesting when service is not hosted on the same machine as the application, and it gets hairy when you self-host a WCF service. Let's see how it is done in each scenario.

In the process of upgrading my IIS 6 to IIS 7, my website was down for almost a whole day. The problem, at first, was that only front page of the site worked all other pages returned a status 404 due to the fact that all routing was stopped working. The problem which was fixed by my hosting provider, but after that, the whole web site stopped working.

I've spent the last couple of hours trying to get a web application working. The problem was that the web application uses a custom Principal object, implementing IPrincipal interface, but upon launching the application in Visual Studio, a strange exception was thrown.

Back in May 2008, I found a way to use Linq expression to fire notification change, and just after that on September 2008, changing the first implementation to benefit extension methods, things looked a lot easier and more C# 3.0 style. But now to think of it, the best implementation of INotifyPropertyChange would be not to implement it at all! Is this possible?