10-4 Episode 16: Windows Workflow 4 | 10-4

Jeroen Ritmeijer

"Workflow expressions are always in VB syntax"? Say it ain't so.

I know it is all still beta, but I noticed that the new VS interface is not very efficient with regards to the available screen estate. Big gaps between panes, valuable space that could be used to display code Wink

Shame the focus of this video is more on testing workflows rather than building them.

Man, I am being negative today, it must be the weather.

rojacobs
Ron Jacobs

In reply to Jeroen Ritmeijer

#Apr 16th @ 10:05 AM

The idea of Expressions in VB.NET syntax is that ultimately business users might be able to understand and/or change these expressions using a rehosted workflow designer.

The C# expression "Name.Length % 2 == 0" is definitely not business user friendly. Will someone who is pretty good with Excel get "Name.Length Mod 2 = 0" - probably. At least that is the goal.

I like to use tests as part of the process of building the business logic. That way once your business logic is built, the tests are already done and you get very high test coverage of the app.

I agree the UI of DEV10 still needs work - but there is still time.

Don't worry - it's finally sunny here in Seattle today so I can take a little criticisim Smiley

Krisw

In reply to rojacobs

#Apr 16th @ 10:46 AM

Why not allow for any desired conditional syntax? For instance, you could put a drop-down on the condition input control that allows you to select which language syntax you want; "VB", "C#", "F#", "Ruby", "Python", etc.

Locking the user into a specific language syntax seems like a design conceit that is contrary to the .Net language flexibility mantra.

JonnyRocks

Ok so I am not sure who will be reading this but this is an example of a very good presenter. Not all devs are good at presenting. I love that channel 9 interviews devs but for a video showing off a new technology we need someone who is exciting and speaks well. This is the first 10-4 video i watched completely.

Weqster

Well presented, but i agree, lacked content.

mwinkle

In reply to Krisw

#Apr 16th @ 2:54 PM

krisw, it's a point in time thing, it's what we'll most likely have for VS 2010 because of some relatively unexciting details, which I can get into if you want. It's our intent that we will have more options in the future.

terrajobst

Great to see the new WF in action. May be I missed something in the video but why does IntelliSense know at 18:30 the paremeter/field "FirstName"?

MarcinNajder

Great presentation!

Another way of wrapping workflow arguments :
http://mnajder.blogspot.com/2008/11/use-expression-tree-to-avoid-string_08.html

It would be great if we could see the whole process with Sequence, TryCatch, While.... activities on the designer surface (as WF3).
mn

Edsilv

This is a topic I'm very interested in but it's disappointing when you can't actually read any of the text in the video because it's shot at the wrong resolution. I've noticed this with quite a lot of C9 videos. Surely the point of these things is to be able to read the labels of menu items/buttons that are being used?