I have a test suite that was building and running acceptably under 8.2.1. I upgraded to 8.3.1 due to other presumably unrelated issues that apparently lead to Ranorex staff insisting could only be dealt with by upgrading to 8.3. I have done so, and as expected Ranorex needed to upgrade the project. Now however the project refuses to build. No errors are returned - it just appears to hang.
I renamed the release folder and Ranorex unsurprisingly recreated it, but even after 15-20 minutes it's still empty. I'm running Ranorex as administrator.
Does anybody have any idea what's occurring here and how to fix it?
Problems after upgrading to 8.3 from 8.2
Re: Problems after upgrading to 8.3 from 8.2
Hi,
What OS and .Net version are you using? Have you tried to build a new solution? Are you using some external references in failing solution? Please check the "What's new" notes, mainly breaking changes mentioned in 8.3.0. Oh and one more thing! Have you simply updated 8.2.1 with 8.3.1 or you first uninstalled 8.2.1? Although the update process should work just fine, it's generally recommended to first uninstall old version and only then install new one
What OS and .Net version are you using? Have you tried to build a new solution? Are you using some external references in failing solution? Please check the "What's new" notes, mainly breaking changes mentioned in 8.3.0. Oh and one more thing! Have you simply updated 8.2.1 with 8.3.1 or you first uninstalled 8.2.1? Although the update process should work just fine, it's generally recommended to first uninstall old version and only then install new one
Pavel Kudrys
Ranorex explorer at Descartes Systems
Please add these details to your questions:
Ranorex explorer at Descartes Systems
Please add these details to your questions:
- Ranorex Snapshot. Learn how to create one >here<
- Ranorex xPath of problematic element(s)
- Ranorex version
- OS version
- HW configuration
Re: Problems after upgrading to 8.3 from 8.2
I upgraded without uninstalling first. Repeating the installation but with the uninstall first appears to have fixed things. Thanks for the pointer.