I wrote a WCF service back in 2009, which uses net.tcp. I used VS 2008, .NET 3.5. Now I’m working on a new WPF app using VS 2010 and .NET 4.0, that will consume my WCF service. In working on this, I’ve discovered that I’m going to have to make several changes to the WCF service. Since I’ve got to do that I thought I might as well upgrade it to .NET 4.0, the only concern is, do I need to be aware of any changes that I need to take into account? (At this point the only app that will be using the WCF service is this new WPF client app, so I won’t be impacting anything else.)
Share
I concur with everyone else, however in my experience
netTcpBindingis more trouble than it’s worth. Too many configuration headaches, and even after I dealt with all of those it turns out some of my clients were using proxy servers that had to have exceptions added to their network. This was the real killer.I ended up redoing my service using
wsHttpBindingon port 80 instead, and instead of worrying about callbacks I just had my clients ping the server in intervals looking for data.