Workflow activity properties not usable in a XOML workflow while they are in a code based workflow - by Maurice de Beijer - DevelopMentor

Status : 

  External<br /><br />
		This item may be valid but belongs to an external system out of the direct control of this product team.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 245819 Comments
Status Closed Workarounds
Type Bug Repros 0
Opened 12/15/2006 6:00:47 AM
Access Restriction Public


In a project I have created a custom activity with a public property. I add this activity to a state workflow and add an IfElseActivity below it. Now I want to use the previously added activity property in the declarative rule condition.

In a code based state workflow I can type “this.myCustomActivity1.TestValue == True” into the rule condition editor. The editor indicates the expression is valid and compiling the project succeeds.

However when I do the same in a XOML with code separation state workflow things work differently. I can still add the custom activity and the IfElseActivity. The first time I try to use the custom activity in the rule condition editor the doesn’t show the this.myCustomActivity1. Adding a condition of true and compiling the project makes this.myCustomActivity1 visible in the rule condition editor. Now I can add “this.myCustomActivity1.TestValue == True” and the rule condition editor indicates everything is correct. However when I compile the project produces errors that the field "myCustomActivity1" on type "WorkflowConsoleApplication1.Workflow2" does not exist or is not accessible.
Sign in to post a comment.
Posted by Microsoft on 1/22/2007 at 2:20 PM
Hello MauriceDB,

Thank you for your feedback. Unfortunately, we do not support windows Workflow Foundation through this connect site. We recommend you ask this issue at the forums where they can provide more help. See

Keen Browne
Program Manager
Visual Studio