CODEWITHSUNDEEP
.netwcfremotingwindows-server-2000
devgeezer
devgeezer

Reputation: 4189

Can WCF run on Win2k?

What is needed to either support WCF on Win2k, or at least minimize the effort in supporting remote communication with Win2k servers via .Net?

Background:

A product I'm working on has a legacy .NET remoting implementation that has been largely replaced by the WCF for new development. The legacy implementation is used as a fall-back for communication with servers running older versions prior to our WCF implementation.

Sales has asked for Win2k support which leaves dev in somewhat of a pickle as .NET 3.0 (and therefore presumably WCF) is not supported on Win2k. We want to support Win2k with a minimum of extra development effort, but it seems that to support Win2k we must implement the interfaces twice; once for remoting with legacy servers and once for WCF.

Upvotes: 4

Views: 566

Answers (3)

Erik Funkenbusch
Erik Funkenbusch

Reputation: 93484

As others have said, you're not going to be able to run WCF on Windows 2000. However, you don't necessarily have to.

Frankly, it's not unreasonable to require your end users to install a Win2003 Server to deal only with your WCF Services. Your customers can leave their Windows 2000 infrastructure in place and simply run a Win2K3 server (or even Virtual Machine) that just runs the service. A Windows 2003 Web license is about $300 and it wouldn't require a huge machine to run, so it's relatively cost effective.

Upvotes: 0

Joel Coehoorn
Joel Coehoorn

Reputation: 416149

Windows 2000 will only run .Net 2.0 and earlier. WCF requires 3.0 or later. A lot of 3.x apps can be recompiled to target the 2.0 runtime, but if you're using any of the extensions (WCF, WF, WPF) you always need the full 3.x framework installed.

So no.

Additionally, extended support for Windows 2000, including security updates, ends in a little over 13 months. If someone wants to keep using Windows 2000 past that date, that's their own business. But the implications to you are from that date on you can't ever know for sure whether there's really a problem that you can actually resolve or if your customer's server was just infected with malware. Offering support in that scenario is difficult at best.

Upvotes: 7

Marc Gravell
Marc Gravell

Reputation: 1064244

The closest you'll get on W2K is WSE3 - this gives you MTOM (etc) over SOAP - but not the full WCF goodness.

You could design the service to be WCF at the server, but WSEx at the client? Not "free", but I'm assured by several WCF experts that it is very "doable" - WCF was designed to support standards, after all. You'll have to limit yourself to http-basic, but IMO that should be the default anyway.

Jimmy has an article on this here: Interoperability between WCF and WSE 3.0 (scroll down to "WSE 3.0 to WCF").

Upvotes: 6

Related Questions