Publish official Ranorex NuGet package
Please publish the core Ranorex libraries in an official NuGet package in order to allow for easier management of Ranorex integration into projects.
Kelly
shared this idea
Currently we are investigating all possible use cases for this idea.
It would help us a lot if you could comment your project setup and how you are adding Ranorex to it. Thx a lot.
Best regards
Ranorex Product Management
12 comments
-
W. Triebkorn
commented
We are using Azure DevOps build agents to build our SW (one agent per machine). Currently we have to install Ranorex on every of these machines. These agent were used by different teams and they use different versions of Ranorex. This leads to conflicts on the build agent.
Expected: The Ranorex assemblies for building shall be included as nuget package. Every build can use a different version of Ranorex assemblies.
-
KevSer
commented
As a use case, I would say that we need to publish libraries relying on Ranorex methods and then, in a second time, use it in a Ranorex Solution.
-
J-F Lemay
commented
One example could be that I have a farm of 100 agents and I use GitLab to dispatch a Ranorex test to run on these machine and it's not always the same agents that is picked and I don't want to install Ranorex via the installer on each machine. Having a Nuget package of the binaries can help me to simply install the required DLL for my test to compile and run on these agents(it will still take a license from the license server).
Another example, I do a library of Ranorex method. I can simply reference the Ranorex nuget package in order to make it compile and access the Ranorex api methods.
-
Sylvain Girard
commented
Well has Hugo said having a NuGet ranorex package would simplify things for us, as our builds process already used them.
-
Hugo Trudel
commented
Publishing to a public source is not really important since they could be easily published to a local repository. It's the creation of the packages that is mostly requested here. We could do it, but it would be much more simple for Ranorex to install them to a local folder when installing Ranorex Studio for example.
-
Hugo Trudel
commented
When Ranorex is used to implement CodedUI tests in Visual Studio, having Ranorex NuGet packages would simplify things a lot IMHO...
-
Anonymous
commented
If you create an official nuget package, please add Ranorex.Controls.dll to the Runtime.
-
Marc Baillargeon
commented
It does not really help us since the build machines need to build the ranorex solution which requires to have ranorex installed. But ranorex is not installed on our build machines. Hence the request to have it as a nuget package.
-
Ranorex provides the option to copy all necessary DLLs to the output directory (Settings -> General -> Copy runtime to output). Like this, you don't have to add Ranorex libs manually.
Wouldn't this help you in your situation? -
Marc Baillargeon
commented
We also use xcopy deployment to execute our tests on our build machines which don't have Ranorex installed. But since Ranorex is not installed on our build machines, we also had to write custom code that changes the references to the ranorex libs in the .csproj to a nuget package that we created ourselves. It would be much simpler if the Ranorex csproj would reference ranorex libs from a nuget package by itself.
-
Sven-Dimo Korsch
commented
We are using the xcopy deployment. Which means we need Ranorex during build time to deploy it to our binaries. Since we try to avoid adding binaries to our source control system nuget would help us a lot here. So we can get rid of unzip scripts in our build scripts.
-
Anonymous
commented
me2