Hi Ron,
Why not just mock the classes and have the mock classes take the
appropriate actions when they are called by mistake.
To clarify my earlier comments: I like your solution here, and agree that
it would work well in this circumstance. It gives more control than my
suggestion to catch
The plugin page Upgrading at runtime mentions 5.8 is the default but that
upgrading to the latest should be possible. Does this take into account the
6.x releases?
Either way may be prudent to add a declaration to this page to avoid others
wondering the same question.
Thanks,
James
On 5
On 06/02/2015 6:32 AM, Curtis Rueden wrote:
Hi Ron,
Why not just mock the classes and have the mock classes take the
appropriate actions when they are called by mistake.
To clarify my earlier comments: I like your solution here, and agree that
it would work well in this circumstance. It gives
