Managing updates to shared project code across packages
We are looking to implement a multi-project structure in our robotic automation solutions/packages where there would be a controller project and multiple other projects in the same solution. These other projects are each responsible for interaction with a different system.
Setting up this structure is easy enough, but my question is about how to handle the distribution of updates to these 'system projects'.
For example, if we have a system project called 'Siebel' (for handling all automation interaction with Siebel) and that project is used in multiple different solutions/packages, when the Siebel project needs to be updated (bug fix, or new interrogation, etc...) what is the safest method of updating all of these solutions/packages with the updated Siebel project?
Can the project simply be deleted from each solution and then re-added from the updated version of the Siebel Project?
Is there a better way to handle this?
If you are referencing the Siebel project from within your controlling project (Add Existing Project), then whenever you open it in Studio the updated referenced project would get loaded. You could create a new deployment and it would reflect the updated Siebel project. As long as that did not materially change anything that you are using in your automations, then they should continue to work as intended.
When you "Add Existing Item" that imports it. When you "Add Existing Project" that references it from where it is located on your disk. You could use your source control system to store these shared projects in a common directory.