CLR Bridge and .NET Method Overloads - Ordering
Interfacing between .NET assemblies and the TestComplete script environment is known to be challenging since the latter does not support method overloading. Rather, it appends a suffix (e.g. Method(), Method_2(...)) to the method name.
We recently came upon an issue where a developer added a new signature to a particular method, and when the TestComplete script ran it selected the new, incompatible one instead of the correct, older one.
My question is:
Is there any way to know in advance how TestComplete will number the method overloads?
How does TestComplete determine which signature is the "original" and which is the "overload" - with a numbered suffix?
We recently came upon an issue where a developer added a new signature to a particular method, and when the TestComplete script ran it selected the new, incompatible one instead of the correct, older one.
My question is:
Is there any way to know in advance how TestComplete will number the method overloads?
How does TestComplete determine which signature is the "original" and which is the "overload" - with a numbered suffix?
