How do you make IMemberCreationService available?
I started a new C# console application, added the System.Workflow references and a Sequential Workflow (code) item.
When I tried to open the workflow to add activities and I got this error message "The service 'System.Workflow.ComponentModel.Design.IMemberCreationService' must be installed for this operation to succeed. Ensure that this service is available."
Confused, I added a WorkflowConsoleApplication project in the same solution and I could see the workflow diagram and add activities.
So I checked that I have all the references tha tthe WorkflowConsoleApplication has and I'm added the System.Design, Transaction and Web namespaces.
How do I create my own applications which have a workflow in them without using the default templates?
Actually, you can have the workflow designer without using the C# or VB.NET Workflow project. However, you need to implement a lot of stuff on your own. Essentially, you need to 'rehost' the designer in Visual Studio. Check out the post at https://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=177366&SiteID=1 for a more detailed discussion. Note that I've not tried to fully reimplement everything the Workflow project system does as it does seem to do a lot.
The the Workflow Designer Control technology sample gives you a starting point to rehosting outside of Visual Studio, and can be used as a basis for rehosting inside Visual Studio, but outside of the C#/VB.NET workflow project. To rehost inside Visual Studio, you'll likely need to be pretty familiar with the Visual Studio extensibility SDK.
Notre
What's really interesting is that if, instead of adding a code based workflow, add a "code separation" (xoml) worklfow. I find that with xoml files the designer seems to work just fine even in a generic c# project. But with code based workflow, the designer won't work unless you have a workflow project type.
I wish I could explain it.
That is interesting, Don! I didn't realize you could do that. But I think I could hazard a guess as to why it works.
The code separation workflow files have a .xoml extension. This is registered with an editor factory in the VisualStudio portion of the registry. Since (e.g.) a vanilla C# project doesn't know what to do with .XOML files (and doesn't override files of this extension with some behaviour of its own), the default editor factory is invoked for the .XOML extension.
On the other hand, a code based workflow normally ends with a .cs extension. In a vanilla C# project, this is interpreted as a traditional C# code file. In contrast, within the Workflow project system, the project system recognizes a .cs extension as a workflow file if it contains one of a few 'workflow things', overriding the default .cs extension behavior. You can test this by adding a 'normal' .cs file to a workflow project system & adding a workflow type thing, such as adding a class that dervies from SequentialWorkflow
e.g.
public sealed partial class Workflow1 : SequentialWorkflow
{
}
Suddenly, you will see a different icon in the solution explorer and when you try to design the file, the project system will invoke the workflow designer. I don't know the full scope of 'workflow things', but the workflow project system seems to parse the .cs file looking for certain things that hint the .cs file contains workflow content and then the behavior is changed accordingly.
Notre
My apologises for my late response (I've just been transfer and been without email or internet for 2 days. Torture!).
My first test on creating a workflow in a standard C# project was with a code-seperated workflow and indeed I was able to happily create a workflow. But (and there's always a but isn't there 
) when I instantiated and run the workflow nothing happened. I created another project using the workflow template and executed the same workflow and everything was fine. Then I copied the code out of the template into the first project and still running ran.
So it seems while you the designer has issues displaying the data, there's also a problem executing it...
If the problem does rest with the IDE not recognising workflows can this be fixed with the final release of WinFX (or hopefully a near future Beta) or will workflows be doomed to exist only within thier template space?
I believe Ghenadie indicated in https://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=177366&SiteID=1 that the workflow designer will only work within the workflow project system. Having said this, you can rehost it inside Visual Studio, but you need to wire up everything yourself. Without this rehosting effort, I think it is 'doomed to exist' only within their project system space 
Notre
