Ranorex looking in wrong location for .ini file

Ranorex Spy, Recorder, and Studio.
Oisin
Posts: 2
Joined: Mon Jan 07, 2019 4:50 pm

Ranorex looking in wrong location for .ini file

Post by Oisin » Mon Jan 07, 2019 4:59 pm

Hi there,

When I manually start my Windows application under test, it starts correctly and the required .ini files are found and read. When Ranorex starts the application, it looks in the wrong location for these files, it is looking in C:\..\RanorexStudio Projects\LogIn\LogIn\bin\Debug\Config\ (where the solution is called LogIn). Can anyone tell me how to set the correct location?

Many thanks

User avatar
RobinHood42
Posts: 283
Joined: Fri Jan 09, 2015 3:24 pm

Re: Ranorex looking in wrong location for .ini file

Post by RobinHood42 » Tue Jan 08, 2019 9:03 am

Hi,

You could try to use an automated double-click on your application under test to open up the app.

Cheers,
Robin

User avatar
odklizec
Ranorex Guru
Ranorex Guru
Posts: 4655
Joined: Mon Aug 13, 2012 9:54 am
Location: Zilina, Slovakia

Re: Ranorex looking in wrong location for .ini file

Post by odklizec » Tue Jan 08, 2019 9:06 am

Hi,

Have you tried to define working directory path in Run application command?
WorkingDir.png
WorkingDir.png (2.89 KiB) Viewed 93 times
Pavel Kudrys
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

Oisin
Posts: 2
Joined: Mon Jan 07, 2019 4:50 pm

Re: Ranorex looking in wrong location for .ini file

Post by Oisin » Tue Jan 08, 2019 10:48 am

Bit of a school boy error. I set the working directory, and now it runs like a dream.

User avatar
odklizec
Ranorex Guru
Ranorex Guru
Posts: 4655
Joined: Mon Aug 13, 2012 9:54 am
Location: Zilina, Slovakia

Re: Ranorex looking in wrong location for .ini file

Post by odklizec » Tue Jan 08, 2019 11:47 am

Cool. Nice to hear such simple trick helped ;)
Pavel Kudrys
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