The Problem Solver - All Comments

[译]Windows Workflow Foundation 4 和持久性

生鱼片 — Fri, 20 Nov 2009 12:05:30 GMT

原文地址：msmvps.com/.../windows-workflow-foundation-4-and-p...

re: Workflow 4 and Visual Basic expressions

Maurice — Wed, 11 Nov 2009 16:09:38 GMT

@Ladislav,

I know the feeling. However that said there is some benefit to this. Having the workflow runtime to let users add to your app by rehosting the designer is not a bad idea by itself. The question is how practical this is in the real world. It remains to be seen.

And there is nothing wrong with marketing. No really, it means we can get payed to do all the cool stuff we enjoy :-)

re: Workflow 4 and Visual Basic expressions

Ladislav — Wed, 11 Nov 2009 15:37:04 GMT

Omg, this is probably the worst explanation I can ever imagine. Why MS deals with business users in technology for developers? Have you ever seen any business user who at least understands exception handling, compensation, transactions, persistence, services or event driven execution? How can people without solid knowledge of these key concepts modify WF? How many WF projects target on business users? I guess no more than 20%. But I understand it sounds great on marketing presentations.

re: Workflow 4 and Visual Basic expressions

mwinkle — Sat, 31 Oct 2009 04:45:32 GMT

@Ernesto,

the workflow runtime is agnostic when it comes to expression languages, there are all the extensibility points to add in a parser, even an extension point to add a custom dialog/ visual editor for the expressions. It is possible to enable the scenario that you mention, where we could have a provider, it is just not something that we enable out of the box, nor do we have a designer that we ship for other languages besides vb (specifically referring to the expression text box).

We're working on a sample that shows how you could implement a different expression text box if you want to support a different language (and also require a parser, etc).

Flowcharts in Workflow 4 and the Switch activity - Maurice

DotNetShoutout — Thu, 29 Oct 2009 22:32:25 GMT

Thank you for submitting this cool story - Trackback from DotNetShoutout

re: Workflow 4 and Visual Basic expressions

Maurice — Thu, 29 Oct 2009 21:41:41 GMT

@Ernesto,

I agree, the workflow should just store a parsed version of the expression and you should be able to edit it in whatever dialect works best for you. Unfortunately that isn't the case for now. Lets hope they enable that some time in the future.

re: Workflow 4 and Visual Basic expressions

Ernesto — Thu, 29 Oct 2009 20:22:45 GMT

It would be better to have an expression interpreter provider that to do the job. So everyone can write the expressions in the language that thay prefer, just changing/adding the provider in config file, just like memberships provider or something else.

re: Workflow 4 and Visual Basic expressions

Robert — Wed, 28 Oct 2009 00:57:46 GMT

Forcing everyone to use VB because it is more convenient for business people is the stupidest excuse I have ever heard. What about all the applications that have nothing to do with business? Being forced to write code in the .net language for amateurs sucks big time. If you set aside this really irritating issue the workflow team is doing a great job IMHO.

Flowcharts in Workflow 4 and the Switch activity

DotNetBurner - Windows Workflow — Wed, 28 Oct 2009 00:17:48 GMT

DotNetBurner - burning hot .net content

Workflow 4 and Visual Basic expressions

DotNetBurner - C# — Mon, 26 Oct 2009 21:50:43 GMT

DotNetBurner - burning hot .net content

re: Workflow 4 and Visual Basic expressions

Maurice — Mon, 26 Oct 2009 18:44:27 GMT

@cibrax,

That on not the explanation I was given. And it would be a new experience where CSD reused something from another team. Normally they rebuild/reinvent everything as they believe they can do a far better job.

re: Workflow 4 and Visual Basic expressions

cibrax — Mon, 26 Oct 2009 18:02:05 GMT

I saw somewhere that WF team used VB for expressions because the VB team gave them an in-memory parser in time for .NET 4.0 RTM. That's the main reason I think :).

Nederlandse CodeCamp 2009

DotNetBurner - ASP.net — Tue, 20 Oct 2009 21:57:25 GMT

DotNetBurner - burning hot .net content

re: Sending your own objects to a WF4 workflow

Maurice — Sat, 10 Oct 2009 15:05:33 GMT

@Simon

I am duplicating the Person on both sides. One thing to make sure of is that the SOAP namespaces match up so I explicitly specify them on both ends. This example was done without using the Add Service Reference as I only needed the Person class but doing so is certainly a valid option.

With Beta 1 the designer is somewhat unstable so I am developing mos workflows using code. When we get beta 2 I expect to be doing more with the designer and XAML.

re: Using Windows Workflow Foundation 4 Receive from an non WF client

Maurice — Sat, 10 Oct 2009 14:57:25 GMT

Tmessages are returned un such a way that that the IsWrapped = false is required, by default they are expected to be wrapped. You cannot do this on a DataContract but you can on a MessageContract hence the requirement for a MessageContract. When WF is used on both sides the message is no different, it just takes care of things for you.

re: Using Windows Workflow Foundation 4 Receive from an non WF client

SSG31415926 — Sat, 10 Oct 2009 06:05:13 GMT

Can you explain why it is necessary to use MessageContracts when not using another workflow? Or can you point me towards something that explains it, please?

re: Sending your own objects to a WF4 workflow

Simon — Sat, 03 Oct 2009 07:51:15 GMT

Did you achieve this without using Add Service Reference? I tried to do the same in xaml but couldn't get it to work. If I use Add Service Reference, and use the generated custom type, it works but if I use my own, annotated with the MessageContractAttribute, it doesn't. Any chance you could revisit this using XAML?

re: Sending your own objects to a WF4 workflow

Simon — Fri, 02 Oct 2009 06:44:46 GMT

Can you explain why it's necessary to use a MessageContract from the client? Is this just normal for WCF?

re: Combining WCF and WF4

Kannan — Fri, 18 Sep 2009 12:56:33 GMT

Please explain about how we can handle transaction?

Sending your own objects to a WF4 workflow

DotNetBurner - WCF — Sat, 12 Sep 2009 22:31:19 GMT

DotNetBurner - burning hot .net content