Are the shortcuts advertised or not? The behavior of CreateShortCuts is different in the advertised/non-advertised cases. If the shortcut is advertised it's basically a pointer to the keypath of the component, and that will result in a call to MsiProvideComponent () if it's used. It's not advertised it's just a pointer to the file.
I guess it's possible that an advertised shortcut that results in a call to MsiProvideComponent () might get a bit hairy if it goes off to verify the component and the feature and finds something not quite installed yet. None of the SxS things will be correct yet, whether they are GAC or some C++ runtime things. --------------- Phil Wilson On Fri, Oct 10, 2014 at 1:13 PM, TimM <timmay...@smarttech.com> wrote: > Yes that is basically what InstallShield is doing and again the only reason > that we are still supporting this is that we still have administrators that > push out our software by .msi only and therefore we had to support a multi > .msi package so that they only had to push out a single .msi file instead of > multiple packages. Some of our packages contain up to 30 .msi projects and > therefore pushing one .msi is preferable. > > Now we are starting to get our admin customers to switch over to our Wrapper > .exe packages that have full support for admin silent pushes and supports > our full range of properties, but we have not fully got that transition in > place and therefore have to continue to support the chain .msi projects. > > So yes it could be that the assembly registration transaction could be > causing the issue if CreateShortcuts happens way before this, but then just > a single .msi has the same issue where CreateShortcuts occurs before > MsiPublishAssemblies and therefore it is not only the Chain that we have > seen this issue. > > So I know that CreateShortcuts is msi Microsoft action, but what does it do > that makes sxs get triggered. Does the creation of the shortcut access the > .exe in someway that is triggering a sxs error because the assemblies have > not been registered yet? > > Again it is not a big issue as after install all apps work as expected, it > is only when there are issues and when we ask the customers for logs and > what not we see these sxs errors and it just does not look good and the > install gets blamed for a lot of issues, some of which like these ones we > can not do anything about. At least not that we have found... > > > > > > -- > View this message in context: > http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Shortcut-creation-seems-to-cause-sxs-assembly-error-in-Event-Viewer-tp7589133p7597237.html > Sent from the wix-users mailing list archive at Nabble.com. > > ------------------------------------------------------------------------------ > 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
