DSC Linked App-V Sequences - Last Launching Registry 'Wins'?
I have an App-V package for Oracle 8i Client, which has some registry settings contained it in under 'HKLM\Software\Oracle\Home2'.
I then created a sequence for a software title (let's call it Application X, it's a custom app for the client) that has a dependency on the Oracle client, that also has some different, additional keys under 'HKLM\Software\Oracle\Home2' within the package, that are specific to that application.
The Application X has a mandatory dependency in its OSD for the Oracle Client package, but when launching Application X I am only seeing the registry settings under 'HKLM\Software\Oracle\Home2' from the Oracle client package, and not the additional settings in Application X.
I'm using Microsoft App-V sequencer 4.6 (not with SP1), and I'm viewing the registry by running sfttray with an alternative executable to gain access to the 'bubbled' registry. If I remove the DSC link then the registry settings in Application X are all present and correct.
I've read the following post and related links http://www.appvirtguru.com/viewtopic.php?f=9&t=3715 and they appear to say that the last launching sequence, in this case the Oracle 8i sequence as it's DSC linked to the main application, Application X, 'wins' in terms of which registy keys are present.
Can anyone confirm if that is correct?
And if so how I can approach this without modifying the Oracle 8i sequence, as it is currently 'live' with many other applications also linked to it.
A post launch script to push the registry settings in after Application X has launched, and invoked the Oracle 8i dependent application worked correctly. Checked by using sfttray with an alternative executable to confirm the registry settings exist.