I still don’t see an official answer for what the Library.runtime package is that shows up in Orchestrator under Packages\Libraries. I don’t really care what it is or why it’s there, but I need to know…
We migrate packages manually from QA to production by downloading them from QA Orchestrator and uploading them into production Orchestrator.
Do we need to include the Library.runtime package now and move both of them?
Neither of those answer my question.
This you would see in the second link…stating difference packages for robots and stuido
its better to include…if you see the first link in that dependencies issues are created if runtime packages are not moved
cheers
Not a case of better, you have to.
The links do answer your question Paul, it just requires some reading.
The TLDR is that they separated the code so the Ui stuff you see in Studio is now separated from the running code, which is more in line with other activity packages made in Visual Studio.
Apparently this allows faster loading when running a robot unattended. Seems completely pointless to me considering the added frustration / annoyance of needing to sync two packages as that wastes much more time than I’d save on a few milliseconds on memory (still not seen the stats to justify the time save on this).
You can turn this off, but its on by default, which really sucks.