WCF Security and NetTcpBinding?

NetTcpBinding is normally used for Intranet where you are likely to have point to point comms so transport security is probably adequate. If you are operating over the web then you will want to enable Message level security to secure the end to end traffic (transport security will only secure the content for 1 hop). The default security for netTcpBinding is transport security so you need to change this.

In both cases message privacy (encryption), integrity(against tampering) and partial authentication is achieved. NetTcpBinding I believe defaults to Windows authentication - so you will need an account in a domain or actually on the Service machine (if operating in a Workgroup) matching the Windows credentials of the client. Note that you can programmatically change request the credentials from the client and set them programmatically before opening the client proxy if need be.

Also enable reliable messaging.

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.