Yes, but it's quite confusing.
The introduction says the article will show a way how to host workflows in IIS that are not workflow services. So it starts with creating a simple workflow (section "Create a simple workflow") in a Console Application project. By following these steps
you will get a workflow based on the Activity-Class (which has an <Activity> element as root node in the XAML).
If you follow the further steps it comes to the point where you test the endpoint by opening its URL in Internet Explorer. This fails with a 404. If you try the following steps and create a client that will call the endpoint, it also fails with an Exception,
containing a 404. The sample seems not working so far.
If you now scroll a bit deeper, there is a section "Example", containing the complete code for this sample. If you look at the code for Workflow1.xamlx, you will recognize that this workflow is based on a <WorkflowService> root activity in
contrast to the sample workflow we created in the beginning (which is based on <Activity>). If you now try to run the sample with this new "Worklflow1.xamlx" code, it works. Nice, but this is a workflow based on WorkflowService, which is no
non-service workflow for me.
The article suggests that it's possible to host normal <Activity> based workflows in IIS. I have tried several simple workflows, but only <WorkflowService> based workflows work with this sample. Every "normal" workflow leads to a 404
I'm looking for a solution to host simple workflows in IIS and appfabric just like they are created when you drag a few activities onto the workflow designer surface and save the XAML to a file. I don't want the user to have to add a <WorkflowService>
node or something like that.