Page 1 of 1
Ranorex still uses old version after NuGet self update
Posted: Thu Mar 15, 2018 5:30 pm
by hellboy81
Hi
I have self updated NuGet from Command Line with admin rights
RS is restarted but NuGet.Core.dll, PackageManagement.dll and other libraries in
PackageManagement dir still out of date (as excepceted
)
Questions:
[*] Is there possible to install into RS project using new updated NuGet version?
[*] Is there possible to update another files?
Is this feature requests are still open:
Support new NuGet format
It`s not possible to update NuGet client version
?
Re: Ranorex still uses old version after NuGet self update
Posted: Fri Mar 16, 2018 11:29 am
by RobinHood42
Hi,
As stated within the feature requests, it's not possible to update the NuGet package manager within Ranorex Studio. Simply up-vote the feature request, to increase its priority. Once the "idea" gets a reasonable amount of votes, Ranorex folks consider to implement them.
Cheers,
Robin
Re: Ranorex still uses old version after NuGet self update
Posted: Mon Mar 19, 2018 1:50 pm
by hellboy81
OK, The last NuGet version supported by RS is 2.8
With last NuGet.exe I cannot restore packages directly:
I got
The file type was not recognized
Is it really Ranorex compatibility problem or NuGet bug?
Re: Ranorex still uses old version after NuGet self update
Posted: Mon Mar 19, 2018 2:47 pm
by krstcs
NuGet does not recognize *.rxsln files. That is a Ranorex specific file. You need to use the *.sln file of the same base name.
Your solution folder should have these files:
MySolution.sln <- Use this one
MySolution_VS2010.sln
MySolution.rxsln
Any file with RX in the extension is Ranorex specific and will not be recognized by tools other than Ranorex, in most situations.
Any version of NuGet supported by Ranorex Studio will work with *.sln files, and that is actually what Ranorex Studio passes to NuGet when you update packages.
tldr; use the *.sln file instead.
Re: Ranorex still uses old version after NuGet self update
Posted: Tue Jul 10, 2018 7:49 am
by hellboy81
As I mentioned this bug has been fixed in last RS version 8.2