Years ago one part of our large app suite was written in WF as it seemed
trendy and suitable for the task (I suppose it was). But now it's like a
lone cuckoos egg in the nest and we want to pull out the working code and
put it in a reusable library, but there is so much specialised WF plumbing
in
WF alive? you'd be surprised how deep that ball of code runs in the .NET
ecosystem. Killing it is like admitting XAML was a bad idea but when has
that ever stopped Microsoft from quietly sliding the dead corpse under the
bed hoping the smell eventually will subside before admitting the "body is
Is WF still alive? From memory I believe the last update was around 2012. I
doubt that it will ever reach .NET Core.
We used WF for a while but it was too complicated for our needs. We
developed our own workflow engine around
https://github.com/dotnet-state-machine/stateless and never looked
Scott,
I don't think WF is available on .net Core yet. So in that case I'd
recommend IIS Express as your host. All the WF stuff I did was years ago
and it was all IIS based. It's grown considerably easier I hear.
Preet
regards,
Preet, in Auckland NZ
On 19 January 2017 at 19:46, Scott Barnes
I have a need to create a local mini web server which sole job is to act as
a WCF host for local area network clients to feed off. The web server's
main role is to act as a Windows Workflow host that will process inbound
data into various whacky workflow(s).
The web server is headless in that i
