Separate design time and runtime dependencies

Feedback Studio
1

So, really not a fan of this new feature. It creates a huge amount of clutter in my packages feed now as each library I publish becomes two libraries so I have twice as many packages as before and must filter out and ignore the runtime ones.
Seems like a ton of overhead for what I imagine is miniscule time savings on downloading packages as they aren’t all that big anyway.

Why isn’t this an optional thing for if you do have a package is too large and leave us with the simple single packages as default?

image
image959×373 39.9 KB

4

Thanks for the feedback. We will consider in the next release and maybe expose this as a customization.

The downside of the “overhead” it’s that robot will execute faster and download smaller packages.

6

Yeah, I get that, but I’m saying for the time saved for 500kb of a nuget to download, I think I’ll waste more in managing packages and forgetting to move one from one tenant to another causing missing dependencies etc resulting in a much larger net loss.

I don’t know how much faster the bots run after downloading, perhaps you can elaborate on that, but again I don’t expect that to be suddenly increasing processing speed by like 20% or something.

1 Like
7

So these things have reared their ugly heads again and I still hate it and cannot see any value, only downsides (please give me some stats on performance increase if thats a thing as the package size cannot be affected imo as both are still needed to run the bot.). Mercifully its now an option but set to default to split (weird choice) and I hate needing the change this everywhere.

The documentation states that it can be handled with a Governance Policy, I checked Automation Ops and cannot see it, can anyone waypoint me to how to turn this off?

3 Likes
8

So I managed to find a way to turn of this feature which is rather merciful as its really annoying and provides no tangible benefits (still not possible by Automation Ops as far as I know despite the documentation claiming so).

In order to turn it off entirely on your machine, go to your UiPath Install folder, navigate to the ‘Profiles’ folder and open the ‘Development.json’ file. In this file find the key ‘EnableLibrarySplitToDesignAndRuntime’ and set it to false and for good measure do the same for the key ‘EnableProcessSplitToDesignAndRuntime’.

I hope this helps some people :slight_smile:
Please turn this off by default UiPath or at least give a good reason for such inconvinience in package management introduced by this.

4 Likes
9

Hi @Jon_Smith , posting a response in case it’s still useful or for others who come across this thread.

To see the option in Automation Ops you would need to update your settings to use the “23.4.0” version first. (Note this may impact existing policies)

image
image2494×868 141 KB

Once you’ve updated the setting, you should see the following settings in the policy under the “Design” tab:

image
image732×768 36.7 KB

Hope that helps :slight_smile:

10

Thanks for sharing, I was wondering the same.

At least in my current (2024-01-09) UiPath Studio 2023.4.5 the setting can (now) be made per-project

  • with a click on the cog icon “Project Settings”, then immediately under “General” with “Separate Runtime Dependencies”
  • which then persists within the project folder into .project\design.json as "SeparateRuntimeDependencies": false,

(I just wanted to add this to the otherwise already informative thread. Maybe I forget and will find this again in a few months :slight_smile: )