I encountered a minor issue this morning which has become quite recurring, over the last few years I’ve found myself needing to move a UiPath project between two machines and this one contains some dependencies that are not available on the recipient machine.
For the known packages, they are quickly resolved by the click of a button in “Manage Packages”, but for custom ones the sender should navigate to his local Packages folder and search for them one by one and send them separately. Which is quite exhausting I might say.
After a quick search on the forum, I found out that UiPath doesn’t provide such a feature to export all project dependencies in a detailed and structured format.
So I was wondering if the UiPath team could try and find a solution for this issue in the upcoming versions, if there isn’t an existing one already that I’m not aware of.
This is a confusing ‘problem’ as the dependencies should just be resolved when the robot runs, its not machine specific, infact its easy to just purge the dependencies on one machine and let them re-download them.
So the question then becomes, why aren’t your packages in the Orchestrator, and therefore easy to get, or from one of the nuget feeds? What packages are you deploying entirely locally and why?