RequestPersist does not exist in Beta2?

RequestPersist does not exist in Beta2?

• Bhanu_Prakash

  What I wnat to obtain is only persistance, not unloading from memory
  
  Is there any chance to obtain this behaviour
  
  

• Ekta

  The workflow must be idled in order to persist the Workflow programatically, and when idle it is appropriate to be unloaded. However, two exceptions are TransactionScope activities, and applying the PersistOnClose attribute to activities. Using these items will cause a workflow to persist and immediately continue to execute. See this post for additional information and an expanded discussion of this topic. Look for the Posts by Paul Andrew for additional information.

  If you persist a workflow in the middle of executing an activity, then there is no way to resume in the middle of that activity if the workflow were to be rehydrated (obvious exception, a workflow is merely nested activities inside container activities and we are breaking in the middle of these activities)

  Thanks,

  Steve Danielson [Microsoft]
  This posting is provided "AS IS" with no warranties, and confers no rights.
  Use of included script samples are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm
  

  
  

• Gregory Dye

  Hi,

  Use TryUnload in place of RequestPersist.

  Thanks,

  Steve Danielson [Microsoft]
  This posting is provided "AS IS" with no warranties, and confers no rights.
  Use of included script samples are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm
  

  
  
• RequestPersist does not exist in Beta2?