"Attended Named user" Publishing the robot

Help Something Else
12

Hi @Sudharsan_Ka,

Lets take a step back. We know that UiPath attended license does not allow publishing without connection to Orchestrator. My three suggestions would be

Alternative 1:
In your development machines (having Studio Pro) just ensure you have a version control (Git or TFS). Every commit to the repo can thereby be built and published to your orchestrator or the agent machine’s disk using UiPath Azure Devops Integration - News / Tutorials - UiPath Community Forum. This way you will avoid needing to edit the .xaml files in the attended name user license.

UiPath Attended Name user License will have access to the packed files from DevOps so the process runs will have no impacts.

Alternative 2:
Use your Studio Pro licenses as floating licenses using machine templates. This way when you want to publish from the Attended Named user pc/server/vdi you have access to all StudioPro tools. Once you have published then you can disconnect from orchestrator and allocate the attended license to the user in Orchestrator.

Alternative 3:
Build package using UiRobot.exe and move the nuget file to the required location for the assistant to use. Take a look at two good answers from @johnfelix and @Marc_Bourgeois
How to create Uipath Project nuget package in command line - Help - UiPath Community Forum