Microsoft KB Archive/926073

= Visual Studio generates an empty .cs code file for a code separated workflow in a Windows Workflow Foundation =

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 &quot;Applies to&quot; section.



Steps to reproduce the problem

 * 1) Start Microsoft Visual Studio 2005 with Visual Studio 2005 Extensions for Windows Workflow Foundation installed.
 * 2) Click File, click New, and then click Project.
 * 3) Under Visual C#, click Workflow, and then click Empty Workflow Project in the right pane.
 * 4) In the Name box, type WorkflowProject1, and then click OK.
 * 5) In Solution Explorer, right-click WorkflowProject1, click Add, and then click Sequential Workflow.
 * 6) Click Sequential Workflow (with code separation), and then click Add.
 * 7) Expand the Workflow1.xoml, right click the Workflow1.xoml.cs, and click delete.
 * 8) Drag a Code control from the Toolbox to the Sequential Workflow pane.
 * 9) In the Sequential Workflow pane, switch to Designer view, right-click codeActivity1, and then click Properties.
 * 10) 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.

