> From: wix-users-requ...@lists.sourceforge.net
> Subject: WiX-users Digest, Vol 89, Issue 117
> To: wix-users@lists.sourceforge.net
> Date: Tue, 29 Oct 2013 21:17:36 +0000
>
> 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. Re: trying to restart explorer with restartresource
> (victorwhiskey)
> 2. Re: trying to restart explorer with restartresource
> (Nicol?s Alvarez)
> 3. Re: Purely WiX patching and FeatureRef (Tunney, Stephen)
> 4. Re: Creating multiple Minor Updates (TimM)
> 5. Re: Possible bug in 3.8 (Rob Mensching)
> 6. Re: trying to restart explorer with restartresource
> (victorwhiskey)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Tue, 29 Oct 2013 11:04:05 -0700 (PDT)
> From: victorwhiskey <victorhwhis...@yahoo.com>
> Subject: Re: [WiX-users] trying to restart explorer with
> restartresource
> To: wix-users@lists.sourceforge.net
> Message-ID: <1383069845363-7590096.p...@n2.nabble.com>
> Content-Type: text/plain; charset=us-ascii
>
> c:\windows
>
>
>
> --
> View this message in context:
> http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/trying-to-restart-explorer-with-restartresource-tp7590046p7590096.html
> Sent from the wix-users mailing list archive at Nabble.com.
>
>
>
> ------------------------------
>
> Message: 2
> Date: Tue, 29 Oct 2013 16:15:46 -0200
> From: Nicol?s Alvarez <nicolas.alva...@gmail.com>
> Subject: Re: [WiX-users] trying to restart explorer with
> restartresource
> To: "General discussion about the WiX toolset."
> <wix-users@lists.sourceforge.net>
> Message-ID:
> <canpc-tvv8j2iu-npbq60s_c5eszad3hri-gnwwq3ao-nves...@mail.gmail.com>
> Content-Type: text/plain; charset=UTF-8
>
> 2013/10/28 victorwhiskey <victorhwhis...@yahoo.com>:
> > <util:RestartResource Id="restart_Explorer"
> > Path="[EXPLORERPATH]"
> > ProcessName="explorer.exe"/>
> >
> > <Property Id="EXPLOREPATH" >
> > <DirectorySearch Id="FindExplorerDir"
> > AssignToProperty="no"
> > Depth="0"
> > Path="[WindowsFolder]">
> > <FileSearch Id="FindExplorer"
> > Name="explorer.exe" />
> > </DirectorySearch>
> > </Property>
>
> You have a typo there. You're creating a property called EXPLOREPATH
> (missing R) and then using [EXPLORERPATH].
>
> --
> Nicol?s
>
>
>
> ------------------------------
>
> Message: 3
> Date: Tue, 29 Oct 2013 18:36:51 +0000
> From: "Tunney, Stephen" <stephen.tun...@nuance.com>
> Subject: Re: [WiX-users] Purely WiX patching and FeatureRef
> To: General discussion about the WiX toolset.
> <wix-users@lists.sourceforge.net>
> Message-ID:
> <ded4d0ad537f9f4f9a4c5cabefe869433986c...@som-exch02.nuance.com>
> Content-Type: text/plain; charset="us-ascii"
>
> More information, Bob :)
>
> The wixmst file is complaining that it cannot find certain files and is
> displaying the path from the RTM.wixpdb.
>
> I see in the wixmst file the following values in their respective fields
> /field/@unresolvedPreviousData node contains the *incorrect* path (RTM.wixpdb
> value)
> /field/@previousData node contains the *correct* path (Latest.wixpdb value)
> /field/@unresolvedData node contains the *correct* path (Latest.wixpdb value)
>
> Thoughts? Would you like me to send you the wixmst file?
>
> -----Original Message-----
> From: Tunney, Stephen [mailto:stephen.tun...@nuance.com]
> Sent: October-29-13 12:51 PM
> To: General discussion about the WiX toolset.
> Subject: Re: [WiX-users] Purely WiX patching and FeatureRef
>
> Hey Bob,
>
> Thank you for your feedback, perhaps you could assist me with my problem
> then. It appears as though my work with Melt and Torch is ignoring me :(
>
> Here is a link to the batch file I'm using:
> http://pastebin.com/kMfbSNcv
>
> http://pastebin.com/Xa08mufQ
>
> Thanks for looking, I can attach the wixmst and wixpdbs if you'd like.
>
> Stephen
>
> -----Original Message-----
> From: Bob Arnson [mailto:b...@joyofsetup.com]
> Sent: October-28-13 11:18 PM
> To: wix-users@lists.sourceforge.net
> Subject: Re: [WiX-users] Purely WiX patching and FeatureRef
>
> I would choose "none of the above." :) The primary reason to use filtering is
> when you're choosing files individually, based on what you know about changes
> made to the product. Otherwise, use no filtering to get the default automatic
> behavior. I'm not aware of any problems using Melt and automatic filtering.
> You can check the .wixpdbs that Melt produces to make sure the paths are
> correct.
>
> On 28-Oct-13 22:05, Tunney, Stephen wrote:
> > Ok, good to know. I have thousands of components though spread across
> > a dozen features. Those features are shared amongst 8 products :)
> >
> > When I originally developed the Products I thought I was being clever by
> > logically grouping certain ComponentRefs into component groups, and those
> > groups would be referenced elsewhere in other componentgroups and features
> > depending on the product requiring them. This made for nice short feature
> > definitions.
> >
> > I might also add that we have a dozen wixlib projects all used to
> > encapsulate high-level services and their required actions.
> > Also, we have a large number of DLLs that are simple extensions based
> > on language
> >
> > Mydll.en-us.dll
> > Mydll.fr-fr.dll
> >
> > These are created as components using pre-processor for loops. This will
> > likely hurt us now.
> >
> >
> > How should I go about solving this problem? I've got three choices
> > here
> > 1) Manually maintain two lists of ComponentRefs a)installer b)patch
> > 2) Use some fancy .WXI include magic and keep my component groups but
> > have them just <?include?> the componentrefs from another file that is
> > shared with the patchfamily
> > 3) Write a custom parser (msi tables or wixlib file) that
> > auto-generates the componentref list for a feature on the fly
> >
> > Bob, do you have any insight into what my next move should be? This is a
> > very complicated set of products.
> >
> > Thanks for everything so far! WiX rocks!! :)
> >
> > -----Original Message-----
> > From: Bob Arnson [mailto:b...@joyofsetup.com]
> > Sent: October-28-13 9:37 PM
> > To: wix-users@lists.sourceforge.net
> > Subject: Re: [WiX-users] Purely WiX patching and FeatureRef
> >
> > On 28-Oct-13 20:38, Tunney, Stephen wrote:
> >> Adding DirectoryRef to the same boat as FeatureRef. I've added all
> >> directoryRefs, including the one that includes the component that I
> >> know has been updated and still no dice. :(
> > When used in patch family filtering, only a ComponentRef will include a
> > component. FeatureRef and DirectoryRef only include the specific thing
> > referenced, not any of their children.
> >
> > --
> > sig://boB
> > http://joyofsetup.com/
> >
> >
> > ----------------------------------------------------------------------
> > -------- Android is increasing in popularity, but the open development
> > platform that developers love is also attractive to malware creators.
> > Download this white paper to learn more about secure code signing
> > practices that can help keep Android apps secure.
> > http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.c
> > lktrk _______________________________________________
> > WiX-users mailing list
> > WiX-users@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/wix-users
> >
> > ----------------------------------------------------------------------
> > -------- Android is increasing in popularity, but the open development
> > platform that developers love is also attractive to malware creators.
> > Download this white paper to learn more about secure code signing
> > practices that can help keep Android apps secure.
> > http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.c
> > lktrk _______________________________________________
> > WiX-users mailing list
> > WiX-users@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/wix-users
> >
>
> --
> sig://boB
> http://joyofsetup.com/
>
>
> ------------------------------------------------------------------------------
> Android is increasing in popularity, but the open development platform that
> developers love is also attractive to malware creators. Download this white
> paper to learn more about secure code signing practices that can help keep
> Android apps secure.
> http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk
> _______________________________________________
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
> ------------------------------------------------------------------------------
> Android is increasing in popularity, but the open development platform that
> developers love is also attractive to malware creators. Download this white
> paper to learn more about secure code signing practices that can help keep
> Android apps secure.
> http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk
> _______________________________________________
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
>
>
> ------------------------------
>
> Message: 4
> Date: Tue, 29 Oct 2013 11:55:17 -0700 (PDT)
> From: TimM <timmay...@smarttech.com>
> Subject: Re: [WiX-users] Creating multiple Minor Updates
> To: wix-users@lists.sourceforge.net
> Message-ID: <1383072917407-7590098.p...@n2.nabble.com>
> Content-Type: text/plain; charset=us-ascii
>
> Joe, we are just looking at patches and I have a question about this method
> if you don't mind?
>
> I am just testing out with using the sample 'Using Pure WiX' example and I
> am looking at the PatchFamily element and noticed that you have to add a
> reference to a component in your main install project. And then you
> mentioned that you added a new file so in the 2nd patch added the reference
> to the new component.
>
> So my question is do you have to add a reference to all components that
> changed or do you simply have to add a reference to any component that
> resides in your target project and then the patch will pick up all
> changed/updated components?
>
> The reason I ask is because in doing the example the sample.txt file updated
> fine, so I added some .exe files to the sample target and update projects,
> some that changed and some that did not and I left the ComponentRef in the
> patch.wxs to still be the same. Did not add any more references. I then
> built the patch and when I ran it over the target install it correctly
> upgraded all files that were updated and left all the ones that were the
> same as is. So it seems to work that way. So was that just a side effect and
> it was not suppose to do that or is that how it is supposed to work?
>
> I have not tried to create a cumulative patch from this example, but if it
> does work this way then for a 2nd and 3rd patch would you have to add more
> component references or simply build the cumulative patch and it would only
> be new components that you would have to add as references?
>
> Oh and that does bring up the question on how you built the cumulative
> patch? what command line do you use to build with to generate the patch to
> work over 1 and ver 2, and so on?
>
> Thanks for any insight that you can supply.
>
>
>
> --
> View this message in context:
> http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Creating-multiple-Minor-Updates-tp7586073p7590098.html
> Sent from the wix-users mailing list archive at Nabble.com.
>
>
>
> ------------------------------
>
> Message: 5
> Date: Tue, 29 Oct 2013 20:19:26 +0000
> From: Rob Mensching <r...@robmensching.com>
> Subject: Re: [WiX-users] Possible bug in 3.8
> To: General discussion about the WiX toolset.
> <wix-users@lists.sourceforge.net>
> Message-ID:
>
> <99bd1e49a4a6482fb991d9cbe3833...@bn1pr07mb181.namprd07.prod.outlook.com>
>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Go here to get your activation email again: http://wixtoolset.org/issues/user
>
> The page that indicated the token expired should have had a link to get a new
> token.
>
> There was an issue with the mail server this morning being incredibly slow.
>
> -----Original Message-----
> From: Thomas Due [mailto:t...@scanvaegt.dk]
> Sent: Tuesday, October 29, 2013 4:25 AM
> To: wix-users@lists.sourceforge.net
> Subject: [WiX-users] Possible bug in 3.8
>
> Hello,
>
> I have tried the entire morning to register for the issue tracker on
> wixtoolset.org/issues, but the activation email is so long arriving, that the
> link has expired, so now I post here instead.
>
> I have recently upgraded to 3.8 in order to get support for VS2013. Now I
> just attempted to recompile my installer and got this error:
>
> Failed to open the database. During validation, this most commonly
> happens when attempting to open a
> database using an unsupported code page or a file that is not a valid
> Windows Installer database. Please
> use a different code page in Module/@Codepage, Package/@SummaryCodepage,
> Product/@Codepage, or
> WixLocalization/@Codepage; or make sure you provide the path to a valid
> Windows Installer database.
>
> Nothing has changed in the project. The only difference is the WiX version.
>
> The project compiles fine on the build server (WiX 3.5), but now I have the
> exact same issue with 3.7. I uninstalled 3.8 and installed 3.7, without
> restarting or anything.
>
>
> Med venlig hilsen / Best regards,
> Thomas Due ?- Software Developer
> Tel: +45 8678 5500 Fax: +45 8678 5210
> Johann Gutenbergs vej 5-9, Aarhus N, Denmark t...@scanvaegt.dk |
> www.scanvaegt.dk
>
>
> This e-mail and its attachments are intended for the named addressee only and
> may contain information that is confidential and privileged. Unauthorized use
> can instigate a claim for damages and constitute a criminal offence. If you
> received this in error, please contact the sender and delete the material.
>
>
> > -----Original Message-----
> > From: wix-users-requ...@lists.sourceforge.net [mailto:wix-users-
> > requ...@lists.sourceforge.net]
> > Sent: 29. oktober 2013 11:52
> > To: wix-users@lists.sourceforge.net
> > Subject: WiX-users Digest, Vol 89, Issue 114
> >
> > 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..."
>
>
> ------------------------------------------------------------------------------
> Android is increasing in popularity, but the open development platform that
> developers love is also attractive to malware creators. Download this white
> paper to learn more about secure code signing practices that can help keep
> Android apps secure.
> http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk
> _______________________________________________
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
>
>
>
> ------------------------------
>
> Message: 6
> Date: Tue, 29 Oct 2013 14:17:28 -0700 (PDT)
> From: victorwhiskey <victorhwhis...@yahoo.com>
> Subject: Re: [WiX-users] trying to restart explorer with
> restartresource
> To: wix-users@lists.sourceforge.net
> Message-ID: <1383081448315-7590100.p...@n2.nabble.com>
> Content-Type: text/plain; charset=us-ascii
>
> Ah crap. So much for not being lazy and trying to type things out...
>
> Thanks so much!
>
>
>
> --
> View this message in context:
> http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/trying-to-restart-explorer-with-restartresource-tp7590046p7590100.html
> Sent from the wix-users mailing list archive at Nabble.com.
>
>
>
> ------------------------------
>
> ------------------------------------------------------------------------------
> Android is increasing in popularity, but the open development platform that
> developers love is also attractive to malware creators. Download this white
> paper to learn more about secure code signing practices that can help keep
> Android apps secure.
> http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk
>
> ------------------------------
>
> _______________________________________________
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
>
> End of WiX-users Digest, Vol 89, Issue 117
> ******************************************
------------------------------------------------------------------------------
Android is increasing in popularity, but the open development platform that
developers love is also attractive to malware creators. Download this white
paper to learn more about secure code signing practices that can help keep
Android apps secure.
http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
