Hi,
Currently working on a project that has multiple libraries. I would like to add these all to a single .uipx solution, but that only seems to accept processes (for some reason).
I should be able to both have a process and a logic/reusable (library) layer in the same solution.
This is standard functionality in dotnet, and tons of other frameworks/languages.
As a side note: the documentation on solutions also seems very poor, and thus also quite hard to create one in the first place.
Hi @thomas_v ,
Thanks for the feedback. You’re right that today .uipx Solutions don’t include libraries. Could you share a bit more about how you’d like to use the libraries inside a solution and why you would need them inside a solution rather than creating a Library and consuming it in a solution? This would helps us better understand this use case.
Regarding the docs, just to confirm, this feedback is related to this docs Studio - Solutions?
Hi @Raluca_Laic,
We have multiple projects that rely on a set of libraries for a specific application. We chose the library route for reusability and maintainability.
Technically we could make this one big library instead of multiple. But splitting these up makes more sense, since not every runtime project requires all of the libraries.
Splitting these up also makes it easier to maintain, since you can more easily find what you’re looking for and libraries remain smaller.
Now as to why I would like to see library support for solutions: since we split up our libraries, but those libraries are still part of the same project (or another word; Solution). It would be ideal to group all of those together in the same solution, while still being able to publish them separately. This would make it much easier to develop and maintain large, split up libraries.
We think this would allow for more easily creating libraries for applications, that are easy to maintain and well organized.
This would also make CI-CD easier, since we would be able to use UIPCLI with solutions instead of each package separately for restoring nuget packages (and caching one large nuget dir. instead of 20 still large ones, because all libraries are separate).
As for the documentation, yes I’m referring to Studio - Solutions (2025.10 LTS in our case, but any for the matter). Specifically the lack of how to create a solution not being present on that page, or really any page for that matter.
For example, on the mentioned page, it states:
Keep in mind these differences when working with solutions in Studio and Studio Web:
- New solutions can only be created in Studio Web. You can open and edit existing solutions in Studio, which is context-aware and allows you to enhance solutions with cross-platform and Windows RPA projects.
But when I look in studio web, I only see the following options:
As far as my eyes can tell; there’s no option to create a new solution. Only to open an existing one from Studio Desktop! Which exactly contradicts the statement in the documentation!
In the end I had to make a .uipx file manually in notepad, only to find out I wasn’t able to add libraries to it.
We use LTS, because we are an enterprise and we highly value stability, but it seems like LTS stands for “Less Than Sufficient”; missing basic functionality, and out of date documentation.
