Our team is working on automating the project deployment and code migration from one environment to another environment. So anyone can help us regarding to the below questions?
UIPath claims to support both TFS and SVN as source controllers, are these source controllers just for storing the source code are we can build and publish the code from these source controllers?
If we cant build and publish, can anyone tell what the dependency dll files we can refer used for creating the nuget package when we click on publish button from studio?
Is there any other ways to make the nuget package like UIPath studio creates when we click on publish?
UiPath claims to support both TFS and SVN as source controllers, are these source controllers just for storing the source code are we can build and publish the code from these source controllers?
TFS / SVN are to be used to centralize source management, and only meant for Studio access.
If we cant build and publish, can anyone tell what the dependency dll files we can refer used for creating the nuget package when we click on publish button from studio?
Please grab a nupkg that was built from Studio to see its insides.
nupkg are basically special zip files, but you can also use appropriate tools such as NuGetPackageExplorer available from the Windows Store.
Is there any other ways to make the nuget package like UiPath studio creates when we click on publish?
To create an appropriate package from outside Studio, I would advise you learn about nuspec files, and how the nuget.exe “pack” command works.
Yes, we can integrate UiPath with TFS(follow the link “About Version Control” ), build and deploy the code. we are in process of learning it and will provide the information if we are 100% successful with it.
I am having this issue , whatever the Package path i give it to it , it is always finding the package in the temp folder of the same job. It is not uploading the package from the path i am giving to it