I need to know what the best process is to upgrade an applications dependency.
I have Application X the is installed on 1000 odd workstations and has a dependency on application y.
Now application Y need an upgrade to Y.1 resolve an issue. The upgrade process requires Y.1 to uninstall Y to complete successfully and I want to do this on a phased deployment process as the application is critical.
So I configure application Y.1 to supersede and uninstall application Y in SCCM 2012 seems simple enough.
Now I install Application X with the original dependency Y but when I attempt to deploy Y.1 to the workstation I get an error deploying due to the upgrade Y.1 conflicting with Y.
When I try modifying the dependencies for Application X to require Y OR Y.1 but only Y is set to auto install Application X will now not install due to not meeting requirements.
The only ways I can think now of actually completing the deployment is breaking the dependency chain altogether and deploying the application that way OR not using the supersedence process and scripting the upgrade (uninstall\install) however I expect that would then break the previous version so I would have to modify the detection method of Y to include the new version Y.1 detection method.
Please tell me I am overanalysing this and there is something simple I have missed!!
David