Export Nuget Project from Orchestrator

"Hello, dear forum. This is Luis Fernando Pazos.

Today, as usual, I have a question I want to bring to the community. The case is as follows:

Lately, I’ve been working on projects where I have to constantly export the project so I can continue working on it on another machine. I know there are multiple ways to do this, such as compressing the project folder into a zip file and sending it via email. However, lately, I’ve liked the idea of publishing the project to my tenant and then downloading the NuGet package of the corresponding version.

The thing with this “methodology” that I know very little about is that when I open my project, the activities seem to be like some kind of custom activity or something similar. They don’t have their typical activity structure, and sometimes they are completely unable to edit the project properties.

As I mentioned before, I know nothing about the reason for this behavior, and I’m sure there must be a simple reason why. If someone could provide me with some clarity, I would really appreciate it."

These two images show the exact same sequences, but the first image represents the project in its raw state, while the second image is the project after I download and open it in my studio which clearly is in another format.



Hi, @Luis_Fernando

The better way to deal with this scenario is using a version control system, like Azure Repos, Git Hub etc. Both have free plans.

If you want to learn more, you can do this shorter course in UiPath Academy

1 Like

Thank you @rikulsilva I do know about both tools, but to be honest, I haven’t really used them. But the main goal of my topic is to understand why it is that when we download a package from our orchestrator, the project opens in that ‘format,’ as shown in the images. Yet, thank you very much for your response; you encourage me to start using the free versions of those tools.