An InstallShield chain of MSIs is the "single transaction" install, the multi-package transaction where the whole transaction of multiple MSIs isn't committed until the end. That seems to include committing assemblies into the GAC, that's not MsiPublishAssemblies as much as the Fusion API not doing the commit until InstallFinalize. That's the context, I assume, and it looks like some things in the install aren't working until that final MSI Commit at the end of the transaction. --------------- Phil Wilson
On Fri, Oct 10, 2014 at 11:14 AM, Rob Mensching <r...@firegiant.com> wrote: > I'm curious. What is a "suite admin installer .msi"? An MSI that installs a > bunch of MSIs? Is this using EmbeddedUI? Maybe I'm just confused. > > I also couldn't parse this: " Since Wix does not support an admin chain > install that creates a output .msi we are using InstallShield to create our > chain installs to chain all out wix install projects." Bundles certainly can > chain together MSIs that require admin elevation. Is the issue here that > you'd want your BA to be elevated as well? > > _____________________________________________________________ > Short replies here. Complete answers over there: http://www.firegiant.com/ > > > > -----Original Message----- > From: TimM [mailto:timmay...@smarttech.com] > Sent: Friday, October 10, 2014 11:00 AM > To: wix-users@lists.sourceforge.net > Subject: Re: [WiX-users] Shortcut creation seems to cause sxs assembly error > in Event Viewer > > No we are not doing nested installs. Since Wix does not support an admin > chain install that creates a output .msi we are using InstallShield to create > our chain installs to chain all out wix install projects. > > We have quite a few wixlib 32 bit assemblies that we create to that gets > installed and are required for a lot of out main products that we install, > either standalone or chained into a suite admin installer .msi. > > The wixlib's use the File Id - Assembly="win32" and AssemblyManifest elements > so that they are correctly registered as assemblies on the machines in the > GAC. > > As for the shortcuts we have them defined as following: > <Shortcut Id="StartMenu_NB_Shortcut" Directory="SMARTIconFolder" > Target="[INSTALLDIR]Notebook.exe" Name="SMART Notebook 14" > Icon="NB_ARP_Icon" Show="normal" WorkingDirectory="INSTALLDIR" /> > > Where Icon=NB_ARP_Icon is the Icon Id to the source .ico file. > > So when you say you use resource only native DLL are you referring to a dll > that contains all your icon resources and you just point to the correct > IconIndex? We used sort of do that, but we just pointed to the main .exe file > and the correct IconIndex, but we found out that this duplicates the .exe in > the installer for resources and therefore increased the sizes of our > installers quite a bit, especially if the .exe files were large.... > > > > ------------------------------------------------------------------------------ > Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer > Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports > Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper > Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer > http://p.sf.net/sfu/Zoho > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://p.sf.net/sfu/Zoho _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
