The first trick would be to get your silverlight to communicate with your WCF properly. NOT FOUND occurs on MANY scenarios. It could be that your Web Service is not running in IIS, it could be that you are trying to communicate using some sort of object that violates the service contract.
E.g. Your object has a property of type "object" that can be anything. The first step to narrow down this process would be to install Fiddler2 to show you the network traffic between your client and your server.
I was able to figure this out - the objects I was using as data contracts were not marked as such and even though they were "accepted" by the silverlight app and were generated by the service reference they would always through this acception after the WCF service returned.
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.