Process for Updating Dependencies in Orchestrator

Help Orchestrator
1

Hi all,

We updated from Orchestrator 2019.10 to 2020.10 and utilize an on-premise solution currently. When we upgraded, we got new versions of many of the main libraries like UiPath.System.Activities 20.10.1 and UiPath.UiAutomation.Activities 20.10.6, etc. However, the sub-dependencies that those main libraries rely on like Newtonsoft.Json and Microsoft.Bcl.AsyncInterfaces did not come over. Because we are a credit union that deals with sensitive member information, we restrict access to Myget and Nuget internally and the bots cannot simply download required packages from those sites.

Can anyone recommend a process for ensuring that we can get the required dependencies and sub-dependencies to our end users so that we can take advantage of new library versions and their functionality? I’ve been in touch with UiPath support and the initial suggestion was to edit two text files and remove any reference to Myget or Nuget from them but we would have to deploy that to all of our current end user machines and virtual machines and that still doesn’t answer the question of how to get all of the sub-dependencies we need into Orchestrator.

Please let me know if you require any clarification.

Thanks!

2

Mark - curious if you ever resolved this issue? I have a similar scenario and looking for a more efficient and optimal way to ensure that Dependencies are accessible in a more localized fashion that have to access and download externally.
I am really surprised that UiPath Studio does not fully package all Dependencies locally and upload them to Orchestrator as Libraries at the Tenant or Host Level.

3

Hi Scott! I agree; that’s how I thought it would/should work initially but they’re completely separate entities. Either way, we ultimately solved our issue by working with our IT security teams to open up certain machines to those MyGet and NuGet endpoints. We’ve also established a stable set of libraries internally that we work with, updating it every so often when see a few versions elapse of the main packages. When we update our stable libraries, we ensure that they’re uploaded to, and available in, each tenant of Orchestrator.

Hope this helps! Good luck with your automation program!