Article ID: 926073
Article Last Modified on 2/8/2007
APPLIES TO
- Windows Workflow Foundation
SYMPTOMS
Consider the following scenario:
- You create a Microsoft Windows Workflow Foundation project that contains a code separated workflow.
- You add a Code activity to the project.
- You click the down arrow on the DropDown list for the ExecuteCode option of a Code activity.
In this scenario, Visual Studio generates an empty Visual C# (.cs) code file that is named MyWorkFlow.xoml.cs in the Windows Workflow Foundation project.
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
MORE INFORMATION
Steps to reproduce the problem
- Start Microsoft Visual Studio 2005 with Visual Studio 2005 Extensions for Windows Workflow Foundation installed.
- Click File, click New, and then click Project.
- Under Visual C# , click Workflow, and then click Empty Workflow Project in the right pane.
- In the Name box, type WorkflowProject1, and then click OK.
- In Solution Explorer, right-click WorkflowProject1, click Add, and then click Sequential Workflow.
- Click Sequential Workflow (with code separation), and then click Add.
- Expand the Workflow1.xoml, right click the Workflow1.xoml.cs, and click delete.
- Drag a Code control from the Toolbox to the Sequential Workflow pane.
- In the Sequential Workflow pane, switch to Designer view, right-click codeActivity1, and then click Properties.
- Click the ExecuteCode list and cause it to drop down.
An empty .cs code file that is named MyWorkFlow.xoml.cs is generated in the Windows Workflow Foundation project.
REFERENCES
For more information about Windows Workflow Foundation, visit the following Microsoft Web site:
Keywords: kbinfo kbtshoot kbprb KB926073
