I have been working on a project that involves developing a custom workflow activity for SharePoint 2013. I am developing it in a single server environment working with http. My problem occurs when deploying to multi-server environment with https (WFE, APP). My question is how to deploy my solution to the new environment.
The steps:
- Create a project - c# activity library
- Add a workflow activity, add .xml
- Deploy the .dll and .xml of project to "C:\Program Files\Workflow Manager\1.0\Workflow\Artifacts" "C:\Program Files\Workflow Manager\1.0\Workflow\WFWebRoot\bin"
- net sotp "Workflow Manager Backend"
- net start "Workflow Manager Backend"
- gacutil to deploy the .dll to GAC
- iisrest
- Create a project - empty SharePoint 2013 project
- Add a workflow custom activity to project
- Edit .actions4 and .xaml (my custom code from previous project is in this project now that i can drag and drop in .xaml)
- Deploy to server, activate feature, open SharePoint Designer 2013 and choose the custom action that now appears when creating a 2013 workflow
This all works fine and dandy on my single server environment. Workflow is working like a charm. How should I go about deploying this to a multi-server environment with https? Does that server need Visual Studio on it also? I have continued to deploy the .dll and .xml to the workflow manager backend folders. I have continued to deploy the .dll to the GAC also. When I upload the solution to the new site, it continues to work. When I open designer to create the workflow, it breaks and i cannot create or edit any of the workflows on that site. Do i need to be doing something different because i am going from a http environment to https?
Let me know if this is unclear or if anyone needs more information. Thanks