endpoint.tv Screencast - Creating Your First WCF Client
- Posted: Oct 08, 2008 at 8:00 AM
- 155,358 Views
- 10 Comments
Welcome back to the WCF screencast series! After a short vacation covering WF topics, we return to WCF for the latest video in the weekly WF/WCF Screencast series.
In this short video, CSD MVP Aaron Skonnard from PluralSight guides the viewer through how to create your first WCF client application that consumes an existing WCF service (see the screencasts covering the creation of a WCF service and how to create endpoints for more details). We add the service to the client application using the WCF service's Metadata Exchange (MEX) endpoint - which generates the service definition and contract, which Aaron then writes the code to consume via code...and how to have VS2008 open up your client as the test client at F5 (debug) instead of the standard WCF test client when the service is launched.
As he shows you how to write the client side code, he touches on how the service endpoint information is stored in the config files and storing the results back from the WCF service in local .NET object classes.
For additional information on WCF, please check out the WCF Dev Center on MSDN and the .NET Endpoint team blog. For more information on classes offered by Aaron and the PluralSight folks, check out their catalog of instructor led courses and new online courses that cover a variety of Microsoft technologies, ranging from .NET v3.5 to WSS to BizTalk server.
In this short video, CSD MVP Aaron Skonnard from PluralSight guides the viewer through how to create your first WCF client application that consumes an existing WCF service (see the screencasts covering the creation of a WCF service and how to create endpoints for more details). We add the service to the client application using the WCF service's Metadata Exchange (MEX) endpoint - which generates the service definition and contract, which Aaron then writes the code to consume via code...and how to have VS2008 open up your client as the test client at F5 (debug) instead of the standard WCF test client when the service is launched.
As he shows you how to write the client side code, he touches on how the service endpoint information is stored in the config files and storing the results back from the WCF service in local .NET object classes.
For additional information on WCF, please check out the WCF Dev Center on MSDN and the .NET Endpoint team blog. For more information on classes offered by Aaron and the PluralSight folks, check out their catalog of instructor led courses and new online courses that cover a variety of Microsoft technologies, ranging from .NET v3.5 to WSS to BizTalk server.
Comments Closed
Comments have been closed since this content was published more than 30 days ago, but if you'd like to continue the conversation,
please create a new thread in our Forums,
or
Contact Us and let us know.
More episodes in this show
-
endpoint.tv Screencast - Using Persistence…
-
endpoint.tv Screencast - Creating Your First WCF…
-
endpoint.tv Screencast - Configuring WCF Service…
Follow the Discussion
Oops, something didn't work.
What does this mean?
Following an item on Channel 9 allows you to watch for new content and comments that you are interested in. You need to be signed in to Channel 9 to use this feature.What does this mean?
Following an item on Channel 9 allows you to watch for new content and comments that you are interested in and view them all on your notifications page.sign up for email notifications?
hi I could not play this video plz help me
Same here...Appears that the screencast never changed from the initial splash screen.
you need to install the latest silverlight (version 3)
i can't believe the client is a console application. will anyone ever get around to creating actual, enterprise usable examples?
these videos are really good; gr8 work by Aaron and Cliff; thanx for these tutorials
This is the stupidest tutorial out there.
OK, I need to create a DYNAMIC end-point in that I don't know which IP address wherein I will communicate to. I've got 50 systems and they all need to peer-to-peer, and on different ports at that.
And I don't care to use console.
You fail miserably in providing insight in real-world usage; e.g. a GUI versus a lame no-longer-used console crap thing.
Great tutorial. It's great for showing the BASICS (ie the FIRST client)... As typical people don't seem to realize you need to understand the basics of WCF before you go to more advanced features...
AWESOME !
Great videos for beginners!! Thanks for bringing the class room at the desk.
Notes:
Run service (without debugger). In Client project, Add Service Reference with the address from the service (e.g. http://localhost:8731/service/mex) and select the interface of interest. This should also add the required WCF references.
In Main, create a new client and pass the constructor the name of the endpoint taken from the client project's app.config file (in the client element) (e.g. WSHttpBinding_IEvalService).
To run both the service and the client, r-click on the solution and set multiple startup projects.
To prevent VS test client from showing up, open service project properties and, in Debug[Start Options], change the /client commandline args (e.g. to the relative directory of your custom client).
Remove this comment
Remove this thread
close