Isolation for an Excel AddIn ?
I'm currently working on a package for a customer which deploys an Excel AddIn to the XLSTART folder. The repackage snapshot picked up two additional OCX files being deployed to the System32 folder, namely COMCTL32.OCX and COMDLG32.OCX both of which are newer versions than those already present in the customer's base build.
Ordinarily I would look to deploy these files using merge module(s), however the customer's packaging standards dictate that merge modules should not be used and instead .local isolation should be employed instead.
My question is therefore, in the absence of an actual executable in the package, is it possible to use .local isolation to force the addin to use isolated copies of these newer OCX files, and if not, are there any other options open ?