Hi,
we working with Ranorex and SVN, with three to five developers at the time, and have a hard time managing the project under version control. To prevent conflicts, we ignored (svn:ignore) binaries as well as reports along with their screenshots:
[*] Reports
[*] bin
[*] obj
[*] *.jpg
[*] *.rxlog
After this we got often conflicts in the "*.rxuser" files, so we ignored them too, which seems to work without any problems.
To prevent conflicts on the test suite (".rxtst"), only one developer is responsible for changes in the test suite. An alternative would be to work with "svn lock" on this file.
This is our setup so far, but we still get a lot of conflicts because of:
[*] generated module ids that change
[*] absolute paths in the .rxrec file's references
[*] changing order of references in the .rxsln file
(Disclosure: I'm not a C# / VisualStudio developer and I'm not sure which parts of this are inherent)
My overall impression is Ranorex is not very VCS friendly and some sort of setup instructions are needed. That said, general tips on Ranorex with VCS as well as concrete tips for the mentioned problems would be highly appreciated.
Thanks and regards,
Tim