On 5/1/10, wix-users-requ...@lists.sourceforge.net <
wix-users-requ...@lists.sourceforge.net> wrote:
>
> Send WiX-users mailing list submissions to
> wix-users@lists.sourceforge.net
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.sourceforge.net/lists/listinfo/wix-users
> or, via email, send a message with subject or body 'help' to
> wix-users-requ...@lists.sourceforge.net
>
> You can reach the person managing the list at
> wix-users-ow...@lists.sourceforge.net
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of WiX-users digest..."
>
>
> Today's Topics:
>
> 1. LGHT0048: The document element name "Wix" is invalid (wallywojo)
> 2. Re: LGHT0048: The document element name "Wix" is invalid
> (Jim Williams)
> 3. Re: LGHT0048: The document element name "Wix" is invalid
> (wallywojo)
> 4. Could WiX warn about this? (John Aldridge)
> 5. Re: Could WiX warn about this? (wallywojo)
> 6. Re: A new plan for WiX v3.5, introducing WiX v3.6
> (John H. Bergman (XPedient Technologies))
> 7. Double entries in Add/Remove programs (Wix Mailing List)
> 8. Re: Double entries in Add/Remove programs (wallywojo)
> 9. Re: Double entries in Add/Remove programs (Wix Mailing List)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Fri, 30 Apr 2010 10:18:54 -0700 (PDT)
> From: wallywojo <wallyw...@gmail.com>
> Subject: [WiX-users] LGHT0048: The document element name "Wix" is
> invalid
> To: wix-users@lists.sourceforge.net
> Message-ID: <1272647934936-4986792.p...@n2.nabble.com>
> Content-Type: text/plain; charset=us-ascii
>
>
> I searched and found a few matches with no replies. Can anyone assist when
> building with this
>
> E:\Users\<username>\Documents\WiX Projects\DSMail\DSMail>light -o "Mail
> Test.msi
> " -ext WixUIExtension Product.wixobj SecuritySettings.wxs
> EncryptionSettings.wxs
> DLHServerSettings.wxs DigitalSafeConfigSettings.wxs DigitalIDRef.wxs
> ConfigureEmailSearching.wxs ConfigureDefaultLanguage.wxs
>
> gives this:
> Microsoft (R) Windows Installer Xml Linker version 3.0.5419.0
> Copyright (C) Microsoft Corporation. All rights reserved.
>
> E:\Users\<username>\Documents\WiX Projects\Mail\Mail\SecuritySettings.wxs :
> er
> ror LGHT0048 : The document element name 'Wix' is invalid. A Windows
> Installer
> XML output file must use 'wixOutput' as the document element name.
>
> I try in VS with Votive and it causes VS to crash. Is there an issue with
> my
> environment or is something wrong within the SecuritySettings.wxs file?
>
> Thanks
> --
> View this message in context:
> http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/LGHT0048-The-document-element-name-Wix-is-invalid-tp4986792p4986792.html
> Sent from the wix-users mailing list archive at Nabble.com.
>
>
>
> ------------------------------
>
> Message: 2
> Date: Fri, 30 Apr 2010 10:29:31 -0700
> From: Jim Williams <jimwilliam...@comcast.net>
> Subject: Re: [WiX-users] LGHT0048: The document element name "Wix" is
> invalid
> To: "General discussion for Windows Installer XML toolset."
> <wix-users@lists.sourceforge.net>
> Cc: "wix-users@lists.sourceforge.net"
> <wix-users@lists.sourceforge.net>
> Message-ID: <dd96649a-8f3a-4185-88f3-3c0d4a7e1...@comcast.net>
> Content-Type: text/plain; charset=us-ascii;
> format=flowed; delsp=yes
>
> It looks like you are trying to link (light) WiX source files.
> Shouldn't you be using 'candle' to compile them first
>
> Jim Williams
>
> On Apr 30, 2010, at 10:18 AM, wallywojo <wallyw...@gmail.com> wrote:
>
> >
> > I searched and found a few matches with no replies. Can anyone
> > assist when
> > building with this
> >
> > E:\Users\<username>\Documents\WiX Projects\DSMail\DSMail>light -o
> > "Mail
> > Test.msi
> > " -ext WixUIExtension Product.wixobj SecuritySettings.wxs
> > EncryptionSettings.wxs
> > DLHServerSettings.wxs DigitalSafeConfigSettings.wxs DigitalIDRef.wxs
> > ConfigureEmailSearching.wxs ConfigureDefaultLanguage.wxs
> >
> > gives this:
> > Microsoft (R) Windows Installer Xml Linker version 3.0.5419.0
> > Copyright (C) Microsoft Corporation. All rights reserved.
> >
> > E:\Users\<username>\Documents\WiX Projects\Mail\Mail
> > \SecuritySettings.wxs :
> > er
> > ror LGHT0048 : The document element name 'Wix' is invalid. A Windows
> > Installer
> > XML output file must use 'wixOutput' as the document element name.
> >
> > I try in VS with Votive and it causes VS to crash. Is there an issue
> > with my
> > environment or is something wrong within the SecuritySettings.wxs
> > file?
> >
> > Thanks
> > --
> > View this message in context:
> http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/LGHT0048-The-document-element-name-Wix-is-invalid-tp4986792p4986792.html
> > Sent from the wix-users mailing list archive at Nabble.com.
> >
> > ---
> > ---
> > ---
> > ---------------------------------------------------------------------
> > _______________________________________________
> > WiX-users mailing list
> > WiX-users@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/wix-users
>
>
>
> ------------------------------
>
> Message: 3
> Date: Fri, 30 Apr 2010 10:36:06 -0700 (PDT)
> From: wallywojo <wallyw...@gmail.com>
> Subject: Re: [WiX-users] LGHT0048: The document element name "Wix" is
> invalid
> To: wix-users@lists.sourceforge.net
> Message-ID: <1272648966442-4986860.p...@n2.nabble.com>
> Content-Type: text/plain; charset=us-ascii
>
>
> thanks Jim, yeah missed a small step with my custom dialogs.
> --
> View this message in context:
> http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/LGHT0048-The-document-element-name-Wix-is-invalid-tp4986792p4986860.html
> Sent from the wix-users mailing list archive at Nabble.com.
>
>
>
> ------------------------------
>
> Message: 4
> Date: Fri, 30 Apr 2010 18:54:58 +0100
> From: John Aldridge <j...@jjdash.demon.co.uk>
> Subject: [WiX-users] Could WiX warn about this?
> To: "General discussion for Windows Installer XML toolset."
> <wix-users@lists.sourceforge.net>
> Message-ID: <4bdb1972.9080...@jjdash.demon.co.uk>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> I've just made a mistake like the following simplified example
>
> <Directory Id="SystemFolder">
> <Component Id="a32.dll" Guid="*" Win64="no">
> <File Id="a32.dll" Name="a.dll" Source="a32.dll" />
> </Component>
> </Directory>
>
> <Directory Id="System64Folder">
> <Component Id="a64.dll" Guid="*" Win64="yes">
> <File Id="a64.dll" Name="a.dll" Source="a64.dll" />
> </Component>
> </Directory>
>
> This is a 64 bit installer, which needs to install both the 32 and 64
> bit versions of a DLL in the respective system folders.
>
> This all works fine until I come to do an administrative installation,
> at which point both DLLs unpack to the same location, with one
> overwriting the other.
>
> I know (now!) that the solution is to give a Name attribute on the two
> Directory elements, e.g.
>
> <Directory Id="SystemFolder" Name="SystemFolder">
> :
> <Directory Id="System64Folder" Name="System64Folder">
> :
>
> but would it be possible for WiX to warn me if I do something stupid
> like this?
>
> --
> Cheers,
> John
>
>
>
> ------------------------------
>
> Message: 5
> Date: Fri, 30 Apr 2010 11:02:00 -0700 (PDT)
> From: wallywojo <wallyw...@gmail.com>
> Subject: Re: [WiX-users] Could WiX warn about this?
> To: wix-users@lists.sourceforge.net
> Message-ID: <1272650520423-4986987.p...@n2.nabble.com>
> Content-Type: text/plain; charset=us-ascii
>
>
> may not need anything additional, I am pretty sure that a Full MSI
> validation
> would report this. Have you tried to validate the built MSI?
> --
> View this message in context:
> http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Could-WiX-warn-about-this-tp4986969p4986987.html
> Sent from the wix-users mailing list archive at Nabble.com.
>
>
>
> ------------------------------
>
> Message: 6
> Date: Fri, 30 Apr 2010 13:04:40 -0500
> From: "John H. Bergman (XPedient Technologies)"
> <john.berg...@xpedienttechnologies.com>
> Subject: Re: [WiX-users] A new plan for WiX v3.5, introducing WiX v3.6
> To: General discussion for Windows Installer XML toolset.
> <wix-users@lists.sourceforge.net>
> Message-ID:
> <
> 662d897a878fb4499a4c067a86693d210114f4199...@exchange.xpedienttechnologies.com
> >
>
> Content-Type: text/plain; charset="us-ascii"
>
> This seems like a good and sound plan. Will 3.5 be moved over to codeplex
> as well (or updated so the source build from a version control repository)?
>
> -----Original Message-----
> From: Rob Mensching [mailto:r...@robmensching.com]
> Sent: Wednesday, April 28, 2010 11:07 PM
> To: General discussion for Windows Installer XML toolset.
> Subject: [WiX-users] A new plan for WiX v3.5, introducing WiX v3.6
>
> I just posted a blog entry about changes to the WiX v3.5 plan:
> http://robmensching.com/blog/posts/2010/4/28/Change-of-plans-for-WiX-v3.5.
>
> This plan is based on feedback sent here (and other places) about getting a
> stable WiX toolset that supports Visual Studio 2010. It pains me to bump
> Burn again but the simple fact is Burn isn't going to be ready soon.
>
> I also want to point out the plan to drop Visual Studio 2005 support
> from*WiX v3.6 *. We aren't fixing bugs in Votive for VS2005 any more and I
> know there were some big problems left. It seems that people have all moved
> to VS2008 and now VS2010.
>
> As always, feedback is welcome.
>
> --
> virtually, Rob Mensching - http://RobMensching.com LLC
>
> ------------------------------------------------------------------------------
> _______________________________________________
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
>
>
> ------------------------------
>
> Message: 7
> Date: Fri, 30 Apr 2010 11:13:47 -0700
> From: "Wix Mailing List" <w...@danhinsley.com>
> Subject: [WiX-users] Double entries in Add/Remove programs
> To: <wix-users@lists.sourceforge.net>
> Message-ID: <003401cae890$e159e4e0$a40dae...@com>
> Content-Type: text/plain; charset="us-ascii"
>
> I looked at the thread in the archive, but it appears that this person
> didn't resolve his issue (or at least didn't post when he did). Here's
> what
> I've got:
>
>
>
> <Product Id="*" Name="Myrna" Language="1033"
>
> Version="0.01.0" Manufacturer="No Bull Software"
> UpgradeCode="{BF762230-9947-44b7-AC28-602088490E13}">
>
> <Package Id ="*" InstallerVersion="300" Compressed="yes" />
>
> <Media Id="1" Cabinet="media1.cab" EmbedCab="yes" />
>
>
>
> <Upgrade Id="{A8C90E5E-814A-4bae-B5BB-6DD2A363DB69}">
>
> <UpgradeVersion Property="OLDERVERSIONBEINGUPGRADED" Minimum="0.0.0"
> Maximum="0.01.0" IncludeMaximum="no" />
>
> <UpgradeVersion Property="NEWERVERSIONDETECTED" Minimum="0.01.0"
> OnlyDetect="yes" IncludeMinimum="yes" />
>
> </Upgrade>
>
> <Condition Message="A later version of [ProductName] is already
> installed. Install will now exit.">
>
> <![CDATA[Installed OR NOT NEWERVERSIONDETECTED]]>
>
> </Condition>
>
>
>
> ..
>
>
>
> <InstallExecuteSequence>
>
> <RemoveExistingProducts After="InstallExecute" />
>
> </InstallExecuteSequence>
>
>
>
> The InstallExecuteSequence if after the <Feature> list if that matters.
>
>
>
> I install as above, everything works as it should. Then I change
> Product/@Version, UpgradeVersion(OLDER.)/@Maximum and
> UpgradeVersion(NEWER.)/@Minimum all to 0.02.0.
>
>
>
> I install again, it installs and I have two entries in the Add/Remove
> table,
> one for version 0.01.0 and one for 0.02.0.
>
>
>
> In the log for FindRelatedProducts I find:
>
>
>
> MSI (c) (E0:BC) [11:09:30:281]: Doing action: FindRelatedProducts
>
> MSI (c) (E0:BC) [11:09:30:281]: Note: 1: 2205 2: 3: ActionText
>
> Action 11:09:30: FindRelatedProducts. Searching for related applications
>
> Action start 11:09:30: FindRelatedProducts.
>
> Action ended 11:09:30: FindRelatedProducts. Return value 1.
>
>
>
> MSI (s) (9C:6C) [11:09:50:357]: Doing action: FindRelatedProducts
>
> MSI (s) (9C:6C) [11:09:50:357]: Note: 1: 2205 2: 3: ActionText
>
> Action 11:09:50: FindRelatedProducts. Searching for related applications
>
> Action start 11:09:50: FindRelatedProducts.
>
> MSI (s) (9C:6C) [11:09:50:357]: Skipping FindRelatedProducts action:
> already
> done on client side
>
> Action ended 11:09:50: FindRelatedProducts. Return value 0.
>
>
>
> Which, given the other thread leads me to believe that FindRelatedProducts
> isn't finding the prior install, but I can't for the life of me figure out
> why. Can anyone point me in the right direction here?
>
>
>
> Thanks
>
>
>
> Dan
>
>
>
>
>
> ------------------------------
>
> Message: 8
> Date: Fri, 30 Apr 2010 11:24:37 -0700 (PDT)
> From: wallywojo <wallyw...@gmail.com>
> Subject: Re: [WiX-users] Double entries in Add/Remove programs
> To: wix-users@lists.sourceforge.net
> Message-ID: <1272651877466-4987090.p...@n2.nabble.com>
> Content-Type: text/plain; charset=us-ascii
>
>
> Hi Dan to point out here that might get you in the right direction. If you
> are trying a launch condition based on a product lookup you cannot use
> FindRelatedProducts since that happens after the LaunchConditions action.
> --
> View this message in context:
> http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Double-entries-in-Add-Remove-programs-tp4987063p4987090.html
> Sent from the wix-users mailing list archive at Nabble.com.
>
>
>
> ------------------------------
>
> Message: 9
> Date: Fri, 30 Apr 2010 11:43:06 -0700
> From: "Wix Mailing List" <w...@danhinsley.com>
> Subject: Re: [WiX-users] Double entries in Add/Remove programs
> To: "'General discussion for Windows Installer XML toolset.'"
> <wix-users@lists.sourceforge.net>
> Message-ID: <004101cae894$f9679740$ec36c5...@com>
> Content-Type: text/plain; charset="us-ascii"
>
> I was just using the example in the help file. I don't call
> FindRelatedProducts directly, I'm assuming it gets called before the
> Upgrade
> actions do. If not, how does one go about doing this?
>
> -----Original Message-----
> From: wallywojo [mailto:wallyw...@gmail.com]
> Sent: Friday, April 30, 2010 11:25 AM
> To: wix-users@lists.sourceforge.net
> Subject: Re: [WiX-users] Double entries in Add/Remove programs
>
>
> Hi Dan to point out here that might get you in the right direction. If you
> are trying a launch condition based on a product lookup you cannot use
> FindRelatedProducts since that happens after the LaunchConditions action.
> --
> View this message in context:
>
> http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Double-entries
> -in-Add-Remove-programs-tp4987063p4987090.html
> Sent from the wix-users mailing list archive at Nabble.com.
>
>
> ----------------------------------------------------------------------------
> --
> _______________________________________________
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
>
>
>
> ------------------------------
>
>
> ------------------------------------------------------------------------------
>
>
> ------------------------------
>
> _______________________________________________
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
>
> End of WiX-users Digest, Vol 47, Issue 131
> ******************************************
>
------------------------------------------------------------------------------
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
