WCF是提高标准还是只是提高复杂性级别? [关闭]

I understand the value of the three-part service/host/client model offered by WCF. But is it just me or does it seem like WCF took something pretty direct and straightforward (the ASMX model) and made a mess out of it?

Is there an alternative to using SvcUtil's command line step back in time to generate the proxy? With ASMX services a test harness was automatically provided; is there a good alternative today with WCF?

I appreciate that the WS* stuff is more tightly integrated with WCF and hope to find some payoff for WCF there, but geeze, otherwise I'm perplexed.

Also, the state of books available for WCF is abysmal at best. Juval Lowy, a superb author, has written a good O'Reilly reference book "Programming WCF Services" but it doesn't do that much (for me anyway) for learning now to use WCF. That book's precursor (and a little better organized, but not much, as a tutorial) is Michele Leroux Bustamante's Learning WCF. It has good spots but is outdated in place and its corresponding Web site is gone.

Do you have good WCF learning references besides just continuing to Google the bejebus out of things?

If you're looking for good test client for WCF services. Look no further than msdn.microsoft.com/en-us/library/bb552364.aspx

Great resources. I wouldn't go as far as to say rp was bashing WCF or the authors. I too have felt a little overwhelmed while attempting to look at WCF after having spent so much time in ASMX. I know it's better and I want to experience it, but it's hard to find an entry point quite like you could with ASMX.

Thanks for the links. Just curious, do you know what happened to Buddhike? He seems to have disappeared off the face of the earth. The new blog he mentions at blogs.thinktecture.com/buddhike doesn't exist (anymore). It's like he's shuffled off this mortal coil. (What dreams may come?) Thanks.

blogs.conchango.com/pauloreichert/archive/2007/02/22/… not found

WCF aims to be a single framework for all those protocols. It does SOAP, REST, and with the WSCF Adapter SDK, it does those "legacy system" connections too, all within the WCF model.

It depends on how you measure "productivity". I would rather a developer take 2 - 3 days to get their head around this now, for the benefits say in 6 months time. WCF replaces more than just webservices.

I agree 100%. If you just want Web Services and you need to ship quickly (who doesn't?), its ASMX all the way baby! WCF is a giant sledgehammer - total overkill if all you want is basic Web Services. Just because its the shiny new thing does not mean you should assume its all round better, for all scenarios, all the time. And just because WCF is hard to understand, doesn't make you a smart person for choosing it. More power to those with the guts to decline to jump onto the WCF bandwagon!

AspNetCompatibilityRequirements is a necessary evil if many developers are going to make the switch from their ASMX services which are currently working just fine.

dan why not AspNetCompatibilityRequirements ?

DaveWard AspNetCompatibilityRequirements is a necessary evil ?

Now, use WCF or REST? or WebAPI ? or MicroService ?

I had no trouble with cross-platform ASMX services--XML does quite nicely there. I understand that WCF = remoting + ASMX + MSMQ + WSE. My beef is that MS should use a little "progressive enhancement" to make WCF more easily approachable and my question is how! Thanks, rp

ASMX interoperability was very good, though the effort got higher when WS-Security was involved.

yes...and as a fundamental communications framework, it should replace ASMX and ASP.NET-oriented web services. No?

I think people are a little off the mark when they say that WCF is a replacement for remoting. Remoting is still a fine option for when you want to do real .Net to .Net object-based calls, and have plenty of control over how things are set up on both ends. WCF on the other hand is geared towards publishing Services for anyone to consume, any way they want to.

Tim, Microsoft now says use WCF for everything and that it is a replacment for Remoting. Remoting seems to be the forgoten child of the .net world.