Nice work.
Keep up the good stuffs.
I think "what was the problem in old approach" should be more elaborate to help beginners get why WCF? Before WCF, we had development and deployment tightly coupled. Now in WCF u develop and almost doesn't take care of deployment. But in non-WCF world if u developed the code for remoting and later wants to use MSMQ or web service u need to do substantial changes in code. So WCF is great! Thanks for sharing.
Thank you very much for your comment, I will try to explain it a more about the problems of old methods and the benefits of WCF.
wow.. I have done the same work with windows service. I am surprised that it also work with ASP.NET. It will help me lot. Thanks for share this.
By the way, I like your blog motto. It is really different.
Why wouldn't it be working with ASP.NET as well? Both of them run as Services. Helpful post for getting started with ASP.NET though.
One issue - If you open the application in multiple browser or multiple times, it may happen that there will be several instance of the asp.net worker process, that is multiple aspnet_wp.exe/w3wp.exe in the process list.
This is absolutely wrong.