[WiX-users] Issues faced while upgrading from Wix 3.5 to Wix 3.8
Hi, For our project we used to create a bootstrapper installer with WiX 3.5. It included the .NetFramework 4.0 and our ProjectMSI. The product version used for this installer was 1.0.1.0. Now we have upgraded WiX to 3.8. The next product version used is 1.0.2.0. The product version for the Bundle and ProjectMSI are same. The product Id and upgrade code for ProjectMSI are the same as that used in 1.0.1.0. The Upgrade code for Bundle is different. Upgrade is allowed but Downgrade is not allowed for the product. We are facing the following issues: 1. If we have 1.0.1.0 (that was created with Wix 3.5) installed on a machine and we try to install 1.0.2.0 with setup.exe (that was created with Wix 3.8) then the control panel shows a single entry for the product with version 1.0.2.0 but when we check the version of the DLLs it shows 1.0.1.0. 2. Before creating the deployment builds we always create an engineering build with version 1.0.0.0. If we have 1.0.1.0 (that was created with Wix 3.5) installed on a machine and we try to install 1.0.0.0 with setup.exe (that was created with Wix 3.8) then the control panel shows two entries for the product - one for 1.0.1.0 and another for 1.0.0.0. However in both the cases if we try to run the ProjectMSI directly (setup.msi) it says Another version of this product is already installed... which is the expected behaviour. How can we get the same behaviour for bootstrapper setup.exe created with Wix 3.8. Thanks Regards, -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Issues-faced-while-upgrading-from-Wix-3-5-to-Wix-3-8-tp7596511.html Sent from the wix-users mailing list archive at Nabble.com. -- Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Options for pausing the download and installation in wix custom BootStrapper
Hi, I have a wix custom Bootstrapper application which will download and install more than two msi in a client machine. Is there any option for me to pause the download process if internet is disconnected. If disconnected the application retries 3 times for re connection, if failed again it starts rollback. If so, is there any ways to pause the download before rollback starts. Please share the kind ideas. Regards, Balaji R. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Options-for-pausing-the-download-and-installation-in-wix-custom-BootStrapper-tp7596512.html Sent from the wix-users mailing list archive at Nabble.com. -- Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] SourceProperty of CopyFile-element changed after execution
Hello,
I have following CopyFile element in my Product.wxs:
CopyFile Id=myId DestinationDirectory=MY_DIR DestinationName=MY_NAME.xml
SourceProperty=MY_SOURCE /
My bootstrapper application passes the MY_SOURCE property in to the msi-file.
The value of MY_SOURCE is C:\someDir\someFile.txt.
It includes the filename and extension!
Some CA that executes after CreateFiles uses the property:
if (!File.Exists(session[MY_SOURCE]))
{
session.log(string.format(File {0} does not exist, session[MY_SOURCE]));
}
the log is:
File C:\someDir\someFile.txt\ does not exist
MY_SOURCE changed from C:\someDir\someFile.txt to C:\someDir\someFile.txt\
Why?
Btw, if I use a local property it works:
SetProperty Id=copyMy_Source Value=[My_SOURCE] Sequence=execute
After=CostFinalize /
...
CopyFile Id=myId DestinationDirectory=MY_DIR DestinationName=MY_NAME.xml
SourceProperty=copyMy_SOURCE /
log:
MSI (s) (50:84) [15:12:15:224]: PROPERTY CHANGE: Adding copyMy_Source property.
Its value is 'C:\someDir\someFile.txt'.
and this is also my workaround for now.
--
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] SourceProperty of CopyFile-element changed after execution
MY_SOURCE in the Directory table?
___
FireGiant | Dedicated support for the WiX toolset |
http://www.firegiant.com/
-Original Message-
From: Ingo Fischer [mailto:ingoderfisc...@hotmail.com]
Sent: Monday, August 25, 2014 6:31 AM
To: General discussion about the WiX toolset.
Subject: [WiX-users] SourceProperty of CopyFile-element changed after execution
Hello,
I have following CopyFile element in my Product.wxs:
CopyFile Id=myId DestinationDirectory=MY_DIR DestinationName=MY_NAME.xml
SourceProperty=MY_SOURCE /
My bootstrapper application passes the MY_SOURCE property in to the msi-file.
The value of MY_SOURCE is C:\someDir\someFile.txt.
It includes the filename and extension!
Some CA that executes after CreateFiles uses the property:
if (!File.Exists(session[MY_SOURCE]))
{
session.log(string.format(File {0} does not exist, session[MY_SOURCE])); }
the log is:
File C:\someDir\someFile.txt\ does not exist
MY_SOURCE changed from C:\someDir\someFile.txt to C:\someDir\someFile.txt\
Why?
Btw, if I use a local property it works:
SetProperty Id=copyMy_Source Value=[My_SOURCE] Sequence=execute
After=CostFinalize / ...
CopyFile Id=myId DestinationDirectory=MY_DIR DestinationName=MY_NAME.xml
SourceProperty=copyMy_SOURCE /
log:
MSI (s) (50:84) [15:12:15:224]: PROPERTY CHANGE: Adding copyMy_Source property.
Its value is 'C:\someDir\someFile.txt'.
and this is also my workaround for now.
--
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Options for pausing the download and installation in wix custom BootStrapper
Yes. ___ FireGiant | Dedicated support for the WiX toolset | http://www.firegiant.com/ -Original Message- From: Balaji R [mailto:ji4all...@gmail.com] Sent: Monday, August 25, 2014 5:53 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Options for pausing the download and installation in wix custom BootStrapper Hi, I have a wix custom Bootstrapper application which will download and install more than two msi in a client machine. Is there any option for me to pause the download process if internet is disconnected. If disconnected the application retries 3 times for re connection, if failed again it starts rollback. If so, is there any ways to pause the download before rollback starts. Please share the kind ideas. Regards, Balaji R. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Options-for-pausing-the-download-and-installation-in-wix-custom-BootStrapper-tp7596512.html Sent from the wix-users mailing list archive at Nabble.com. -- Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Customizing BA for Burn/Bundles
I'm creating lots of small msi's so I can modularize my installation package, and have been using the bundle feature (Burn?), to make an Exe that can install everything. The problem with this is the UI.. I have somewhat managed to make UI in the MSI, but I cannot use that UI, and need to make an UI in the Bundle package instead. It seems like I cannot use any the ui features that have been aquired for MSI, so Have to relearn everything in an totally different language for bundles.. Where can I find docoumentation on this format?, the Theme files seems to be kinda easy to manipulate, but i cannot find any information about sequence?, or adding other pages? What I need, is to implement some form of featureselection, not many selections, but a few, does it exist any bundle projects out there other than the wix installer (which is just a few pictures to click on), that show how to do this? Or is the idea that everyone need to make their own Bootstrapper application? -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Customizing-BA-for-Burn-Bundles-tp7596514.html Sent from the wix-users mailing list archive at Nabble.com. -- Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Customizing BA for Burn/Bundles
Both WixStdBA (C) and the WixBA (C#) have source code available to learn from. Since everyone wants a different look/feel and work flow, the bundle customization is often left up to a custom BA. For a vanilla install, WixStdBA does a good job, but injecting new pages isn't possible without coding. If you are using .Net for your application, I'd strongly suggest starting with a C# BA. This will allow you to do a full blown .Net UI, with all the customization you want, and then just property drive your MSI's. The second option would be to modify the Options page of WixStdBA to include some check boxes for your feature selection, but I don't think that would give you the optimal workflow that you're expecting (a user would have to click Options before hitting install). -Original Message- From: neslekkim [mailto:asbj...@neslekkim.net] Sent: Monday, August 25, 2014 9:55 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Customizing BA for Burn/Bundles I'm creating lots of small msi's so I can modularize my installation package, and have been using the bundle feature (Burn?), to make an Exe that can install everything. The problem with this is the UI.. I have somewhat managed to make UI in the MSI, but I cannot use that UI, and need to make an UI in the Bundle package instead. It seems like I cannot use any the ui features that have been aquired for MSI, so Have to relearn everything in an totally different language for bundles.. Where can I find docoumentation on this format?, the Theme files seems to be kinda easy to manipulate, but i cannot find any information about sequence?, or adding other pages? What I need, is to implement some form of featureselection, not many selections, but a few, does it exist any bundle projects out there other than the wix installer (which is just a few pictures to click on), that show how to do this? Or is the idea that everyone need to make their own Bootstrapper application? -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Customizing-BA-for-Burn-Bundles-tp7596514.html Sent from the wix-users mailing list archive at Nabble.com. -- Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] unsubscribe me
-Original Message- From: wix-users-requ...@lists.sourceforge.net [mailto:wix-users-requ...@lists.sourceforge.net] Sent: Friday, August 22, 2014 6:38 AM To: wix-users@lists.sourceforge.net Subject: WiX-users Digest, Vol 99, Issue 46 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: Dynamic dialog workflow (David G. van Hoose) 2. Re: Leave components installed between upgrades -but not permanent? (Spud) 3. Re: Burn not show installed prerequisites (LocalDB) MSI in Program and Features (Spud) 4. Re: Antivirus is blocking execution of standard bootstrapper application (Spud) 5. Re: Burn not show installed prerequisites (LocalDB) MSI in Program and Features (Mrugesh Patel) 6. Re: Download and Install Selected Msi packages using custom bootstrapper (Saravanan) 7. How to display uninstall progress bar using BootStrapper Application (linos) 8. How to reference variables within an msi that are set in bootstrapper app (linos) 9. Re: How to reference variables within an msi that are set in bootstrapper app (John Cooper) -- Message: 1 Date: Thu, 21 Aug 2014 16:26:21 -0500 From: David G. van Hoose david.g.vanho...@gmail.com Subject: Re: [WiX-users] Dynamic dialog workflow To: wix-users@lists.sourceforge.net Message-ID: 323A95C266EC4840BFEDF9148A81B40D@Bahamut Content-Type: text/plain; charset=UTF-8 Hello, I finally figured it out. I had instead of in my inequality conditions. Orca for the win! Regards, David From: David G. van Hoose Sent: Wednesday, August 20, 2014 14:31 To: wix-users@lists.sourceforge.net Subject: Dynamic dialog workflow Hello, I have read through lots of documentation and examples over the last year and have made a nice web service installer. Originally, my users (web server admins) wanted to be able to specify existing web sites during installation, so I made custom (Internal UI) dialogs and some custom actions that communicate with the Server Manager. Now, some of the admins want the installer to create new application pools and web sites instead of using existing ones. My first thought was to employ mux conditions on my PushButton?s published NewDialog events, but those do not work. Using the Internal UI, is there a way to have the workflow progress to different dialogs based on the value of a ComboBox property? If not, what alternatives would be my best options for a dynamic dialog workflow? Regards, David -- Message: 2 Date: Fri, 22 Aug 2014 03:24:16 -0700 (PDT) From: Spud andysmi...@gmail.com Subject: Re: [WiX-users] Leave components installed between upgrades -butnot permanent? To: wix-users@lists.sourceforge.net Message-ID: 1408703056301-7596468.p...@n2.nabble.com Content-Type: text/plain; charset=us-ascii Thanks for the reply (Schedule major upgrade late and ensure Component Rules are followed. ) Rob. I'm not sure I follow. Hopefully I'm following the component rules as all resources used more than once are only installed via one MSI in the GAC - lets call it SharedComponents.msi. In my (simplified) chain, I have -ProductA.msi -ProductB.msi -ProductC.msi -SharedComponents.msi. SharedComponents.msi gets installed when either product A,B or C are installed. If I schedule a major upgrade late (schedule RemoveExistingProducts after InstallFinalize) and define the MsiPackage in the chain with a DownloadURL, will this effectively a) Skip downloading the SharedComponents.msi as it will already be in the cache b) run but ultimately leave the resources untouched as it would (usually) have no updates and no removals due to being the same MSI ? Thanks again. Sorry if this is a silly Q - the problem I have is that we generally only have to update our installers every 6-8 months, by which time I've forgotten everything sheepish grin. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Leave-components-installed-between-upgrades-but-not-permanent-tp7596436p7596468.html Sent from the wix-users mailing list archive at Nabble.com. -- Message: 3 Date: Fri, 22 Aug 2014 03:29:19 -0700 (PDT) From: Spud andysmi...@gmail.com Subject: Re: [WiX-users] Burn not show installed prerequisites (LocalDB) MSI in Program and Features To: wix-users@lists.sourceforge.net Message-ID:
Re: [WiX-users] Customizing BA for Burn/Bundles
Would that be the code that is here? https://github.com/wixtoolset/wix3/tree/develop/src/ext/BalExtension mba = WixBA? I was hoping that one could use the same formats for the squences, languages, and ui definitions as one do for pure msi, but that is probably run by something else that is not part of wix? On Mon, Aug 25, 2014 at 5:46 PM, Hoover, Jacob jacob.hoo...@greenheck.com wrote: Both WixStdBA (C) and the WixBA (C#) have source code available to learn from. Since everyone wants a different look/feel and work flow, the bundle customization is often left up to a custom BA. For a vanilla install, WixStdBA does a good job, but injecting new pages isn't possible without coding. If you are using .Net for your application, I'd strongly suggest starting with a C# BA. This will allow you to do a full blown .Net UI, with all the customization you want, and then just property drive your MSI's. The second option would be to modify the Options page of WixStdBA to include some check boxes for your feature selection, but I don't think that would give you the optimal workflow that you're expecting (a user would have to click Options before hitting install). -Original Message- From: neslekkim [mailto:asbj...@neslekkim.net] Sent: Monday, August 25, 2014 9:55 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Customizing BA for Burn/Bundles I'm creating lots of small msi's so I can modularize my installation package, and have been using the bundle feature (Burn?), to make an Exe that can install everything. The problem with this is the UI.. I have somewhat managed to make UI in the MSI, but I cannot use that UI, and need to make an UI in the Bundle package instead. It seems like I cannot use any the ui features that have been aquired for MSI, so Have to relearn everything in an totally different language for bundles.. Where can I find docoumentation on this format?, the Theme files seems to be kinda easy to manipulate, but i cannot find any information about sequence?, or adding other pages? What I need, is to implement some form of featureselection, not many selections, but a few, does it exist any bundle projects out there other than the wix installer (which is just a few pictures to click on), that show how to do this? Or is the idea that everyone need to make their own Bootstrapper application? -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Customizing-BA-for-Burn-Bundles-tp7596514.html Sent from the wix-users mailing list archive at Nabble.com. -- Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- mvh Asbjørn -- Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Customizing BA for Burn/Bundles
The MSI UI is limited by windows installer. The BA UI as no such limitations. https://github.com/wixtoolset/wix3/tree/develop/src/Setup/WixBA is the BA for Wix -Original Message- From: Asbjørn Mikkelsen [mailto:asbj...@neslekkim.net] Sent: Monday, August 25, 2014 11:20 AM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Customizing BA for Burn/Bundles Would that be the code that is here? https://github.com/wixtoolset/wix3/tree/develop/src/ext/BalExtension mba = WixBA? I was hoping that one could use the same formats for the squences, languages, and ui definitions as one do for pure msi, but that is probably run by something else that is not part of wix? On Mon, Aug 25, 2014 at 5:46 PM, Hoover, Jacob jacob.hoo...@greenheck.com wrote: Both WixStdBA (C) and the WixBA (C#) have source code available to learn from. Since everyone wants a different look/feel and work flow, the bundle customization is often left up to a custom BA. For a vanilla install, WixStdBA does a good job, but injecting new pages isn't possible without coding. If you are using .Net for your application, I'd strongly suggest starting with a C# BA. This will allow you to do a full blown .Net UI, with all the customization you want, and then just property drive your MSI's. The second option would be to modify the Options page of WixStdBA to include some check boxes for your feature selection, but I don't think that would give you the optimal workflow that you're expecting (a user would have to click Options before hitting install). -Original Message- From: neslekkim [mailto:asbj...@neslekkim.net] Sent: Monday, August 25, 2014 9:55 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Customizing BA for Burn/Bundles I'm creating lots of small msi's so I can modularize my installation package, and have been using the bundle feature (Burn?), to make an Exe that can install everything. The problem with this is the UI.. I have somewhat managed to make UI in the MSI, but I cannot use that UI, and need to make an UI in the Bundle package instead. It seems like I cannot use any the ui features that have been aquired for MSI, so Have to relearn everything in an totally different language for bundles.. Where can I find docoumentation on this format?, the Theme files seems to be kinda easy to manipulate, but i cannot find any information about sequence?, or adding other pages? What I need, is to implement some form of featureselection, not many selections, but a few, does it exist any bundle projects out there other than the wix installer (which is just a few pictures to click on), that show how to do this? Or is the idea that everyone need to make their own Bootstrapper application? -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Customiz ing-BA-for-Burn-Bundles-tp7596514.html Sent from the wix-users mailing list archive at Nabble.com. -- Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- mvh Asbjørn -- Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Issues faced while upgrading from Wix 3.5 to Wix 3.8
You'll want to investigate the log files. They should show what is going on. ___ FireGiant | Dedicated support for the WiX toolset | http://www.firegiant.com/ -Original Message- From: CCM [mailto:chhaya_mal...@persistent.co.in] Sent: Monday, August 25, 2014 4:27 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Issues faced while upgrading from Wix 3.5 to Wix 3.8 Hi, For our project we used to create a bootstrapper installer with WiX 3.5. It included the .NetFramework 4.0 and our ProjectMSI. The product version used for this installer was 1.0.1.0. Now we have upgraded WiX to 3.8. The next product version used is 1.0.2.0. The product version for the Bundle and ProjectMSI are same. The product Id and upgrade code for ProjectMSI are the same as that used in 1.0.1.0. The Upgrade code for Bundle is different. Upgrade is allowed but Downgrade is not allowed for the product. We are facing the following issues: 1. If we have 1.0.1.0 (that was created with Wix 3.5) installed on a machine and we try to install 1.0.2.0 with setup.exe (that was created with Wix 3.8) then the control panel shows a single entry for the product with version 1.0.2.0 but when we check the version of the DLLs it shows 1.0.1.0. 2. Before creating the deployment builds we always create an engineering build with version 1.0.0.0. If we have 1.0.1.0 (that was created with Wix 3.5) installed on a machine and we try to install 1.0.0.0 with setup.exe (that was created with Wix 3.8) then the control panel shows two entries for the product - one for 1.0.1.0 and another for 1.0.0.0. However in both the cases if we try to run the ProjectMSI directly (setup.msi) it says Another version of this product is already installed... which is the expected behaviour. How can we get the same behaviour for bootstrapper setup.exe created with Wix 3.8. Thanks Regards, -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Issues-faced-while-upgrading-from-Wix-3-5-to-Wix-3-8-tp7596511.html Sent from the wix-users mailing list archive at Nabble.com. -- Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Splitting a package in a bundle
Yes, but note Bundle upgrades happen last (maybe useful notes: https://support.firegiant.com/entries/24024208-Bundle-chain-execution-order-). ___ FireGiant | Dedicated support for the WiX toolset | http://www.firegiant.com/ -Original Message- From: Nicolás Alvarez [mailto:nicolas.alva...@gmail.com] Sent: Sunday, August 24, 2014 2:08 PM To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] Splitting a package in a bundle I have decided that my common dependencies .msi in my bundles is too large and monolithic, and should be split into two or maybe three packages. Can I just create new packages with new product and upgrade codes, and make the bundle use those instead? If all works well, upgrading the bundle will uninstall the old monolithic package when uninstalling the old bundle, and then install the two new packages when installing the upgraded bundle. Is that how it works? -- Nicolás -- Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Issues with Wix Installer per-user minor upgrade
New issue to me. Sounds like you are executing a minor upgrade. Do those work
independent of the Bundle? Burn is just executing minor upgrades per MSI SDK so
not exactly sure what should be changed.
___
FireGiant | Dedicated support for the WiX toolset |
http://www.firegiant.com/
-Original Message-
From: Sascha Sertel [mailto:sascha.ser...@gmail.com]
Sent: Friday, August 22, 2014 1:31 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Issues with Wix Installer per-user minor upgrade
Well that didn't take long. I have been able to isolate the offending Windows
Update that breaks my WiX bundle:
Security Update for the Windows Installer Service: August 12, 2014 (
http://support.microsoft.com/kb/2918614)
After installing this update I can no longer update from one bundle to the
next. I'm not sure if this only affects bundles that were generated with WiX or
if this is a general MSI issue after this update.
The update replaces Msi.dll and other related binaries, so I'm guessing some
change in there messes things up for us.
The question is, which I hope someone can answer (Rob?), can this be resolved
by a change in the bundle or product wxs, or does it require updating to a
newer WiX version? Is it maybe fixed in 3.9 already? Or is it something
Microsoft needs to fix on their end republish the windows update?
I would file a Connect bug report for them but I can't really find any product
that would be suitable to file MSI defects against.
// Sascha
On Fri, Aug 22, 2014 at 12:23 PM, Sascha Sertel sascha.ser...@gmail.com
wrote:
I am having the EXACT same issue as described by Vikas, but I have
reason to believe that this breakage is caused by a recent Windows
Update released by Microsoft, because I tested packages that used to
upgrade fine from one version to the next (they are released in
production and have been used by customers without issues), and even those
don't upgrade anymore.
The errors in the main bundle log file are:
[1760:2DC0][2014-08-22T12:12:19]e000: Error 0x80070642: Failed to
perform minor upgrade of MSI package.
[1760:2DC0][2014-08-22T12:12:19]e000: Error 0x80070642: Failed to
configure per-user MSI package.
[1760:2DC0][2014-08-22T12:12:19]e000: Error 0x80070642: Failed to
execute MSI package.
And in the specific MSI log file I see:
MSI (s) (A4:30) [12:12:19:495]: SECREPAIR: Hash Database:
C:\Windows\Installer\SourceHash{C5E60292-2E11-4FAE-883F-E548ECF032F7}
MSI (s) (A4:30) [12:12:19:496]: SECREPAIR: CryptAcquireContext
succeeded MSI (s) (A4:30) [12:12:19:676]: SECREPAIR: filename:
Product.msi Stored Hash
Value:qifyrB1gltbWOyNTEPMp8gkQLOj80n1Vgs9hAkFUPeg= Current
Hash:ewxqrvKcJkUL0IxZgZeAoopceBPNACUkDakExnZTxbw=
MSI (s) (A4:30) [12:12:19:676]: Machine policy value
'AlwaysInstallElevated' is 0 MSI (s) (A4:30) [12:12:19:676]: User
policy value 'AlwaysInstallElevated'
is 0
MSI (s) (A4:30) [12:12:19:676]: MSI_LUA: Elevation prompt disabled for
silent installs MSI (s) (A4:30) [12:12:19:676]: Note: 1: 3 MSI (s)
(A4:30) [12:12:19:676]: SECUREREPAIR: SecureRepair Failed. Error
code: 390FC9A18
After that it rolls back. It looks like it's trying to repair
something because the hash values don't match?
I have another test machine on which I will uninstall all Windows
Updates from the last week or so to see if it makes a difference or
not. I'm running on Windows 8.1 Pro Update 1 and all the latest
updates including the downgraded Upgrade 2. I also found this thread:
http://www.edugeek.net/forums/windows-7/140586-possible-issue-kb291861
4-causing-overlapped-i-o-operation-progress-errors.html
Any suggestions/ideas on how to fix this?
// Sascha
On Wed, Aug 20, 2014 at 10:10 PM, vikasyv vikas@gmail.com wrote:
I am using a Bootstrapper Application to bundle the msi installer.
Can this cause any problems? Here is the BA code:
Bundle Name=Bundle-Name Version=$(var.ProductVersion)
Manufacturer=CompanyName IconSourceFile=$(var.IconSourceFile)
UpgradeCode=UPGRADE-GUID Copyright=Copyright String
BootstrapperApplicationRef
Id=WixStandardBootstrapperApplication.RtfLicense
bal:WixStandardBootstrapperApplication ShowVersion=yes
ThemeFile=Installer-Theme.xml LicenseUrl=/
Payload SourceFile=$(var.PayloadSourceFile)/
/BootstrapperApplicationRef
util:RegistrySearch Root='HKCU' Key='SOFTWARE\AppName'
Id=CheckInstalled Variable=App_Installer Result=exists /
Chain
MsiPackage Id=quot;MainPackagequot;
SourceFile=quot;lt;MsiFileName.msi Vital=yes
DisplayInternalUI=no /
/Chain
/Bundle
Thanks
Vikas
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Issues-
with-Wix-Installer-per-user-minor-upgrade-tp7596442p7596450.html
Sent from the wix-users mailing list archive at Nabble.com.
Re: [WiX-users] SourceProperty of CopyFile-element changed after execution
No, it is not in the Directory table.
It is a full file path. (C:\someDir\someFile.txt )
I copy the file MY_SOURCE to the directory MY_DIR and rename it to MY_NAME.
From: r...@firegiant.com
To: wix-users@lists.sourceforge.net
Date: Mon, 25 Aug 2014 15:13:38 +
Subject: Re: [WiX-users] SourceProperty of CopyFile-element changed after
execution
MY_SOURCE in the Directory table?
___
FireGiant | Dedicated support for the WiX toolset |
http://www.firegiant.com/
-Original Message-
From: Ingo Fischer [mailto:ingoderfisc...@hotmail.com]
Sent: Monday, August 25, 2014 6:31 AM
To: General discussion about the WiX toolset.
Subject: [WiX-users] SourceProperty of CopyFile-element changed after
execution
Hello,
I have following CopyFile element in my Product.wxs:
CopyFile Id=myId DestinationDirectory=MY_DIR
DestinationName=MY_NAME.xml SourceProperty=MY_SOURCE /
My bootstrapper application passes the MY_SOURCE property in to the msi-file.
The value of MY_SOURCE is C:\someDir\someFile.txt.
It includes the filename and extension!
Some CA that executes after CreateFiles uses the property:
if (!File.Exists(session[MY_SOURCE]))
{
session.log(string.format(File {0} does not exist, session[MY_SOURCE])); }
the log is:
File C:\someDir\someFile.txt\ does not exist
MY_SOURCE changed from C:\someDir\someFile.txt to C:\someDir\someFile.txt\
Why?
Btw, if I use a local property it works:
SetProperty Id=copyMy_Source Value=[My_SOURCE] Sequence=execute
After=CostFinalize / ...
CopyFile Id=myId DestinationDirectory=MY_DIR
DestinationName=MY_NAME.xml SourceProperty=copyMy_SOURCE /
log:
MSI (s) (50:84) [15:12:15:224]: PROPERTY CHANGE: Adding copyMy_Source
property. Its value is 'C:\someDir\someFile.txt'.
and this is also my workaround for now.
--
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] No progress in installation
Hi,
we had created an installer using Bootstrapper and Burn with wix 3.7. In some
machines, our setup installation was not started. Setup installation was in a
starting state. No progress in installation.
We are getting the below error when we look at the log file.
[0E6C:10D4][2014-08-13T12:03:59]e000: Error 0x80070002: Failed to get size of
pseudo bundle: C:\ProgramData\Package
Cache\{6f998459-8c96-468d-add4-c3fbae829931}\Application_1.1.0.3.exe
[0E6C:10D4][2014-08-13T12:03:59]e000: Error 0x80070002: Failed to initialize
package from related bundle id: {6f998459-8c96-468d-add4-c3fbae829931}
[0E6C:10D4][2014-08-13T12:03:59]i199: Detect complete, result: 0x0
[0E6C:10D4][2014-08-13T12:03:59]i300: Apply begin
[1240:15D8][2014-08-13T12:03:59]e000: Error 0x80070002: Failed to get size of
pseudo bundle: C:\ProgramData\Package
Cache\{6f998459-8c96-468d-add4-c3fbae829931}\ Application_1.1.0.3.exe
[1240:15D8][2014-08-13T12:03:59]e000: Error 0x80070002: Failed to initialize
package from related bundle id: {6f998459-8c96-468d-add4-c3fbae829931}
[1240:15D8][2014-08-13T12:04:02]i360: Creating a system restore point.
[1240:15D8][2014-08-13T12:06:10]i361: Created a system restore point.
[1240:15D8][2014-08-13T12:06:10]i323: Registering package dependency provider:
{2882A35F-95A8-4C34-91E7-88433FE3116E}, version: 12.2.0.36, package: Studio
[1240:15D8][2014-08-13T12:06:10]i325: Registering dependency:
{d5f0a119-9ba3-4a19-b1cf-882c39cb4720} on package provider:
{2882A35F-95A8-4C34-91E7-88433FE3116E}, package: Studio
[0E6C:10D4][2014-08-13T12:06:10]i399: Apply complete, result: 0x0, restart:
None, ba requested restart: No
[0E6C:10D4][2014-08-13T13:13:31]i500: Shutting down, exit code: 0x0
Already I have tried the work around as clean up the temp folder, restart the
machine and reinstall the setup. It also didn't work. My setup installation was
stuck in starting state itself. We don't want to follow this work around
anymore as this is not worked in our machines. Can you please provide solution
for this issue?
Thanks in Advance!
--
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Customizing BA for Burn/Bundles
ah, thanks. When I'm using this element: BootstrapperApplicationRef Id='WixStandardBootstrapperApplication.RtfLicense' I'm using the C++ one then?, does it exist any examples that uses this WixBA to get an startingpoint on how I can reference it from wxs? On Mon, Aug 25, 2014 at 6:24 PM, Hoover, Jacob jacob.hoo...@greenheck.com wrote: The MSI UI is limited by windows installer. The BA UI as no such limitations. https://github.com/wixtoolset/wix3/tree/develop/src/Setup/WixBA is the BA for Wix -Original Message- From: Asbjørn Mikkelsen [mailto:asbj...@neslekkim.net] Sent: Monday, August 25, 2014 11:20 AM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Customizing BA for Burn/Bundles Would that be the code that is here? https://github.com/wixtoolset/wix3/tree/develop/src/ext/BalExtension mba = WixBA? I was hoping that one could use the same formats for the squences, languages, and ui definitions as one do for pure msi, but that is probably run by something else that is not part of wix? On Mon, Aug 25, 2014 at 5:46 PM, Hoover, Jacob jacob.hoo...@greenheck.com wrote: Both WixStdBA (C) and the WixBA (C#) have source code available to learn from. Since everyone wants a different look/feel and work flow, the bundle customization is often left up to a custom BA. For a vanilla install, WixStdBA does a good job, but injecting new pages isn't possible without coding. If you are using .Net for your application, I'd strongly suggest starting with a C# BA. This will allow you to do a full blown .Net UI, with all the customization you want, and then just property drive your MSI's. The second option would be to modify the Options page of WixStdBA to include some check boxes for your feature selection, but I don't think that would give you the optimal workflow that you're expecting (a user would have to click Options before hitting install). -Original Message- From: neslekkim [mailto:asbj...@neslekkim.net] Sent: Monday, August 25, 2014 9:55 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Customizing BA for Burn/Bundles I'm creating lots of small msi's so I can modularize my installation package, and have been using the bundle feature (Burn?), to make an Exe that can install everything. The problem with this is the UI.. I have somewhat managed to make UI in the MSI, but I cannot use that UI, and need to make an UI in the Bundle package instead. It seems like I cannot use any the ui features that have been aquired for MSI, so Have to relearn everything in an totally different language for bundles.. Where can I find docoumentation on this format?, the Theme files seems to be kinda easy to manipulate, but i cannot find any information about sequence?, or adding other pages? What I need, is to implement some form of featureselection, not many selections, but a few, does it exist any bundle projects out there other than the wix installer (which is just a few pictures to click on), that show how to do this? Or is the idea that everyone need to make their own Bootstrapper application? -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Customiz ing-BA-for-Burn-Bundles-tp7596514.html Sent from the wix-users mailing list archive at Nabble.com. -- Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- mvh Asbjørn -- Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- mvh Asbjørn -- Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/ ___ WiX-users mailing list
Re: [WiX-users] Issues with Wix Installer per-user minor upgrade
This thread also talks about issues with the August 12th Updates: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/SECREPAIR-CryptAcquireContext-Could-not-create-the-default-key-container-td7596414.html -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Issues-with-Wix-Installer-per-user-minor-upgrade-tp7596442p7596528.html Sent from the wix-users mailing list archive at Nabble.com. -- Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] No progress in installation
The error indicates The system cannot find the file specified. Do you have
an over-zealous Anti-Virus software running on the effected machines?
-Original Message-
From: Vadivel Natarajan [mailto:vadiv...@syncfusion.com]
Sent: Monday, August 25, 2014 12:04 PM
To: General discussion about the WiX toolset.
Subject: [WiX-users] No progress in installation
Hi,
we had created an installer using Bootstrapper and Burn with wix 3.7. In some
machines, our setup installation was not started. Setup installation was in a
starting state. No progress in installation.
We are getting the below error when we look at the log file.
[0E6C:10D4][2014-08-13T12:03:59]e000: Error 0x80070002: Failed to get size of
pseudo bundle: C:\ProgramData\Package
Cache\{6f998459-8c96-468d-add4-c3fbae829931}\Application_1.1.0.3.exe
[0E6C:10D4][2014-08-13T12:03:59]e000: Error 0x80070002: Failed to initialize
package from related bundle id: {6f998459-8c96-468d-add4-c3fbae829931}
[0E6C:10D4][2014-08-13T12:03:59]i199: Detect complete, result: 0x0
[0E6C:10D4][2014-08-13T12:03:59]i300: Apply begin
[1240:15D8][2014-08-13T12:03:59]e000: Error 0x80070002: Failed to get size of
pseudo bundle: C:\ProgramData\Package
Cache\{6f998459-8c96-468d-add4-c3fbae829931}\ Application_1.1.0.3.exe
[1240:15D8][2014-08-13T12:03:59]e000: Error 0x80070002: Failed to initialize
package from related bundle id: {6f998459-8c96-468d-add4-c3fbae829931}
[1240:15D8][2014-08-13T12:04:02]i360: Creating a system restore point.
[1240:15D8][2014-08-13T12:06:10]i361: Created a system restore point.
[1240:15D8][2014-08-13T12:06:10]i323: Registering package dependency provider:
{2882A35F-95A8-4C34-91E7-88433FE3116E}, version: 12.2.0.36, package: Studio
[1240:15D8][2014-08-13T12:06:10]i325: Registering dependency:
{d5f0a119-9ba3-4a19-b1cf-882c39cb4720} on package provider:
{2882A35F-95A8-4C34-91E7-88433FE3116E}, package: Studio
[0E6C:10D4][2014-08-13T12:06:10]i399: Apply complete, result: 0x0, restart:
None, ba requested restart: No
[0E6C:10D4][2014-08-13T13:13:31]i500: Shutting down, exit code: 0x0
Already I have tried the work around as clean up the temp folder, restart the
machine and reinstall the setup. It also didn't work. My setup installation was
stuck in starting state itself. We don't want to follow this work around
anymore as this is not worked in our machines. Can you please provide solution
for this issue?
Thanks in Advance!
--
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] No progress in installation
My best guess is that you deleted stuff out of your package cache without
updating the appropriate Add/Remove Programs registration as well.
___
FireGiant | Dedicated support for the WiX toolset |
http://www.firegiant.com/
-Original Message-
From: Vadivel Natarajan [mailto:vadiv...@syncfusion.com]
Sent: Monday, August 25, 2014 10:04 AM
To: General discussion about the WiX toolset.
Subject: [WiX-users] No progress in installation
Hi,
we had created an installer using Bootstrapper and Burn with wix 3.7. In some
machines, our setup installation was not started. Setup installation was in a
starting state. No progress in installation.
We are getting the below error when we look at the log file.
[0E6C:10D4][2014-08-13T12:03:59]e000: Error 0x80070002: Failed to get size of
pseudo bundle: C:\ProgramData\Package
Cache\{6f998459-8c96-468d-add4-c3fbae829931}\Application_1.1.0.3.exe
[0E6C:10D4][2014-08-13T12:03:59]e000: Error 0x80070002: Failed to initialize
package from related bundle id: {6f998459-8c96-468d-add4-c3fbae829931}
[0E6C:10D4][2014-08-13T12:03:59]i199: Detect complete, result: 0x0
[0E6C:10D4][2014-08-13T12:03:59]i300: Apply begin
[1240:15D8][2014-08-13T12:03:59]e000: Error 0x80070002: Failed to get size of
pseudo bundle: C:\ProgramData\Package
Cache\{6f998459-8c96-468d-add4-c3fbae829931}\ Application_1.1.0.3.exe
[1240:15D8][2014-08-13T12:03:59]e000: Error 0x80070002: Failed to initialize
package from related bundle id: {6f998459-8c96-468d-add4-c3fbae829931}
[1240:15D8][2014-08-13T12:04:02]i360: Creating a system restore point.
[1240:15D8][2014-08-13T12:06:10]i361: Created a system restore point.
[1240:15D8][2014-08-13T12:06:10]i323: Registering package dependency provider:
{2882A35F-95A8-4C34-91E7-88433FE3116E}, version: 12.2.0.36, package: Studio
[1240:15D8][2014-08-13T12:06:10]i325: Registering dependency:
{d5f0a119-9ba3-4a19-b1cf-882c39cb4720} on package provider:
{2882A35F-95A8-4C34-91E7-88433FE3116E}, package: Studio
[0E6C:10D4][2014-08-13T12:06:10]i399: Apply complete, result: 0x0, restart:
None, ba requested restart: No
[0E6C:10D4][2014-08-13T13:13:31]i500: Shutting down, exit code: 0x0
Already I have tried the work around as clean up the temp folder, restart the
machine and reinstall the setup. It also didn't work. My setup installation was
stuck in starting state itself. We don't want to follow this work around
anymore as this is not worked in our machines. Can you please provide solution
for this issue?
Thanks in Advance!
--
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] How to automatically include localized satellite assemblies?
Hi all, I'm new to WiX and am inheriting a project. So please pardon me if this is an silly question. Can WiX be set to automatically include all generated satellite resource assemblies? The goal is to have a single English language MSI that installs an application with localized strings available for ~10 languages. I found this StackOverflow question: http://stackoverflow.com/questions/2162320/how-do-i-include-satellite-assemblieslocalized-resources-in-an-msi-built-with However the solution presented suggests that new component and directory definitions needs to be manually added for each culture variant. Is that the correct method, or can WiX somehow automatically learn about each language from the Visual Studio project definitions? (Running VS2010 and WiX 3.8) Thanks much -- Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Issues with Wix Installer per-user minor upgrade
@Rob: Yes the bundle as well as the packages inside the bundle all work fine without the August 12 update, but started failing after applying the update. @Phill: Yes that is exactly the issue I'm seeing as well. Is there any solution to this other than uninstalling the August 12 update? // Sascha On Mon, Aug 25, 2014 at 10:49 AM, Phill Hogland phogl...@rimage.com wrote: This thread also talks about issues with the August 12th Updates: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/SECREPAIR-CryptAcquireContext-Could-not-create-the-default-key-container-td7596414.html -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Issues-with-Wix-Installer-per-user-minor-upgrade-tp7596442p7596528.html Sent from the wix-users mailing list archive at Nabble.com. -- Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Customizing BA for Burn/Bundles
Here is a tutorial on using a mba: http://bryanpjohnston.com/2012/09/28/custom-wix-managed-bootstrapper-application/ The WixBA is used in the wixtoolset setup. So unlike the WixStdBA, it is not packaged as a module that can be included in your project. It is specific to the needs of the Wixtoolset setup. But it is still a good working example of how you can write your own mba. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Customizing-BA-for-Burn-Bundles-tp7596514p7596533.html Sent from the wix-users mailing list archive at Nabble.com. -- Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Issues with Wix Installer per-user minor upgrade
Microsoft has acknowledged some of the issues related to the August 12th Update, and in some cases advised folks to uninstall certain of the updates in the August 12th release. I did not see any specific instruction from Microsoft about this particular KB. I suspect it would be best to contact Microsoft, and let them know the details you are observing. http://support.microsoft.com/kb/2982791/en-us -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Issues-with-Wix-Installer-per-user-minor-upgrade-tp7596442p7596534.html Sent from the wix-users mailing list archive at Nabble.com. -- Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Issues with Wix Installer per-user minor upgrade
Just to clarify I don't have any connection to Microsoft or any expertise on the subject. Just passing on observations gleaned from Googling. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Issues-with-Wix-Installer-per-user-minor-upgrade-tp7596442p7596535.html Sent from the wix-users mailing list archive at Nabble.com. -- Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Customizing BA for Burn/Bundles
Great!, thanks, this looks very usefull On Mon, Aug 25, 2014 at 11:08 PM, Phill Hogland phogl...@rimage.com wrote: Here is a tutorial on using a mba: http://bryanpjohnston.com/2012/09/28/custom-wix-managed-bootstrapper-application/ The WixBA is used in the wixtoolset setup. So unlike the WixStdBA, it is not packaged as a module that can be included in your project. It is specific to the needs of the Wixtoolset setup. But it is still a good working example of how you can write your own mba. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Customizing-BA-for-Burn-Bundles-tp7596514p7596533.html Sent from the wix-users mailing list archive at Nabble.com. -- Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- mvh Asbjørn -- Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Customizing BA for Burn/Bundles
This may also be helpful http://www.wrightfully.com/part-1-of-writing-your-own-net-based-installer-with-wix-overview/ And there is a book on the wixtoolset.org site which I think has information on mba development. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Customizing-BA-for-Burn-Bundles-tp7596514p7596537.html Sent from the wix-users mailing list archive at Nabble.com. -- Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Cannot view RootView.xaml file in visual studio 2010
So, I was able to fix my problem on my local PC, but since then I needed to switch on over to a VM that is running Window7. To my surprise the problem came back, but only on the VM. This is very disturbing especially when the folder containing all of the source code was copied from the PC, which works. What would cause this problem from one machine to another?? Up to my eye balls with frustration, I decided to take on another path, which was create a new BA project and call it testBA instead of wixBA. I'm successfull in building my project, but ran into the same problem as before where I cannot view the RootView.xaml file only this time I'm, receiving another error. System.Xaml.XamlObjectWriterException Set property 'System.Windows.ResourceDictionary.Source' threw an exception. at MS.Internal.Xaml.Runtime.ClrObjectRuntime.SetValue(Object inst, XamlMember property, Object value) at MS.Internal.Xaml.Runtime.PartialTrustTolerantRuntime.SetValue(Object obj, XamlMember property, Object value) at System.Xaml.XamlObjectWriter.SetValue(Object inst, XamlMember property, Object value) at System.Xaml.XamlObjectWriter.Logic_ApplyPropertyValue(ObjectWriterContext ctx, XamlMember prop, Object value, Boolean onParent) at System.Xaml.XamlObjectWriter.Logic_DoAssignmentToParentProperty(ObjectWriterContext ctx) at System.Xaml.XamlObjectWriter.Logic_AssignProvidedValue(ObjectWriterContext ctx) at System.Xaml.XamlObjectWriter.WriteEndMember() at System.Xaml.XamlWriter.WriteNode(XamlReader reader) at System.Xaml.XamlServices.Transform(XamlReader xamlReader, XamlWriter xamlWriter, Boolean closeWriter) at System.Xaml.XamlServices.Transform(XamlReader xamlReader, XamlWriter xamlWriter) at System.Windows.SystemResources.ResourceDictionaries.LoadDictionary(Assembly assembly, String assemblyName, String resourceName, Boolean isTraceEnabled) at System.Windows.SystemResources.ResourceDictionaries.LoadGenericDictionary(Boolean isTraceEnabled) at System.Windows.SystemResources.FindDictionaryResource(Object key, Type typeKey, ResourceKey resourceKey, Boolean isTraceEnabled, Boolean allowDeferredResourceReference, Boolean mustReturnDeferredResourceReference, Boolean canCache) at System.Windows.SystemResources.FindResourceInternal(Object key, Boolean allowDeferredResourceReference, Boolean mustReturnDeferredResourceReference) at System.Windows.StyleHelper.GetThemeStyle(FrameworkElement fe, FrameworkContentElement fce) at System.Windows.FrameworkElement.UpdateThemeStyleProperty() at System.Windows.FrameworkElement.OnInitialized(EventArgs e) at System.Windows.FrameworkElement.TryFireInitialized() at System.Windows.FrameworkElement.ChangeLogicalParent(DependencyObject newParent) at System.Windows.FrameworkElement.AddLogicalChild(Object child) at System.Windows.Controls.UIElementCollection.AddInternal(UIElement element) at System.Windows.Controls.UIElementCollection.Add(UIElement element) at MS.Internal.GridControl.GridDesigner.InitGridDesigner() at MS.Internal.GridControl.GridDesigner.GetDesigner(ModelItem gridItem) at MS.Internal.GridControl.AlwaysVisibleGridAdornerProvider.Activate(ModelItem item) at Microsoft.Windows.Design.Interaction.AdornerProvider.InvokeActivate(EditingContext context, ModelItem item) at MS.Internal.Features.AdornerProviderFeatureConnector.FeatureProvidersAdded(ModelItem item, IEnumerable`1 extensions) at Microsoft.Windows.Design.Policies.PolicyDrivenFeatureConnector`1.UpdateFeatureProviders() at MS.Internal.Features.PolicyDrivenToolFeatureConnector`1.UpdateCurrentTool(Tool newTool) at MS.Internal.Features.PolicyDrivenToolFeatureConnector`1..ctorb__0(Tool newTool) at Microsoft.Windows.Design.ContextItemManager.SubscribeProxy`1.SubscribeContext(ContextItem item) at Microsoft.Windows.Design.SubscribeContextCallback.Invoke(ContextItem item) at Microsoft.Windows.Design.EditingContext.DefaultContextItemManager.OnItemChanged(ContextItem item) at Microsoft.Windows.Design.EditingContext.DefaultContextItemManager.SetValue(ContextItem value) at MS.Internal.Host.ToolSubsystem.ActivateTool(ToolFactory toolFactory) at MS.Internal.Host.ToolSubsystem..ctor(EditingContext editingContext, DesignerContext designerContext) at MS.Internal.Host.Designer.Load() at MS.Internal.Designer.VSDesigner.Load() at MS.Internal.Designer.VSIsolatedDesigner.VSIsolatedView.Load() at MS.Internal.Designer.VSIsolatedDesigner.VSIsolatedDesignerFactory.Load(IsolatedView view) at MS.Internal.Host.Isolation.IsolatedDesigner.BootstrapProxy.LoadDesigner(IsolatedDesignerFactory factory, IsolatedView view) at MS.Internal.Host.Isolation.IsolatedDesigner.BootstrapProxy.LoadDesigner(IsolatedDesignerFactory factory, IsolatedView view) at MS.Internal.Host.Isolation.IsolatedDesigner.Load() at MS.Internal.Designer.DesignerPane.LoadDesignerView() System.IO.FileNotFoundException Could not load file or assembly 'BootstrapperCore,
Re: [WiX-users] Copy the files from installation location to another location
-- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Copy-the-files-from-installation-location-to-another-location-tp7596539p7596540.html Sent from the wix-users mailing list archive at Nabble.com. -- Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Issues faced while upgrading from Wix 3.5 to Wix 3.8
Please find the Burn log for scenario 2 below:
[23FC:17E0][2014-08-25T18:42:45]i001: Burn v3.8.1128.0, Windows v6.1 (Build
7601: Service Pack 1), path:
C:\Users\Administrator\Desktop\MyProject\1.0.0.0\en-us_1.0.0.0\Setup.exe,
cmdline: '/log D:\WixLog.txt -burn.unelevated
BurnPipe.{E8510335-55EC-40C7-B8D8-92BC3F32988E}
{6EF0667C-E7FE-4F9E-A9A2-B7D7DF909702} 4044'
[23FC:17E0][2014-08-25T18:42:45]i000: Initializing string variable
'PARAMETER_0' to value ''
[23FC:17E0][2014-08-25T18:42:45]i000: Initializing string variable
'PARAMETER_1' to value ''
[23FC:17E0][2014-08-25T18:42:45]i000: Setting string variable 'WixBundleLog'
to value 'D:\WixLog.txt'
[23FC:17E0][2014-08-25T18:42:45]i000: Setting string variable
'WixBundleOriginalSource' to value
'C:\Users\Administrator\Desktop\MyProject\1.0.0.0\en-us_1.0.0.0\Setup.exe'
[23FC:17E0][2014-08-25T18:42:45]i000: Setting string variable
'WixBundleName' to value 'Project Software'
[23FC:17E0][2014-08-25T18:42:45]i100: Detect begin, 3 packages
[23FC:17E0][2014-08-25T18:42:45]i000: Setting string variable
'Netfx4x64FullVersion' to value '4.5.50709'
[23FC:17E0][2014-08-25T18:42:45]i000: Setting string variable
'Netfx4FullVersion' to value '4.5.50709'
[23FC:17E0][2014-08-25T18:42:45]i052: Condition 'Netfx4FullVersion AND (NOT
VersionNT64 OR Netfx4x64FullVersion)' evaluates to true.
[23FC:17E0][2014-08-25T18:42:45]i103: Detected related package:
{3E2AE35F-4FF2-4E81-AF16-F4D76AA25C54}, scope: PerMachine, version: 1.0.1.0,
language: 1033 operation: Downgrade
[23FC:17E0][2014-08-25T18:42:45]i101: Detected package: Netfx4Full, state:
Present, cached: None
[23FC:17E0][2014-08-25T18:42:45]i101: Detected package: ThirdPartyTool,
state: Present, cached: None
[23FC:17E0][2014-08-25T18:42:45]i101: Detected package: ProjectMSI, state:
Superseded, cached: None
[23FC:17E0][2014-08-25T18:42:45]i199: Detect complete, result: 0x0
[23FC:1CF8][2014-08-25T18:42:48]i000: Setting numeric variable
'EulaAcceptCheckbox' to value 0
[23FC:17E0][2014-08-25T18:42:48]i200: Plan begin, 3 packages, action:
Install
[23FC:17E0][2014-08-25T18:42:48]w321: Skipping dependency registration on
package with no dependency providers: Netfx4Full
[23FC:17E0][2014-08-25T18:42:48]i201: Planned package: Netfx4Full, state:
Present, default requested: Present, ba requested: Present, execute: None,
rollback: None, cache: No, uncache: No, dependency: None
[23FC:17E0][2014-08-25T18:42:48]i201: Planned package: ThirdPartyTool,
state: Present, default requested: Present, ba requested: Present, execute:
None, rollback: None, cache: No, uncache: No, dependency: Register
[23FC:17E0][2014-08-25T18:42:48]i201: Planned package: ProjectMSI, state:
Superseded, default requested: Present, ba requested: Present, execute:
None, rollback: None, cache: No, uncache: No, dependency: Register
[23FC:17E0][2014-08-25T18:42:48]i299: Plan complete, result: 0x0
[23FC:17E0][2014-08-25T18:42:48]i300: Apply begin
[0FCC:1510][2014-08-25T18:42:48]i360: Creating a system restore point.
[0FCC:1510][2014-08-25T18:42:54]i361: Created a system restore point.
[0FCC:1510][2014-08-25T18:42:54]i000: Caching bundle from:
'C:\Users\ADMINI~1\AppData\Local\Temp\{9394f13e-0fc1-41cc-9098-b69c312bb248}\.be\setup.exe'
to: 'C:\ProgramData\Package
Cache\{9394f13e-0fc1-41cc-9098-b69c312bb248}\setup.exe'
[0FCC:1510][2014-08-25T18:42:54]i320: Registering bundle dependency
provider: {9394f13e-0fc1-41cc-9098-b69c312bb248}, version: 1.0.0.0
[0FCC:1510][2014-08-25T18:42:54]i323: Registering package dependency
provider: {CC3F5E73-FE3D-4D41-9B11-4484C6FAE10F}, version: 5.1.010.0,
package: ThirdPartyTool
[0FCC:1510][2014-08-25T18:42:54]i325: Registering dependency:
{9394f13e-0fc1-41cc-9098-b69c312bb248} on package provider:
{CC3F5E73-FE3D-4D41-9B11-4484C6FAE10F}, package: ThirdPartyTool
[0FCC:1510][2014-08-25T18:42:54]i323: Registering package dependency
provider: {3E2AE35F-4FF2-4E81-AF16-F4D76AA25C54}, version: 1.0.0.0, package:
ProjectMSI
[0FCC:1510][2014-08-25T18:42:54]i325: Registering dependency:
{9394f13e-0fc1-41cc-9098-b69c312bb248} on package provider:
{3E2AE35F-4FF2-4E81-AF16-F4D76AA25C54}, package: ProjectMSI
[23FC:17E0][2014-08-25T18:42:54]i399: Apply complete, result: 0x0, restart:
None, ba requested restart: No
[23FC:17E0][2014-08-25T18:42:57]i500: Shutting down, exit code: 0x0
[23FC:17E0][2014-08-25T18:42:57]i410: Variable: EulaAcceptCheckbox = 0
[23FC:17E0][2014-08-25T18:42:57]i410: Variable: Netfx4FullVersion =
4.5.50709
[23FC:17E0][2014-08-25T18:42:57]i410: Variable: Netfx4x64FullVersion =
4.5.50709
[23FC:17E0][2014-08-25T18:42:57]i410: Variable: VersionNT64 = 6.1.0.0
[23FC:17E0][2014-08-25T18:42:57]i410: Variable: PARAMETER_1 =
[23FC:17E0][2014-08-25T18:42:57]i410: Variable: PARAMETER_0 =
[23FC:17E0][2014-08-25T18:42:57]i410: Variable: WixBundleAction = 4
[23FC:17E0][2014-08-25T18:42:57]i410: Variable: WixBundleElevated = 1
[23FC:17E0][2014-08-25T18:42:57]i410: Variable: WixBundleInstalled = 0
[23FC:17E0][2014-08-25T18:42:57]i410: Variable: WixBundleLog =
