Hi All,
How to link the Upgraded new Library with the existing already old published Process? so that after publishing the new version of the Library into the tenant it will automatically get linked with the Process as well ?
Regards,
Ritesh
Hi All,
How to link the Upgraded new Library with the existing already old published Process? so that after publishing the new version of the Library into the tenant it will automatically get linked with the Process as well ?
Regards,
Ritesh
You can’t. You’ll have to open each individual project, update the dependency, then republish the project.
Hi @postwick
If we delete the old Library versions from orchestrator Library and Publish the new Library version just by changing the Version name as it is same like New Version =1.0.1 and publish it there ,will it work? just assume in the current process also this library version is same (1.0.1)
Regards,
Ritesh
Is there any reason keep the name of the version same?
It is hard to give same name of a different version project in the uipat assistant.
It will publish without any issues. But make sure you’re deleting the package not only in Orchestrator, but also in the nuget folder of the server you ran this process earlier. Because, sometimes it will pick the nuget package that was already installed in the nuget folder within the server as the versions are same.
If there is any code change in the library, it will not automatically update in the project. You’ve to update manually.
Thanks!!!
No. You have to update each project so its project.json file has the new version of the package listed.