Microsoft KB Archive/926500

= A custom activity does not reflect changes to the base type of the activity from which it is derived in a Windows Workflow Foundation solution =

Article ID: 926500

Article Last Modified on 11/24/2006

-

APPLIES TO


 * Windows Workflow Foundation

-



SYMPTOMS
Consider the following scenario:
 * You have a Microsoft Windows Workflow Foundation solution.
 * You have two custom activities in the Windows Workflow Foundation solution.
 * You change the base type of the second activity to the first activity, you recompile the solution, and then you change the base type of the first activity to the state base type.

In this scenario, the second activity does not change the base type to the state base type.

Note The second activity does not change the base type to the state base type even if you recompile the solution multiple times.



CAUSE
This problem occurs because the type information for the activity is cached and it is not updated even if the project is rebuilt.



WORKAROUND
To work around this problem, close and then reopen the solution in Microsoft Visual Studio 2005.



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) In Visual Studio 2005, create a Windows Workflow Foundation solution.
 * 2) In a project, create a custom activity that is named Activity1.
 * 3) In a separate project in the same solution, create a custom activity that is named Activity2.
 * 4) Compile the solution.
 * 5) Change the base type of the Activity2 activity to Activity1.
 * 6) Create a state machine workflow in the third project in the same solution.
 * 7) Change the base type of the Activity1 activity to StateActivity.
 * 8) Compile this solution again.
 * 9) Try to add the Activity2 activity to the state machine workflow.

Notice that you cannot add the Activity2 activity to the state machine workflow.

Keywords: kbtshoot kbprb KB926500

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.