Ranorex Forum

I've upgraded my copy of Ranorex to 8.3.2, but now when I try to start Ranorex it just stops. The task item for Ranorex Studio appears in the task manager for a second or two but then disappears. Nothing else happens and Ranorex fails to start. No errors are displayed.

Any idea what's happening here?

Hi,

This problem happens if you install 8.3.2 over 8.3.1, without uninstalling 8.3.1. We already discussed this problem here:
cannot-run-ranorex-after-update-to-8-3-2-t13145.html
The solution is to completely uninstall Ranorex Studio and then install 8.3.2 again. Hope this helps?

Thanks for the quick reply. I'll try that. Come to think of it I seem to recall you suggesting the same when I had issues upgrading from 8.2 to 8.3.

It seems a little odd though that the installer seems incapable of dealing with existing installations.

As for me, I'm always uninstalling existing version before installing new one. Just last time, I forgot about it and experienced such issue Installation over existing version should definitely not cause problem like this. As far as I know, Ranorex folks already investigating this problem.

Thanks for that. It worked.

Just in case anybody from Ranorex happens to read this thread, I'm now getting the following error when trying to run the project in 8.3.2 that was created in 8.3.1:

Cannot intercept exception. Debugged program can not be continued and properties can not be evaluated.
System.IO.FileLoadException: Could not load file or assembly 'Ranorex.Core.Resolver, Version=8.3.1.0, Culture=neutral, PublicKeyToken=b798506b574ebc9a' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)

I'm assuming it's just the references that need to be updated, but if they change from one version to another shouldn't Ranorex itself be checking for this when opening the solution and offer the option to upgrade them, at least when it involves the core Ranorex references that all such projects probably have?

I'm not experiencing such issue. But it seems the solution is to rebuild a solution?...
viewtopic.php?f=4&t=12968&p=51545

D'oh! I could have sworn I'd already done that.

Oh well. Thanks for pointing out something I ought have been able to figure out myself. Not enough coffee this morning I think...