Recently at our .NET user group meeting, we had a presentation on WCF over TCP, which is something that I'm trying to do. The two guys who did the presentation said that no class or method within the WCF service should ever use the static keyword. This concerns me, because that is exactly what I've done. When writing my WCF service I relied heavily upon a blog post by Ira Lukhezo titled, "Windows Communication Foundation Support in Visual Studio 2008". Lukherzo's method relied upon HTTP, and I wanted to use TCP instead, but basically I followed his example. He decorated methods of his NorthwindDataManager class with the static keyword, and so I decorated the methods of my data access layer component with the static keyword.

Have I done the wrong thing?

---

Rod

This issue is your service contract implementation canot use statics. Things you use inside the service implementation can be static

---

Richard Blewett, thinktecture - http://www.dotnetconsult.co.uk/weblog2
Twitter: richardblewett

This issue is your service contract implementation canot use statics. Things you use inside the service implementation can be static

---

Richard Blewett, thinktecture - http://www.dotnetconsult.co.uk/weblog2
Twitter: richardblewett

Thank you, Richard, that gives me a lot of relief!!

---

Rod