It'd be great if we could call Workflow Services directly from an AJAX application through REST/JSON endpoints. The current inability to define a contract first when defining a Workflow Services prevents us annotating the contract with the [WebGet] attribute which would be the obvious way to enable both a SOAP and REST endpoint on the same service.

Port Windows Workflow Foundation to .NET Core.

Currently, the source code for the workflow assemblies has been open sourced under the MIT license at https://github.com/microsoft/referencesource, but the XAML files and resource files are not included in that distribution. It would be great if you could release the entire package as part of the referencesource repository so that others can fork and improve the workflow framework.

Update the old CodePlex Microsoft.Activities.UnitTesting and build it into the framework with associated VS tooling.

Sadly it looks like WF is now abandoned.

Add the Workflow activities that are under Microsoft.Activities and its child namespaces (Microsoft.Activities.Expressions, Microsoft.Activities.Hosting, Microsoft.Activities.Messaging, Microsoft.Activities.Client, Microsoft.Activities.Client.Security) into the collection of activities that are available under the WF designer toolbox in VS2015 and allow them to work without the need to use Workflow Manager

An online diagnostic and repair tool able to fix problems with an installation when a local component becomes corrupted or deleted.

This isn't a detailed idea with any kind of architecture, it's just an idea that could prove useful given how complex the system has grown [and the fact that I've spent all day dealing with this exact issue].

Flow chart diagram with a lot of paths becomes unreadable when crossing paths are not disatinguished from merging paths. Usualy, in other diagram editors, when one path is crossing the other path, it runs over like a little bridge. And then, If there are no bridge, you are sure that the paths are merged.

Why not to allows inserting ending point of flowchart diagram (or subdiagram). Without public (not supposed) end point, where every paths converging to, the diagram is not properly readable - some of paths are virtual - you don't see them at the diagram, so can miss them. It is bug friendly, am i right?

Why not to allow manual moving path's labels. Automated positioning on the middle of the path is one of the most important issue, that often makes the diagram hard to read or sometimes completely unreadable (mainly at decision or switch components).

Why not customize side of true/false paths of decision component? It is one of base requirements that allows creating readable diagrams.

Why not to allow resizing of diagram items? It is one of the base requirements that allow to create readable, usable diagrams. The main problem is, when the entered name does not fit in, and you could not read it without opening properties window. It realy makes reading of diagram dificult.