In the past we always got separate packages for the libraries we publish. I see that there’s now a setting for this in Studio 2024.10.8 and I have that setting set to Yes:
But I published the library and it did not publish the runtime:
Between the last publish (23 days ago) and now, I was upgraded from Studio 2023.x to 2024.10.8.
Hello @postwick!
It seems that you have trouble getting an answer to your question in the first 24 hours.
Let us give you a few hints and helpful links.
First, make sure you browsed through our Forum FAQ Beginner’s Guide. It will teach you what should be included in your topic.
You can check out some of our resources directly, see below:
Always search first. It is the best way to quickly find your answer. Check out the 
icon for that.
Clicking the options button will let you set more specific topic search filters, i.e. only the ones with a solution.
Topic that contains most common solutions with example project files can be found here.
Read our official documentation where you can find a lot of information and instructions about each of our products:
Watch the videos on our official YouTube channel for more visual tutorials.
Hopefully this will let you easily find the solution/information you need. Once you have it, we would be happy if you could share your findings here and mark it as a solution. This will help other users find it in the future.
Thank you for helping us build our UiPath Community!
Cheers from your friendly
Forum_Staff
I forwarded it to our internal channel for the team to investigate. Thank you for the mention.
I published another library this morning and did get both the activities and runtime packages. So now I need to understand why I didn’t get them on the other library and what the impact is to projects that have that dependency installed.
I got some answers.
Apparently, we made an optimization to only do the split when necessary. A blank library will not cause the split, but adding an input argument and defining it as a dropdown will.
This was documented over here:
Specifically:
I hope this clarifies things!
It doesn’t clarify things. It clearly says it will generate the separate packages if the Separate Runtime Dependencies option is enabled. I had that option enabled but I did not get separate packages.
If I understand this correctly, then the separation only occurs when both of the conditions are met. It can be that the separation is not needed if the ViewModels.dll file is not neither as per the specific library project configuration.
