Linked Repositories not handled correctly

Bug reports.
Posts: 7
Joined: Tue Jun 01, 2021 8:56 am

Linked Repositories not handled correctly

Post by ContiChris » Fri Jun 18, 2021 7:03 am

Ranorex 9.5.0
Regarding to the post Linking a Repository i prepared an example.
The project in the ./common/rx_modules/example/src/modules.rxsln solution reference the repository ./common/rx_repos/example/src/example_app/example_appRepository.rxrep as a link. The link is kept in the the project's folder _Repositories.
Building the solution with Ranorex copies the repository's code file example_appRepository.cs to the _Repositories-folder, which is fine.
Building the solution with msbuild (how it will be done on e.g. Jenkins) does not copy the cs-file, so the build will fail.

For projects that are under version control that behavior is very bad. The repository has to be stored twice. The project that references the repository will not get the latest version when building with msbuild.
You do not have the required permissions to view the files attached to this post.
Last edited by ContiChris on Mon Jun 21, 2021 6:35 am, edited 2 times in total.

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

Re: Linked Repositories not handled correctly

Post by odklizec » Fri Jun 18, 2021 10:33 am


The problem is, that linked repositories are a Ranorex-specific thing. Plus cs files are generated from rxrep files (the same as recordings). And because MSBuild builds only MSBuild-comaptible files, it cannot build rxrep (or rxrec) files directly. In other words, MSBuild requires pre-generated cs files. And this is why you should always store cs files in your source control system, not just rxrec/rxrep files. It's definitely not a bug.
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

Posts: 7
Joined: Tue Jun 01, 2021 8:56 am

Re: Linked Repositories not handled correctly

Post by ContiChris » Mon Jun 21, 2021 6:46 am

the thing is that the cs files are kept on two places (first in the folder where the repository resides and second in the folder that has a reference to the repository) which will lead to failures because one of them will not get updated automatically.
I think there would be a way for Ranorex to automatically put a pre-build copy (or something similar) to the project-file in case a linked repository is used.
Maybe not a bug but a very bad behavior.

Posts: 1
Joined: Mon Oct 31, 2022 6:01 am

Re: Linked Repositories not handled correctly

Post by kinithhettiarachchi » Wed Oct 11, 2023 10:31 am

We are facing the same problem and it would be handy if there is a command line command/tool to generate .cs from .rxrep.

We have a large product which may contain 50-100 solutions due to its complexity and design. For us, this mean opening and building those 50-100 solutions one by one to fix this issue!