Page 1 of 1

Ranorex 7.1 upgrade -- error

Posted: Fri Jun 30, 2017 2:39 pm
by Jimmyto
Hi all,

Just completed the Ranorex upgrade and suddenly received this error after trying to run a TC.

Could not load file or assembly 'Newtonsoft.Json, Version=8.0.0.0, Culture=neutral, PublicKeyToken=30ad4fe6b2a6aeed' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040) (InnerException: -- )

I've created a new TC since this one was converted to newest version and reloaded the JiraReporter in which currently working on and still receive the error.

I've looked at the pacakages.config file and can see the line (below) but what will be the new value?

<package id="Newtonsoft.Json" version="8.0.3" targetFramework="net40" />

Any help is greatly appreciated and Thanks in advance!!
Jimmy

Re: Ranorex 7.1 upgrade -- error

Posted: Mon Jul 03, 2017 1:13 pm
by asdf
Hi Jimmy,

I would recommend just adding the NuGet package "Ranorex Jira Reporter" again to your project.
You could also use "Install-Package Ranorex_JiraIntegration -Version 7.0.1.1" in the package management console in order to install the NuGet Package.

Please let us know, if this helps you to overcome your problem.

Sincerely,
asdf

Re: Ranorex 7.1 upgrade -- error

Posted: Mon Jul 10, 2017 6:59 pm
by Jimmyto
Hi asdf and Thanks for your suggestion.. was out on vacation :D

Ok, so, remove it and added again and still same error. Any other suggestion? or maybe someone can provide the version to try?

Thanks in advance!!
Jimmy

Re: Ranorex 7.1 upgrade -- error

Posted: Mon Jul 10, 2017 7:50 pm
by Jimmyto
looking at my references
Newtonsoft.Json --> Properties version 6.0.0.0

packages.config
Newtonsoft.Json --> version=8.0.3


Could this be the problem? I've updated the version to match the reference to 6.0.0.0 still... not working!

Remove the reference Newtonsoft.Json --> Properties version 6.0.0.0 from my reference, reinstalled it and same problem.

Could this be a Ranorex 7.1 bug? :shock:

This began after I upgrade to 7.1, last resource will be rolling back to 7.0. Just glad I'm the only one the upgraded to 7.1 for testing purposes.

Re: Ranorex 7.1 upgrade -- error

Posted: Tue Jul 11, 2017 12:57 pm
by Jimmyto
@RanorexSupport team..

Do you guys have an answers for this issue?

Re: Ranorex 7.1 upgrade -- error

Posted: Tue Jul 11, 2017 4:25 pm
by krstcs
If you want a quick answer from Ranorex support, you should email them at [email protected] (if in US timezones) or [email protected]. They are usually much more responsive through email.

Re: Ranorex 7.1 upgrade -- error

Posted: Wed Jul 12, 2017 8:38 am
by xeronar
Hey everyone,

I'm having the same issue as mentioned in another topic (https://www.ranorex.com/forum/jira-inte ... 11055.html), I've contacted the support and they said that they can reproduce it: "Adding Jira references to Ranorex 7.0.1 worked as expected, but there seems to be an issue when adding them to Ranorex 7.1.0."

So they are keeping track of it and will inform me/us if they got more information according to this problem.

Re: Ranorex 7.1 upgrade -- error

Posted: Mon Jul 17, 2017 12:11 pm
by Support Team
Hello Everyone,

This issue occurs since Ranorex 7.1.0 and will be fixed in one of our next releases.
However, we suggest using the workaround described under the following link in the meantime:

https://www.ranorex.com/forum/jira-inte ... tml#p44819

Thank you for your understanding.

Regards,

Stephan

Re: Ranorex 7.1 upgrade -- error

Posted: Wed Jul 19, 2017 2:39 pm
by Jimmyto
Hi Xenorar & everyone,

If that workaround does not work please try this.. This Solution was provided by Jon support team from Ranorex and worked for me.

1. Create a new blank solution in Ranorex
2. Convert the target framework to version 4.5.2
3. Save and Close Ranorex Studio
4. Open the solution using Visual Studio (2017 recommended, I am using the free community version)
5. Add the Ranorex Jira packages
6. Close Visual Studio
7. Open the solution in Ranorex Studio and Build the solution

Thanks!
Jimmy