10-4 episode 29: Workflow Web Services
- Posted: Jul 29, 2009 at 11:03 AM
- 73,983 Views
- 6 Comments
Download
How do I download the videos?
- To download, right click the file type you would like and pick “Save target as…” or “Save link as…”
Why should I download videos from Channel9?
- It's an easy way to save the videos you like locally.
- You can save the videos in order to watch them offline.
- If all you want is to hear the audio, you can download the MP3!
Which version should I choose?
- If you want to view the video on your PC, Xbox or Media Center, download the High Quality WMV file (this is the highest quality version we have available).
- If you'd like a lower bitrate version, to reduce the download time or cost, then choose the Medium Quality WMV file.
- If you have a Zune, WP7, iPhone, iPad, or iPod device, choose the low or medium MP4 file.
- If you just want to hear the audio of the video, choose the MP3 file.
Right click “Save as…”
- High Quality WMV (PC, Xbox, MCE)
- MP3 (Audio only)
- MP4 (iPod, Zune HD)
- Mid Quality WMV (Lo-band, Mobile)
- WMV (WMV Video)
Windows Workflow Foundation in .NET 4 makes it easy to build and consume web services. In this episode I'll take you through the Introduction to Workflow Services lab from the
Visual Studio 2010 Training Kit. Where you will learn about some cool new features such as content based correlation.
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.
Follow the Discussion
For me Workflow services is a mixed bag, there are few things I’m not willing to trade off :
-Contract First: it’s just awkward, I want be able to declare the service contract and then pick the operation to implement in the receive shape.
-I want to be able to group workflows as service operations instead of independent services, for example in the video you have HRService, what if I want to have a single workflow for process the application , other dedicated to check the application status, other for vacation request, other for raise request, other for complains and so on, all related to HRServices however I can’t host all of them under http://localhost:8080/HRservices and “see” them as operations( ProcessApplication, CheckApplicationStatus, VacationRequest, RaiseRequest, Complains ) I’ll have to host each of them under different addresses and treat them as separate services, in other words I’ll end up having for example:
http://localhost:8080/ProcessApplication
http://localhost:8081/CheckApplicationStatus
http://localhost:8082/VacationRequest
http://localhost:8083/RaiseRequest
http://localhost:8083/Complains
To accomplish the desire functionality (single service many operation) today we have to use parallel/ pick shapes which again doesn’t feel natural.
Just my thoughts, other than that; thanks and keep up the good work
Enrique G.
cool stuff
but the vb only syntax just ruins it for me.. when i have a c# project i want to write c#. imo the workflow syntax should be whatever the project language is..
as for intellisense, can you use the editor that vs uses? it has c# intellisense, so compiler as a service cant be a requisite there
this would seem av even better option in vs10 with its MEF:ed componentization..
anyhow, i see WF as something that could have great potential for prototyping / service orchestration and such, i do however see it as something devs will use, not "excel types" as they will hand things over to a dev anyway as soon as visual studio is mentioned
with VB force feeding however i dont see WF4 hitting the (non VB)dev main stream im sad to say :/
Hey Ron,
great stuff ... BUT ...
where have your doors in the background gone to? Between Part 1 and Part 2 ???
FUNNY :O)
Hi Ron, this is great. But it's not in VS2010 Training Kit. Where can I get it?
It's now available in the Visual Studio 2010 Training Kit - January Release
The Windows Workflow runtime is flexible and extensible. We can customize the runtime by adding services to meet our application's needs. Scheduling services allow us to control the assignment of workflow to threads. Persistence services allow us to save the state of workflows. Tracking services allow us to monitor, record, and measure workflow execution. Windows Workflow exposes diagnostic tracing information with the .NET tracing API. A workflow host can add these services with code, or using an application configuration file.
Remove this comment
Remove this thread
close