The new article titled “Building Distributed Applications with NHibernate and Rhino Service Bus” no doubt shows one of the best implementation of a Client / Service architecture, so If you haven’t checked it out, it is a must read. The problem, however, is that in certain scenarios it may not work out of the box and you need additional configuration on your client / server to make it work. Continue reading

Since working on our RIA application that uses JBoss WebServices on the backend, we’ve had tremendous amount of problems when it came down to handling proxies generated by Visual Studio. The fact is Visual Studio proxy generator (as well as the command prompt tools) are so lame! Although they do the job, but they should only suffice basic scenarios where a client connects to a bunch of webservice with no shared contract across them. Continue reading

This is the 3rd part of the series where in previous post we saw how to develop WPF applications using Caliburn Framework. In this post, we’ll see some more advanced usage where our shell instead of being just limited to displaying single view at a time, can have multiple ones in a Tabbed user interface. Continue reading

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. Continue reading

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. Continue reading

After upgrading some solutions to the new Visual Studio 2010 RTM and expecting automatic migration would do the trick, I bumped into a problem. The problem is that Unit Test project will be automatically upgraded to use .NET Framework 4.0 even if you explicitly choose not to do so in the migration wizard! Continue reading

Author's picture

Hadi Eskandari

Developer, amateur photographer, coffee snob, husband and father.

Sydney