IMemberCreationService missing

I created a newWindows Application project today, added all references to the Workflow assemblies and then added a Sequential Workflow (code) to my project. Every time I open the designer I get:

The service 'System.Workflow.ComponentModel.Design.IMemberCreationService' must be installed for this operation to succeed. Ensure that this service is available.

at System.Workflow.ComponentModel.Design.NamePropertyDescriptor.SetValue(Object component, Object value)
at System.ComponentModel.Design.Serialization.CodeDomSerializerBase.DeserializeAssignStatement(IDesignerSerializationManager manager, CodeAssignStatement statement)
at System.ComponentModel.Design.Serialization.CodeDomSerializerBase.DeserializeStatement(IDesignerSerializationManager manager, CodeStatement statement)
When I do a new console workflow project or new activity library I can edit workflows without a problem.

[931 byte] By [JaredBienz] at [2008-2-19]
# 1
I just tried again with a fresh Windwos Application project. I got a different error and maybe I got this error once before and didn't catch it.

The designer could not be shown for this file because none of the classes within it can be designed.

at System.ComponentModel.Design.Serialization.CodeDomDesignerLoader.EnsureDocument(IDesignerSerializationManager manager)
at System.ComponentModel.Design.Serialization.CodeDomDesignerLoader.PerformLoad(IDesignerSerializationManager manager)
at Microsoft.VisualStudio.Design.Serialization.CodeDom.VSCodeDomDesignerLoader.PerformLoad(IDesignerSerializationManager serializationManager)
at Microsoft.VisualStudio.Design.Serialization.CodeDom.VSCodeDomDesignerLoader.DeferredLoadHandler.Microsoft.VisualStudio.TextManager.Interop.IVsTextBufferDataEvents.OnLoadCompleted(Int32 fReload)

JaredBienz at 2007-9-9 > top of Msdn Tech,Software Development for Windows Vista,Windows Workflow Foundation...
# 2

Jared,

Currently we do not support adding workflow items to non-workflow projects. There is a bug logged for this issue and I will follow it up with the Dev team.

Thanks,

Vihang

vihang at 2007-9-9 > top of Msdn Tech,Software Development for Windows Vista,Windows Workflow Foundation...
# 3
Alright. I went the other way and started with a Workflow Console app and added the references for System.Windows.Forms. All works well for now.
JaredBienz at 2007-9-9 > top of Msdn Tech,Software Development for Windows Vista,Windows Workflow Foundation...
# 4

Of course this is a hack, but it works and is pretty simple to do...

Add all the needed references, and also add the following line in the csproj file.

<ProjectTypeGuids>{14822709-B5A1-4724-98CA-57A101D1B079};{FAE04EC0-301F-11D3-BF4B-00C04F79EFBC}</ProjectTypeGuids>

Put it under the first <PropertyGroup> item right beneath the <AssemblyName> item.

Just another alternative...
David

DavidMaltby at 2007-9-9 > top of Msdn Tech,Software Development for Windows Vista,Windows Workflow Foundation...
# 5
Thanks David.
JaredBienz at 2007-9-9 > top of Msdn Tech,Software Development for Windows Vista,Windows Workflow Foundation...
# 6
This did not work in my own scenerio. In my application I had a class library project containing all my custom activities and another Winforms project that references this library. I have the Workflow viewer control on one of my forms. Something like what visual studio had and each time I tried to change the workflow properties, i get this exception and this still persists even after using ur suggestion. What else can I do?
murpheux at 2007-9-9 > top of Msdn Tech,Software Development for Windows Vista,Windows Workflow Foundation...

Software Development for Windows Vista

Site Classified