Skip to main content
SharePoint

Return to Question

added 111 characters in body
Source Link
lthibodeaux
lthibodeaux
  • 53
  • 11

I've been suffering through an issue I haven't managed to find much documentation on over the past several weeks as I've begun working on my first custom workflow project. I have a workflow solution deployed to the farm with a single feature which is activated on a single SharePoint site instance. Whenever I want to make a change to the workflow, I deactivate and uninstall the feature, then retract the solution and redeploy, but the following always occurs, no matter if I retract and deploy the solution using Visual Studio 2010, stsadm, or the SharePoint Management Shell:

  • Any time my workflows are activated by the System Account when an item is created or changed, the previous codebase is used to run the workflow. That means the changes I've made have taken no effect.
  • Any time the workflows are activated manually using the Workflows form under "Start a New Workflow," the updated codebase is used to run the workflow. The changes I've made appear to work just fine.

How do I completely root out the previous version of the solution? I've already read through this article detailing the same scenario, but this solution is deployed to the farm and the guidelines there were unfortunately no help, even if I changed the parameters to stsadm so that it did not target a web application. I've also enabled "Restart Web Server" on the package and set "Always Force Install" to "True" on the feature when using Visual Studio 2010's deployment.

I've been suffering through an issue I haven't managed to find much documentation on over the past several weeks as I've begun working on my first custom workflow project. I have a workflow solution deployed to the farm with a single feature which is activated on a single SharePoint site instance. Whenever I want to make a change to the workflow, I deactivate and uninstall the feature, then retract the solution and redeploy, but the following always occurs, no matter if I retract and deploy the solution using Visual Studio 2010, stsadm, or the SharePoint Management Shell:

  • Any time my workflows are activated by the System Account when an item is created or changed, the previous codebase is used to run the workflow. That means the changes I've made have taken no effect.
  • Any time the workflows are activated manually using the Workflows form under "Start a New Workflow," the updated codebase is used to run the workflow. The changes I've made appear to work just fine.

How do I completely root out the previous version of the solution? I've already read through this article detailing the same scenario, but this solution is deployed to the farm and the guidelines there were unfortunately no help, even if I changed the parameters to stsadm so that it did not target a web application.

I've been suffering through an issue I haven't managed to find much documentation on over the past several weeks as I've begun working on my first custom workflow project. I have a workflow solution deployed to the farm with a single feature which is activated on a single SharePoint site instance. Whenever I want to make a change to the workflow, I deactivate and uninstall the feature, then retract the solution and redeploy, but the following always occurs, no matter if I retract and deploy the solution using Visual Studio 2010, stsadm, or the SharePoint Management Shell:

  • Any time my workflows are activated by the System Account when an item is created or changed, the previous codebase is used to run the workflow. That means the changes I've made have taken no effect.
  • Any time the workflows are activated manually using the Workflows form under "Start a New Workflow," the updated codebase is used to run the workflow. The changes I've made appear to work just fine.

How do I completely root out the previous version of the solution? I've already read through this article detailing the same scenario, but this solution is deployed to the farm and the guidelines there were unfortunately no help, even if I changed the parameters to stsadm so that it did not target a web application. I've also enabled "Restart Web Server" on the package and set "Always Force Install" to "True" on the feature when using Visual Studio 2010's deployment.

Source Link
lthibodeaux
lthibodeaux
  • 53
  • 11

VS2010 Workflow Update Deployments Failing to Update System Account Codebase

I've been suffering through an issue I haven't managed to find much documentation on over the past several weeks as I've begun working on my first custom workflow project. I have a workflow solution deployed to the farm with a single feature which is activated on a single SharePoint site instance. Whenever I want to make a change to the workflow, I deactivate and uninstall the feature, then retract the solution and redeploy, but the following always occurs, no matter if I retract and deploy the solution using Visual Studio 2010, stsadm, or the SharePoint Management Shell:

  • Any time my workflows are activated by the System Account when an item is created or changed, the previous codebase is used to run the workflow. That means the changes I've made have taken no effect.
  • Any time the workflows are activated manually using the Workflows form under "Start a New Workflow," the updated codebase is used to run the workflow. The changes I've made appear to work just fine.

How do I completely root out the previous version of the solution? I've already read through this article detailing the same scenario, but this solution is deployed to the farm and the guidelines there were unfortunately no help, even if I changed the parameters to stsadm so that it did not target a web application.