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 don't ever plan on providing a HTML UI to it, as its really just in place to run long running procs, react to new inbound data and then answer any local clients requests back with data (in fact i'd ideally like to keep it locally "swagger"`fied). Where are we at with this kind of pattern, any new toys to play with that makes this easier or should i keep it circa 2009 and below - .NET wise. I'm at the moment leaning towards .NET Core mix but still not sure how to make Windows Workflow fit into that still (i have to use WWF). --- Regards, Scott Barnes http://www.riagenic.com
