I have a Ranorex solution that contains several tests. Up until recently, there were a couple common functions that I would copy into each test's UserCode.cs file. Yesterday, I decided it'd make a lot more sense to add a base class to each test that contained the commonly used functions so I could stop copying them. As expected, this built successfully and worked.
However, if I now open a recording, Ranorex sees that my recording has UserCode actions and automatically regenerates the function signatures in the test's UserCode.cs file, despite the inherited class already having the exact same function signatures.
How can I get Ranorex to stop doing this seemingly helpful, but actually irritating behavior? Is there a way I can fool Ranorex into thinking the method signatures are present in the UserCode file, so it won't regenerate them?
Thanks,
-Craig