What makes WCF powerful is its ability to expose services via multiple addresses, bindings and contracts . In WCF, you're programming at the interface level as opposed to the actual operation. If you think about it, this is extremely subtle, yet enormously powerful.
With ASMX style services you're restricted to an http endpoint hosted by IIS, where as with WCF you can expose a single contract and implement and host it in a variety of ways. For example, if you wrote a calculator asmx service that returned the sum of two numbers, it would forever live on IIS and invoked from there. The same service operation, i.e.
Add(int a, int b) via WCF could not only be altered in its implementation per channel, but could be hosted in many different ways outside of IIS. Also in ASMX if you're looking to implement any of the WS* Standards, you would have to use WSE etc, WCF wonderfully handles all this lower level plumbing for you, which you can implement via configuration or code, think Secure Conversation, Transactions, etc etc. There are lot of resources on WCF, you can look here for a good starting point.
While I did not put this site together, the microsoft site "Champ vs. Contender" provides lots of resources for showing why they feel WCF is the better choice vs. ASMX.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.