Runtime Packages after downloading nupkg from orchestator

Hi folks, I usually download the package directly form orchestrator and change extension to zip, so I can extract the code from the nupkg and no need to use git, I use the control version directly from orchestrator.

But what I notice from last year is that now when you do this approach the dependencies come as “Runtime” and you need to remove all the Runtime packages and reinstall in order to get the code properly open again.

Do you guys know why this happen? What kind of approach do you use as version control? Would be great to be able to use the version control directly from orchestrator for the code itself, but since only the package is there we need to convert to zip and extract the code, and then update those dependencies manually

@Michael.Vornes,

Follow my article on this. You will get reason and solution for this.

Thanks,
Ashok :slightly_smiling_face:

@ashokkarale what a great article, very clear and informative, I didn’t know that was possible to disable that option, thanks a lot for sharing the information!

1 Like

@Michael.Vornes,

Glad to know it was helpful :smiling_face:

Happy automation!

Thanks,
Ashok :slightly_smiling_face:

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.