Administrator
VB.NET Forum Admin
- Joined
- Jun 3, 2004
- Messages
- 1,462
- Programming Experience
- 10+
In our recent upgrade to VS 2008 we learned that WSE/WS-* is dead in VS 2008. Of course we're not surprised Microsoft would do this to force people to WCF, but after huffing and puffing and the shock of having to learn one of the "cosmic 3" (WPF, WCF, WF) I am happy to say the WCF experience has been awesome!
WCF is amazingly easy to learn, especially for those that know web services. I wish I would have gone down this path with .NET 3.0 instead of ever using WSE 3 and WS-* implementations. So here are a few ways YOU can learn WCF in no time.
It all starts with Michele Leroux Bustamante aka "That Indigo Girl" as "Indigo" was the code name for WCF before it was "named." Michele wrote a great book "Learning WCF" which is one of my "must have" recommendations. She also hosted a series of 15 web casts you can download for your viewing pleasure. Here is the list from Michele's web site.
WCF is definitely the way to go in my opinion, now having been forced to use it. The MSDN docs are easy to read (for the most part) on WCF so don't forget to overlook the information that lies before you.
WCF is amazingly easy to learn, especially for those that know web services. I wish I would have gone down this path with .NET 3.0 instead of ever using WSE 3 and WS-* implementations. So here are a few ways YOU can learn WCF in no time.
It all starts with Michele Leroux Bustamante aka "That Indigo Girl" as "Indigo" was the code name for WCF before it was "named." Michele wrote a great book "Learning WCF" which is one of my "must have" recommendations. She also hosted a series of 15 web casts you can download for your viewing pleasure. Here is the list from Michele's web site.
WCF is definitely the way to go in my opinion, now having been forced to use it. The MSDN docs are easy to read (for the most part) on WCF so don't forget to overlook the information that lies before you.