We have been running into a lot of type problems during our upgrade when trying to develop custom tasks and plugins for XLR. The issue seems to be when we have an existing or archived releases using this custom task and then we attempt to modify it the existing releases will fail if there is a property or field mismatch.
So, I was wondering what others are doing to mitigate this. It would be painful to go through existing releases and remove these tasks. We love the extensibility of XLR but we keep getting caught by dead or new types that put us into catch 22 situations.
Any ideas, are we alone?
Thanks all for any input!