Follow up, I see how it's working now. When I consume the MSM with InstallShield, it is placing Type 51 CA's in th= resulting MSI that aren't shown in the ISM project. This does an assign=ent to allow it to work.
I'm in a shop where we share MSM's with other vendors who are not using WiX= I'm trying to switch all of my IS MSM's over to WiX MSM's and then start=switching from IS to WiX for my installer. In this scenario, what is the best practice for describing folders like Com=onAppData in WXS merge modules and then consuming them in a WiX product pr=ject? At this point in time Fragments aren't a possibility except for ha=ing a fragment to describe a module and reference a fragment that contains=the implementation of the module with the intention of one day in the futu=e eliminating the module. Thanks, Chris Christopher Painter, Author of Deployment Engineering Blog Have a hot tip, know a secret or read a really good thread that deserves attention? E-Mail Me --- On Fri, 9/18/09, Christopher Painter <chr...@deploymentengineering.com> wrote: > From: Christopher Painter <chr...@deploymentengineering.com> > Subject: [WiX-users] Directory Table Question > To: wix-users@lists.sourceforge.net > Date: Friday, September 18, 2009, 9:03 AM > I thought I understood the Directory > table and costing pretty well but there's something that I > have working that I'm not sure why it's working. > > I have a WXS Merge Module snippet with: > > <Directory Id="CommonAppDataFolder"> > ... > </Directory> > > This results in a Merge Module and MSI with a Directory > table entry of: > > CommonAppDataFolder.GUID TARGETDIR . > > When I run the installer, my components go where I'd expect > them to be. I know that the Directory column can be a > property, but I'm trying to figure out how this is working > despite the modularization of the > property. Is there an obsecure SDK page > that I've missed? > > Thanks, > Chris > > > > > ------------------------------------------------------------------------------ > Come build with us! The BlackBerry® Developer > Conference in SF, CA > is the only developer event you need to attend this year. > Jumpstart your > developing skills, take BlackBerry mobile applications to > market and stay > ahead of the curve. Join us from November 9-12, 2009. > Register now! > http://p.sf.net/sfu/devconf > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > ------------------------------------------------------------------------------ Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
