Re: [WiX-users] Finding out the number of cores during install?
You can get into all sorts of pain identifying logical cores vs physical cores, but the quick way is to just look at the NUMBER_OF_PROCESSORS environment variable. Rob On 13/02/2013 18:22, Stephen Turner wrote: Hi During the install of our product we need to know how many cores the CPU has. Does Wix have this capability?. Thanks - Stephen Turner AudioScience, Inc. -- Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb -- Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Solved! RE: RegistrySearch returning strange value
Yep, the Canon installers are the scourge of the deployment world ;) Us too. Sorry I didn't see your message in time. http://kb.sdl.com/#tab:homeTab:crumb:7:artId:4654 -Original Message- From: Arnette, Bill [mailto:bi...@signalscape.com] Sent: 13 February 2013 18:59 To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] Solved! RE: RegistrySearch returning strange value Solved! It seems that (an older version) of Canon Easy Web-Print EX which shipped with the (in our case) Pixma MG8120 was putting its Uninstall values directly beneath the Uninstall key instead of in its own product-specific key and didn't clear them on uninstall. So for a new install of our product, [PREVIOUSVERSIONSINSTALLED] resolved to an empty string thus causing my AppSearch to resolve to HKLM:Software\Microsoft\Windows\CurrentVersion\Uninstall\@InstallLocatio n where it happily found the erroneous InstallLocation value. The current version of the Canon software on their web site creates the correct Uninstall key/value hierarchy so I was unable to reproduce it on my machine. These people ran into the same issue but were unable to figure it out.. http://community.mediabrowser.tv/permalinks/2650/cronos-install-error Is there any way to get AppSearch to log what path it is searching or at what path it found a valid value? That would have helped tremendously in this case. -Original Message- From: Arnette, Bill [mailto:bi...@signalscape.com] Sent: Wednesday, February 13, 2013 11:42 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] RegistrySearch returning strange value Hi all, I ran into the strangest problem on a customer's machine today. He was installing a new version (MAJOR upgrade) of our software which has the authoring below. We set INSTALLDIR from UPGRADEDIR if a previous version is installed (SetUpgradeInstallDir custom action) and make the installation folder read-only (conditioned on UPGRADEDIR) on the [Admin]FolderForm to force the new version to be installed to the same location. On this particular customer's computer, UPGRADEDIR was set to some other application (in fact a Canon software component). This would happen even if I uninstalled the older version of my application and the Canon software. My first thought was that for some reason our UpgradeCode was the same as the Canon software; though we should be able to have GUID collision like that. But after downloading and examining the Canon software's installer, it does not even appear to be Windows Installer based. I am going to modify the conditions to also require PREVIOUSVERSIONSINSTALLED to be non-NULL to determine that this is an upgrade, but why would the RegistrySearch return some other application's Uninstall key? WiX version is 3.0. Installation target is Win7 64-bit. Application/installer is 32-bit. Thanks in advance for any insight you can provide. Bill !-- Find previous installation folder for upgrade after uninstall -- Property Id=UPGRADEDIR RegistrySearch Id=FindInstallLocation Root=HKLM Key=Software\Microsoft\Windows\CurrentVersion\Uninstall\[PREVIOUSVERSIO NSINSTALLED] Name=InstallLocation Type=raw / /Property CustomAction Id=SetUpgradeInstallDir Return=check Execute=oncePerProcess Property=INSTALLDIR Value=[UPGRADEDIR]/ Upgrade Id=$(var.UpgradeCode) UpgradeVersion Minimum=$(var.version) Property=NEWERPRODUCTFOUND OnlyDetect=yes IncludeMinimum=yes / UpgradeVersion Minimum=1.0.0 Maximum=$(var.version) RemoveFeatures=ALL Property=PREVIOUSVERSIONSINSTALLED IncludeMinimum=yes / /Upgrade InstallExecuteSequence . . . Custom Action=SetARPInstallLocation Before=RegisterProductNOT Installed/Custom AppSearch After=FindRelatedProducts/ Custom Action=SetUpgradeInstallDir After=AppSearch![CDATA[UPGRADEDIR ]]/Custom . . . /InstallExecuteSequence InstallUISequence AppSearch After=FindRelatedProducts/ Custom Action=ERRCA_UIANDADVERTISED Before=AppSearch![CDATA[ProductState=1]]/Custom Custom Action=SetUpgradeInstallDir After=AppSearch![CDATA[UPGRADEDIR ]]/Custom . . . /InstallUISequence --**-- This email and any files transmitted with it are confidential and intended solely for the use of Signalscape, Inc. and the addressed individual or entity. If you have received this email in error please delete it. Information in this email may be subject to the Privacy Act of 1974 and any unauthorized review, use, disclosure, or distribution is strictly prohibited. Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of the company. -- Free Next-Gen Firewall Hardware
[WiX-users] Thinking about modifying msiengine.cpp...
We are thinking about modifying the MsiEngineComcatProperties() to allow optional handling of MSINEWINSTANCE=1 on Uninstall. Optional meaning - on uninstall we would exclude this from the parameters so that msiexec.exe will unistall the transform. We are using a Multi-Transform msi and need to use the MSINEWINSTANCE=1 on Install. However using WIX, we have not found any means to exclude the msiProperty MSINEWINSTANCE=1 from the Chain on uninstall. If the parameter MSINEWINSTANCE=1 is defined, msiexec.exe /x will fail. Any comments? Thanks in advance. - - jon -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Thinking-about-modifying-msiengine-cpp-tp7583572.html Sent from the wix-users mailing list archive at Nabble.com. -- Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] C# Custom Actions - Cannot Trace
MMsiBreak worked... Thanks Also for some reason having my PDB in the compilation folder was not enough, even though my symbol paths were pointing to the correct location. To get my break point to trigger I had to copy my PDB to the Windows\Installer\MSI63CB.tmp- folder which is where the DLLs are temporally extracted when running the MSI and manually reload the symbols. Unit Testing: Fully agree with you that the code should be unit tested before. This exercise I am doing is simply learning the ins and outs of writing MSis using WIX and various possibilities Thanks for the tips they are always more than welcomed -Original Message- From: Christopher Painter [mailto:chr...@iswix.com] Sent: February-13-2013 4:56 PM To: General discussion for Windows Installer XML toolset.; wix-users@lists.sourceforge.net Subject: Re: [WiX-users] C# Custom Actions - Cannot Trace For C# using DTF it's MMsiBreak. For C/C++ it's MsiBreak. Also you have to restart the machine after setting the env var for the service control manager to pick up the environment change and pass it along to the Windows Installer service. I've debugged many DTF custom actions it's entirely possible to attach a debugger to the messagebox. That said, I find it easier to unit test the class and then create the custom action class as a very thin veneer around it. Testing inside MSI's is just too much friction for my taste. From: Marc Beaudry mbeau...@matrox.com Sent: Wednesday, February 13, 2013 3:36 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] C# Custom Actions - Cannot Trace I am learning to use wix and have come across an issue that doesn't seem to make sense to me. I have created 2 CustomActions one in c++ and one in c#. (Purely for experimental purposes) Both CAs simply contain a MessageBox. (To prove they are being called). And both are called correctly. The difference between the two is I can trace the C++ one but not the C# one. I use attach to process in both cases, but the c# one does not recognize its PDB. Here is what I have tried so far: - Used MSIBreak, nothing happens. But found posts of this issue with Windows 7 not working very well - Tried this too, which should be the proper way to do this but I get nothing. Record record = new Record(2); record[0] = [1]; record[1] = My MSI Message; session.Message(InstallMessage.Info, record); I have searched without any success, I am convinced this is something obvious I am not seeing. How do you attach to a process to be able to trace a c# CA. My message box according to the debugger is running through Run32dll as expected. Thanks for the advice Marc -- Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] [SPAM] Re: Thinking about modifying msiengine.cpp...
This is a better conversation for wix-d...@lists.sourceforge.net Short answer: this is something a custom BA could handle. Supporting instance transforms is a much bigger problem than just setting MSINEWINSTANCE. If you'd like to discuss how to add support for multiple instances to Burn, let's continue on wix-devs. On Thu, Feb 14, 2013 at 5:57 AM, jeamis jonathan.a...@intergraph.comwrote: We are thinking about modifying the MsiEngineComcatProperties() to allow optional handling of MSINEWINSTANCE=1 on Uninstall. Optional meaning - on uninstall we would exclude this from the parameters so that msiexec.exe will unistall the transform. We are using a Multi-Transform msi and need to use the MSINEWINSTANCE=1 on Install. However using WIX, we have not found any means to exclude the msiProperty MSINEWINSTANCE=1 from the Chain on uninstall. If the parameter MSINEWINSTANCE=1 is defined, msiexec.exe /x will fail. Any comments? Thanks in advance. - - jon -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Thinking-about-modifying-msiengine-cpp-tp7583572.html Sent from the wix-users mailing list archive at Nabble.com. -- Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] [SPAM] Re: msi.dll crashes during transaction.Commit()
Haven't heard many good things about the multi-package transaction support
from MSI. We don't use it in Burn because of bugs reported. You might ask
the Windows Installer team if this is another known issue.
On Wed, Feb 13, 2013 at 11:01 PM, Anton Reyes anton.re...@emerson.comwrote:
Hello Guys,
We have a very intermittent bug in the installer that we are developing.
We have a bootstrapper that uses WiX 3.5 and has the following code:
/var transactionSession = new Transaction(ANTON,
TransactionAttributes.None);
foreach (var msiPackage in msiPackageList)
{
Installer.InstallProduct(msiPackage, string.Empty);
}
transactionSession.Commit();
transactionSession.Close();/
This simply creates a transaction session, installs several msis from the
list, and then commits the transaction. However in some cases, msi.dll
crashes during the transaction Commit() call.
*Exception message in transaction.Commit:*
/The Windows Installer Service could not be accessed. This can occur if the
Windows Installer is not correctly installed. Contact your support
personnel
for assistance./
*Event logs:*
/Faulting application name: msiexec.exe, version: 5.0.7601.17514, time
stamp: 0x4ce792c4
Faulting module name: msi.dll, version: 5.0.7601.17514, time stamp:
0x4ce7b902
Exception code: 0xc005
Fault offset: 0x00027b88
Faulting process id: 0xe0c
Faulting application start time: 0x01cd4a967dd25cb4
Faulting application path: C:\Windows\system32\msiexec.exe
Faulting module path: C:\Windows\system32\msi.dll
Report Id: 756b0d09-b68b-11e1-86f9-001b21740788/
All the MSIs are created from InstallShield basic msi project. Any ideas
what might be causing this?
Your help is appreciated guys :)
Cheers,
Anton
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/msi-dll-crashes-during-transaction-Commit-tp7583567.html
Sent from the wix-users mailing list archive at Nabble.com.
--
Free Next-Gen Firewall Hardware Offer
Buy your Sophos next-gen firewall before the end March 2013
and get the hardware for free! Learn more.
http://p.sf.net/sfu/sophos-d2d-feb
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
Free Next-Gen Firewall Hardware Offer
Buy your Sophos next-gen firewall before the end March 2013
and get the hardware for free! Learn more.
http://p.sf.net/sfu/sophos-d2d-feb
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] [SPAM] Re: Fragments and Binary elements...
That work around adds an empty Component. An empty Component could cause issues later when repairing which can create issues with upgrading or patching. Can you provide more information about why the Binary elements were referenced automatically? How were those Binary elements used? On Wed, Feb 13, 2013 at 8:01 AM, Tristen Fielding tfield...@tradestation.com wrote: Thanks for your feedback. We are using Wix3.5 (currently looking at moving to 3.7). Unfortunately, using BinaryRef caused an error with candle. However, we tried adding a empty Component to the fragment file and then referenced the dummy component from within the master.wxs file, which forced everything else to be included. This work-a-round worked perfectly. Tristen Fielding -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Wednesday, February 13, 2013 6:06 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Fragments and Binary elements... Your last approach is correct. In general, you: Place resources in a fragment in a separate file. Add the file to the project. Reference resources from your main wxs file (or any wxs file that it already references) using an xxxRef. When candle runs, it compiles the wxs file into a wixobj because it is in the project. When light runs, it will see the ref to the fragment and pull in the relevant wixobj created by candle. FragmentRefs are deprecated - just reference the fragment contents. It sounds like you're doing it right. You might have made a mistake somewhere. Try it with a minimal project if necessary to see how it works. -Original Message- From: Tristen Fielding [mailto:tfield...@tradestation.com] Sent: 12 February 2013 22:55 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Fragments and Binary elements... We have a very large wix project and we would like to break it apart. One of the things we would like to do is move several of our Binary element to a fragment but we can't seem to figure out how to make it work. We have something like define in the master.wxs file: Binary Id=WixUI_Bmp_Dialog SourceFile=$(var.MEDIAPATH)\side_panel.bmp / Binary Id=WixUI_Bmp_Banner SourceFile=$(var.MEDIAPATH)\WizardHeader.bmp / Binary Id=WixUI_Bmp_BannerJpn SourceFile=$(var.MEDIAPATH)\WizardHeaderJpn.bmp / Binary Id=WixUI_Bmp_Footer SourceFile=$(var.MEDIAPATH)\WizardFooter.bmp / Binary Id=FirstProgressBMP SourceFile=$(var.MEDIAPATH)\1_awards12_A.bmp / Binary Id=SecondProgressBMP SourceFile=$(var.MEDIAPATH)\2_awards12_B.bmp / Binary Id=ThirdProgressBMP SourceFile=$(var.MEDIAPATH)\3_awards12_C.bmp / Binary Id=FourthProgressBMP SourceFile=$(var.MEDIAPATH)\4_awards12_D.bmp / So we tried simply to move these definition into a new file and wrapped them with a Fragment element. When we built the project the project didn't complain but the binaries weren't in the binaries table. So, we then tried to reference these elements using BinaryRef and FragmentRef but we got error instead. What is the right way to reference these Binary elements in the master.wxs file? Thanks. Tristen Fielding Sr. Software Developer / Program Lead TradeStation Group, Inc. http://www.TradeStation.comhttp://www.tradestation.com/ 8050 SW 10th Street, Suite 2000 Plantation, FL 33324 Tel. 954.652.7320 Fax 954.652.5320 TradeStation Group, Inc. is the parent company of four operating subsidiaries, TradeStation Securities, Inc. (Member NYSE, FINRA, SIPC and NFA), IBFX, Inc. (Member NFA), TradeStation Technologies, Inc., a trading software and subscription company, and TradeStation Europe Limited, a United Kingdom, FSA-authorized introducing brokerage firm. None of these companies provides trading or investment advice, recommendations or endorsements of any kind. The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer. Forex products and services are offered by TradeStation Forex, a division of IBFX, Inc. - - Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users SDL PLC confidential, all rights reserved. If you are not the intended recipient of this mail SDL requests and requires that you
Re: [WiX-users] Finding out the number of cores during install?
I dislike depending on environment variables if there is an OS API call avaliable. I just don't trust that env vars aren't tweaked by a human. smlie/ It does seem like something that could be added next to the OsInfo custom action. Maybe HardwareInfo? Wouldn't be hard to add if you already know how to query the OS for cores. If interested, please start a thread on wix-devs and we can point anyone interested in the right direction. On Thu, Feb 14, 2013 at 2:15 AM, Rob Hamflett rob_hamfl...@sn.scee.netwrote: You can get into all sorts of pain identifying logical cores vs physical cores, but the quick way is to just look at the NUMBER_OF_PROCESSORS environment variable. Rob On 13/02/2013 18:22, Stephen Turner wrote: Hi During the install of our product we need to know how many cores the CPU has. Does Wix have this capability?. Thanks - Stephen Turner AudioScience, Inc. -- Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb -- Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] problem on setting passing selected feature from burn to msi
Don't use ADDLOCAL or any of those other properties to control feature
states. It won't work out well in the end. Instead, EnableFeatureSelection
on your MsiPackage then use the Feature callbacks from Burn to control
Feature states.
On Wed, Feb 13, 2013 at 11:04 PM, Nan Zang naz...@microsoft.com wrote:
I think I found the issue.
In bundle msipackage definition I need to define the following. Property
to make it work
msiproperty name=ADDLOCAL value=[ADDLOCAL]/
Sent from my Windows Phone
From: Nan Zangmailto:naz...@microsoft.com
Sent: 2/13/2013 7:15 PM
To: General discussion for Windows Installer XML toolset. (
wix-users@lists.sourceforge.net)mailto:wix-users@lists.sourceforge.net
Subject: [WiX-users] problem on setting passing selected feature from burn
to msi
My MSI has two dummy feature as listed below.
Feature Id=FULLPRODUCTION Title=RMSSetupInstaller
ComponentGroupRef Id=ProductComponents /
/Feature
Feature Id=ADMINCONFIGURATIONTOOL Title=RMSAdminInstaller
ComponentGroupRef Id=AdminComponents /
/Feature
And I am using customize UI to collect user feature selection, then pass
it into through Engine by using following code
this.Bootstrapper.Engine.StringVariables[ADDLOCAL] =
featureList;
this.Bootstrapper.Engine.Plan(LaunchAction.Install);
This is my log, the addlocal variable doesn't seem work. Anything I am
missing here? Thank you for help.
[3B40:1788][2013-02-13T19:02:26]: Detected package: NetFX40, state:
Present, cached: None
[3B40:1788][2013-02-13T19:02:26]: Detected package:
RMSSetupInstallationPackageId, state: Absent, cached: None
[3B40:1788][2013-02-13T19:02:26]: Detected package:
RMSSetupInstallationPackageId, feature: FULLPRODUCTION, state: Absent
[3B40:1788][2013-02-13T19:02:26]: Detected package:
RMSSetupInstallationPackageId, feature: ADMINCONFIGURATIONTOOL, state:
Absent
[3B40:1788][2013-02-13T19:02:26]: Detect complete, result: 0x0
[3B40:25E8][2013-02-13T19:02:38]: Add property name ADDLOCAL with
valueADMINCONFIGURATIONTOOL
[3B40:25E8][2013-02-13T19:02:38]: Setting string variable 'ADDLOCAL' to
value 'ADMINCONFIGURATIONTOOL'
[3B40:1788][2013-02-13T19:02:38]: Plan 2 packages, action: Install
[3B40:1788][2013-02-13T19:02:38]: Skipping dependency registration on
package with no dependency providers: NetFX40
[3B40:1788][2013-02-13T19:02:38]: Plan 2 msi features for package:
RMSSetupInstallationPackageId
[3B40:1788][2013-02-13T19:02:38]: Planned feature: FULLPRODUCTION, state:
Absent, default requested: Unknown, ba requested: Unknown, execute action:
None, rollback action: None
[3B40:1788][2013-02-13T19:02:38]: Planned feature: ADMINCONFIGURATIONTOOL,
state: Absent, default requested: Unknown, ba requested: Unknown, execute
action: None, rollback action: None
[3B40:1788][2013-02-13T19:02:38]: Setting string variable
'WixBundleRollbackLog_RMSSetupInstallationPackageId' to value
'e:\wix\Dev\wix37\setup_0_RMSSetupInstallationPackageId_rollback.log'
[3B40:1788][2013-02-13T19:02:38]: Setting string variable
'WixBundleLog_RMSSetupInstallationPackageId' to value
'e:\wix\Dev\wix37\setup_0_RMSSetupInstallationPackageId.log'
[3B40:1788][2013-02-13T19:02:38]: Planned package: NetFX40, state:
Present, default requested: Present, ba requested: Present, execute: None,
rollback: None, cache: No, uncache: No, dependency: None
[3B40:1788][2013-02-13T19:02:38]: Planned package:
RMSSetupInstallationPackageId, state: Absent, default requested: Present,
ba requested: Present, execute: Install, rollback: Uninstall, cache: Yes,
uncache: Yes, dependency: Register
[3B40:1788][2013-02-13T19:02:38]: Planned related bundle:
{4d72440b-3501-4b0c-9ee3-2fae6b7e4716}, type: Upgrade, default requested:
None, ba requested: None, execute: None, rollback: None, dependency: None
[3B40:1788][2013-02-13T19:02:38]: Planned related bundle:
{63379848-f823-4d73-9364-83bebc1528b2}, type: Upgrade, default requested:
None, ba requested: None, execute: None, rollback: None, dependency: None
[3B40:1788][2013-02-13T19:02:38]: Planned related bundle:
{886235b4-2f08-4c05-916f-d75266a07525}, type: Upgrade, default requested:
None, ba requested: None, execute: None, rollback: None, dependency: None
[3B40:1788][2013-02-13T19:02:38]: Planned related bundle:
{f08b430f-3d9c-4d8e-a160-708f9be5827e}, type: Upgrade, default requested:
None, ba requested: None, execute: None, rollback: None, dependency: None
[3B40:1788][2013-02-13T19:02:38]: Plan complete, result: 0x0
[3B40:1788][2013-02-13T19:02:38]: Apply begin
[3554:1888][2013-02-13T19:02:38]: Creating a system restore point.
[3554:1888][2013-02-13T19:02:38]: System restore disabled, system restore
point not created.
[3554:1888][2013-02-13T19:02:38]: Caching bundle from:
'C:\Users\nazang\AppData\Local\Temp\{34d831eb-4e21-4fed-9502-58ee48298d6f}\.be\BootstrapperSetup.exe'
[WiX-users] [SPAM] Re: problem with wix 3.7 and vs 2008
FYI: bug is already opened. On Wed, Feb 6, 2013 at 11:15 PM, georg.kelle...@lfu.bayern.de wrote: Hi, thanks. that solved my problem. Now all works fine. Georg -Ursprüngliche Nachricht- Von: jlau1269 [mailto:jlau1...@gmail.com] Gesendet: Donnerstag, 7. Februar 2013 05:16 An: wix-users@lists.sourceforge.net Betreff: Re: [WiX-users] problem with wix 3.7 and vs 2008 I believe it's a known problem, you need to add this to your project file, RunWixToolsOutOfProctrue/RunWixToolsOutOfProc, check this post for additional info WiX 3.7 with vs2008 http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Wix-3-7-Woes-with-VS2008-td7582558.html -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/problem-with-wix-3-7-and-vs-2008-tp7583349p7583400.html Sent from the wix-users mailing list archive at Nabble.com. -- Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Adding background to burn theme?
I add images as the background all the time. Need more information to understand why yours doesn't work. On Thu, Feb 7, 2013 at 11:33 AM, Bull, Thomas thomas.b...@defensegp.comwrote: I am attempting to add an image that will act as a background for each burn page. If I only define the image in one page it will sometimes work, other times the controls on the page will be overwritten by the image. If I add an image to each Page then no controls appear until they receive focus. Is this a known issue? Is there a way to either add a background image or change the window color to something other than white? -- Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] When is ExecuteFilesInUse invoked for custom .NET bootstrapper
Bug. I found it just yesterday. I haven't opened a bug yet... if you want to do it, feel free. On Mon, Feb 11, 2013 at 8:44 AM, ptr ptrajku...@gmail.com wrote: hey all I am trying to handle all possible error scenarios for my custom bootstrapper. Even if main executable I have installed is running, Bootstrapper.ExecuteFilesInUse is never invoked. How can one test this scenario ? Thanks raj -- Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Heat.exe
Hi i am using below statement for harvesting the web application. %WIX%bin\heat.exe dir $(Wixdest) -cg SCBUDirect -gg -scom -sreg -sfrag -srd -dr INSTALLLOCATION -var env.Wixdest -out C:\Workspaces\Chatra\SCBUFragment.wxs And when I install the MSI the resulting folders just contain .dll,.pdb,.xml only .If I require everything from published website folder which is the source then how is the Heat cmd look like. Thanks in Advance Chatra -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Heat-exe-tp7583483p7583583.html Sent from the wix-users mailing list archive at Nabble.com. -- Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Burn: Prerequisites on Windows 2012 Server and the Server Manager requirement
I think the issue is actually that Burn is putting the full path to the executable to prevent PATH searching and opening a potential security vulnerability. Full paths are always safer. On Tue, Feb 5, 2013 at 1:58 PM, Neil Sleightholm n...@x2systems.com wrote: I think that is probably related to burn being 32 bit and dcim running from 64 bit system folder so the current environment is not passed to the process. May be the code could support expansion of a [SystemFolder64] property. Neil -Original Message- From: Eric Schultz [mailto:eschu...@outercurve.org] Sent: 05 February 2013 20:46 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Burn: Prerequisites on Windows 2012 Server and the Server Manager requirement For me, running dism.exe only worked if I put in the full path. Not sure why that is. Eric On Tue, Feb 5, 2013 at 2:22 PM, Neil Sleightholm n...@x2systems.com wrote: DCIM should be on the path so adding C:\Windows\system32 shouldn't be necessary. -Original Message- From: Hoover, Jacob [mailto:jacob.hoo...@greenheck.com] Sent: 04 February 2013 22:09 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Burn: Prerequisites on Windows 2012 Server and the Server Manager requirement Depending on C:\Windows\system32 would break on non-default installs... -Original Message- From: Neil Sleightholm [mailto:n...@x2systems.com] Sent: Monday, February 04, 2013 3:59 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Burn: Prerequisites on Windows 2012 Server and the Server Manager requirement Because burn will only run exes packaged in a release. It won't run arbitrary exes. -Original Message- From: Marc Fauser [mailto:marc.fau...@gmail.com] Sent: 04 February 2013 21:37 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Burn: Prerequisites on Windows 2012 Server and the Server Manager requirement On 2013-02-04 22:29, Eric Schultz wrote: All, I've created a simple ExeRunner application that can be embedded into your bundle and then be called to run a command on the destination computer. To install .NET Framework 3.5 and less on Win 8, the entire command line would be: ExeRunner.exe C:\Windows\system32\dism.exe /online /norestart /enable-feature /featurename:netfx3 If the inner command fails, it's error code is returned. If you can call ExeRunner.exe, why can't you call dism.exe directly? Marc -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_jan ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Eric Schultz, Developer Advocate, Outercurve Foundation http://www.outercurve.org eschu...@outercurve.org cell: 920-539-0404 skype: ericschultzwi @EricOutercurve -- Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] [SPAM] Re: Issue with uninstalling a Multi-Transforms Msi with MSNEWINSTANCE set
Multi-instance transforms are very particular. The external driver has to manage quite a bit. On Wed, Feb 6, 2013 at 1:06 PM, jeamis jonathan.a...@intergraph.com wrote: Does anyone know why the msiexec.exe fails because the MSINEWINSTANCE=1 happens to be on the command line? I assume that the msiexec.exe is involved in a wix installation as well. Is there a way for the multi - transform msi to regulate this or only the boot strapper? Thanks - Jon - - jon -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Issue-with-uninstalling-a-Multi-Transforms-Msi-with-MSNEWINSTANCE-set-tp7583210p7583397.html Sent from the wix-users mailing list archive at Nabble.com. -- Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Help with Wix custom managed bootstrapper
Take a look at the Burn log file and see if the related bundles are finding each other. You should see stuff in the log file saying the new bundle is upgrading the old bundle. On Mon, Feb 4, 2013 at 12:06 PM, Kristian Jaksch kristian.jak...@gmail.comwrote: Hello, I'm still struggling with the custom managed bootstrapper application. I've built a sample from scratch by looking at some other examples but I'm still having issues with getting it to work as I want. It is the same problem I've had before: If I first build the bootstrapper and install it everything works as expected. The bundle is added to ARP. But if I change version of the bundle to something higher, for example from 1.0.0.0 to 2.0.0.0 and rebuild and try to install again it does not work as expected. What happens when I'm trying to install again is that a new bootstrapper window is launched when calling Engine.Apply(IntPtr.Zero) and if I click install in that window the new version is installed side by side with the previous version in ARP. What I expect to happen is that if I already have a previous version installed and then install a new version, the new version will replace the old version in ARP and there should be no second installer window popping up when trying to install the new version. Can anyone explain why this is happening? This time I've put together a sample application containing the minimum to perform an installation. The source is available here: https://docs.google.com/file/d/0B71bOgcmv_iwcmlwUGlPaFlWQU0/edit?usp=sharing If someone could have a look at why this doesn't behave as expected I would really appreciate it! Thanks for help! /Kristian -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_jan ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] [SPAM] Re: TopBanner bitmap looks lower resolution
I think a bug was opened recently that the wixstdba is not handling scaling very well. On Thu, Feb 7, 2013 at 3:20 PM, StevenOgilvie sogil...@msn.com wrote: Hi folks, I am using WIX 3.7... I have replaced the default BMP for our companies version: WixVariable Overridable=yes Id='WixUIBannerBmp' Value=$(var.resourcePath)\TMCTopBanner.bmp/ and WixVariable Overridable=yes Id='WixUIDialogBmp' Value=$(var.resourcePath)\TMCSide.bmp/ I am using Windows 7 Enterprise 64 bit, when running the resolution at Smaller 100% (Control Panel - Appearance and Personalization - Display) the top/side banner looks great... However when running the display at Medium 125% the bmp looks like a lower resolution it is not smooth. I am using the proper sizing and resolution, it is: Top bitmap Size: 493 x 58 Resolution: 96 DPI Type: 24 bit Bitmap Side bitmap Size: 493 x 309 Resolution: 96 DPI Type: 24 bit Bitmap Has anyone else experienced something like this? thanks, Steve -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/TopBanner-bitmap-looks-lower-resolution-tp7583423.html Sent from the wix-users mailing list archive at Nabble.com. -- Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Id for Component and File
If you see a crash in the WiX toolset, please open a bug with the error message and the callstack that is dumped to console. On Mon, Feb 11, 2013 at 8:03 AM, Peter Shirtcliffe pshirtcli...@sdl.comwrote: The default Id thing was a recent addition. Wix 3.6 maybe. Your light error sounds like a possible Wix bug. Its cropped up on the list before but that person turned off validation to work around it. You could validate interactively with orca or instEd which aren't based on the Wix code. That's what we do to reduce build times - validation is only needed occasionally, if the installer changes. Adding a bug with a minimal project to reproduce would help it get fixed too. -Original Message- From: Sam Boman [mailto:s...@samb.se] Sent: 11 February 2013 15:47 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Id for Component and File Ok, I also found the example in the documentation which uses same Id for Component and File... http://wix.sourceforge.net/manual-wix3/add_a_file.htm But they (Id's) seems to be required, so I can't skip them. Also, the Error: LGHT0216 Can I get a better / more detailed description? I have tried to set -val for the Light.exe And use Smoke.exe to validate, but I just got the same message. //Sam - - Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users SDL PLC confidential, all rights reserved. If you are not the intended recipient of this mail SDL requests and requires that you delete it without acting upon or copying any of its contents, and we further request that you advise us. SDL PLC is a public limited company registered in England and Wales. Registered number: 02675207. Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6 7DY, UK. -- Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] [SPAM] Re: Gracefully skip elevated packages for non-admin in bundle
Actually, it's the other way around. If there are any per-user packages the Bundle will be per-user. This scenario will work, you'll just have to find a different way of detecting if the bundle is elevatable than Privileged variable. The Privileged variable (and MSI property) have a long history that make them quite interesting. On Tue, Feb 12, 2013 at 12:51 AM, Yawar Khan yawar.k...@live.com wrote: filed at https://sourceforge.net/p/wix/feature-requests/723/ -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Gracefully-skip-elevated-packages-for-non-admin-in-bundle-tp7583426p7583496.html Sent from the wix-users mailing list archive at Nabble.com. -- Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] 2 bundles sharing some msi's behaving strange on xp
Never seen such behavior. Can you try using procmon to watch the registry and see what is deleting the key? On Tue, Feb 12, 2013 at 7:02 AM, Ogrodowski, Sabine (ehem. Frauenhoffer) sabine.ogrodow...@haufe-lexware.com wrote: Another problem I'm currently struggling with: I create two bundles, that have some msi's in common. If I install both on Win 7 and uninstall 1 of them, the shared msi's stay installed. Great. On XP however, the shared msi's get uninstalled too. We digged a bit deeper and found out, that sometimes the registry key hkcr\installer\dependencies completely gets deleted during the second installer's installation process which then leads to the result, that only the second product is registered in this registry key. When we then uninstall the second product, there is no further dependency on the shared msi's found, and they get uninstalled. I tested on Windows XP Profesional (32 bit) SP 3. Has anyone seen this strange behavior before? Is there some workaround? -- Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] [SPAM] Re: Creating a bootstrap application and need a more simple UI
Exactly. I've been massively customizing the UI for customers the last two weeks such that it looks beautiful (some big companies have some really good design teams smile/). The default is bare because I created it and anyone that knows me will tell you that I have near zero design skills. Would be great if someone with awesome design skills wanted to make the default UI look prettier. smile/ On Tue, Feb 12, 2013 at 3:41 AM, Pally Sandher pally.sand...@iesve.comwrote: Download the WiX sources, find the HyperlinkTheme.xml file modify it to your needs. You can then supply it using bal:WixStandardBootstrapperApplication LicenseUrl= SuppressOptionsUI=yes LogoFile=yourlogo.jpg ThemeFile= HyperlinkTheme.xml / Works for me. Palbinder Sandher Software Platform Engineer T: +44 (0) 141 945 8500 F: +44 (0) 141 945 8501 http://www.iesve.com **Design, Simulate + Innovate with the Virtual Environment** Integrated Environmental Solutions Limited. Registered in Scotland No. SC151456 Registered Office - Helix Building, West Of Scotland Science Park, Glasgow G20 0SP Email Disclaimer -Original Message- From: joshh [mailto:joshuadeanh...@gmail.com] Sent: 11 February 2013 20:47 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Creating a bootstrap application and need a more simple UI Bruce, That is really close to what I am looking for. The only improvement I can think of would be to reduce the size and have a short message. And maybe a background logo like the wix ui can have. Thanks! -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Creating-a-bootstrap-application-and-need-a-more-simple-UI-tp7583473p7583478.html Sent from the wix-users mailing list archive at Nabble.com. -- Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Explanation of Microsoft.Tools.WindowsInstallerXml.Bootstrapper.Display
Embedded is when the Bundle is launched as a child of another Bundle (like during Upgrade) and Passive is when the /passive switch is passed on the command-line. On Tue, Feb 12, 2013 at 2:26 PM, ptr ptrajku...@gmail.com wrote: Hey all Does anybody know when is Display.Embedded and Display.Passive used for bootstrapper ? Is this documented somewhere ? Thanks raj -- Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] [SPAM] Re: Detect Complete- freezed
Engine is waiting for the BA to do something. On Wed, Feb 13, 2013 at 3:09 AM, Kannan24 skan...@syncfusion.com wrote: Hi, Some times uninstallation works, but second setup installation does not started without uninstall first setup or restart. Could you provide any solution for this? Thanks, Kannan -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Detect-Complete-freezed-tp7583517p7583546.html Sent from the wix-users mailing list archive at Nabble.com. -- Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] [SPAM] Re: questions on bootstrapper
I do think there is a feature request out ther for the preq BA to support
installing more than one prerequisite package. Not implemented today.
On Wed, Feb 13, 2013 at 7:00 AM, Hoover, Jacob
jacob.hoo...@greenheck.comwrote:
Burn only fails back to the MBA prerequisite BA if it can't create the
AppDomain it needs. Look at BootstrapperApplicationCreate in
src\ext\BalExtension\mba\host\host.cpp.
Introducing additional dependencies for a BA seems wrong to me. If you are
using this custom dependency to modify machine state, you could accomplish
this by adding the dependency earlier in the chain and having a later
MsiPackage that could use custom actions to interact with the newly
installed dependency.
-Original Message-
From: Nan Zang [mailto:naz...@microsoft.com]
Sent: Wednesday, February 13, 2013 1:17 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] questions on bootstrapper
After some investigation, it seemsdefine Id=WixMbaPrereqPackageId
will accomplish what I need, however, I cannot get it work.
?xml version=1.0 encoding=UTF-8?
Wix xmlns=http://schemas.microsoft.com/wix/2006/wi; xmlns:util=
http://schemas.microsoft.com/wix/UtilExtension; xmlns:bal=
http://schemas.microsoft.com/wix/BalExtension;
Bundle Name=My Test Application Version=1.0.0.0
Manufacturer=Microsoft UpgradeCode=C82A383C-751A-43B8-90BF-A250F7BC2863
BootstrapperApplicationRef Id=ManagedBootstrapperApplicationHost
Payload SourceFile=..\TestBA\BootstrapperCore.config/
Payload SourceFile=..\TestBA\bin\Release\TestBA.dll/
Payload SourceFile=C:\Program Files (x86)\WiX Toolset
v3.6\SDK\Microsoft.Deployment.WindowsInstaller.dll/
/BootstrapperApplicationRef
Chain
PackageGroupRef Id='OrgIdSignInAssistant' /
MsiPackage
SourceFile=..\DummyInstaller\bin\debug\DummyInstaller.msi
Id=DummyInstallernPackageId Cache=yes Visible=no/
/Chain
/Bundle
Fragment
WixVariable Id=WixMbaPrereqPackageId Value=OrgIdSignInAssistant /
WixVariable Id=WixMbaPrereqLicenseUrl Value=Eula.rtf /
PackageGroup Id=OrgIdSignInAssistant
MsiPackage Id=OrgIdSignInAssistant Cache=no
Compressed=yes Permanent=yes Vital=yes
SourceFile=E:\rmsonline\private\externals\IDCRL\7.250.4303.0\MSI\msoidcrl.msi
/
/PackageGroup
/Fragment
/Wix
This is the log, this is modfied from the sample code. There is no
prerequisite step gets invoked, Anything wrong here?
[1F40:1700][2013-02-12T23:07:48]: Burn v3.6.3303.0, Windows v6.1 (Build
7601: Service Pack 1), path:
C:\Users\nazang\Desktop\RMSSetupBA\BootstrapperSetup\bin\Debug\BootstrapperSetup.exe,
cmdline: '/install /log setup.log /runas:administrator -burn.unelevated
BurnPipe.{F434AAE5-B80D-43FF-8859-670E1B3D483E}
{E175F3B6-186C-445D-A861-3BDC024177A4} 12900'
[1F40:1700][2013-02-12T23:07:48]: Setting string variable 'WixBundleLog'
to value 'e:\wix\Dev\wix37\setup.log'
[1F40:1700][2013-02-12T23:07:48]: Setting string variable
'WixBundleOriginalSource' to value
'C:\Users\nazang\Desktop\RMSSetupBA\BootstrapperSetup\bin\Debug\BootstrapperSetup.exe'
[1F40:1700][2013-02-12T23:07:48]: Setting string variable 'WixBundleName'
to value 'My Test Application'
[1F40:1700][2013-02-12T23:07:48]: Loading managed bootstrapper application.
[1F40:1700][2013-02-12T23:07:49]: Creating BA thread to run asynchronously.
[1F40:3B48][2013-02-12T23:07:49]: Launching custom TestBA UX
[1F40:1700][2013-02-12T23:07:49]: Detect 2 packages
[1F40:1700][2013-02-12T23:07:49]: Detected related bundle:
{4d72440b-3501-4b0c-9ee3-2fae6b7e4716}, type: Upgrade, scope: PerMachine,
version: 1.0.0.0, operation: None
[1F40:1700][2013-02-12T23:07:49]: Detected related bundle:
{63379848-f823-4d73-9364-83bebc1528b2}, type: Upgrade, scope: PerMachine,
version: 1.0.0.0, operation: None
[1F40:1700][2013-02-12T23:07:49]: Detected related bundle:
{886235b4-2f08-4c05-916f-d75266a07525}, type: Upgrade, scope: PerMachine,
version: 1.0.0.0, operation: None
[1F40:1700][2013-02-12T23:07:49]: Detected package: OrgIdSignInAssistant,
state: Absent, cached: None
[1F40:1700][2013-02-12T23:07:49]: Detected package:
DummyInstallernPackageId, state: Present, cached: Complete
[1F40:1700][2013-02-12T23:07:49]: Detect complete, result: 0x0
From: Nan Zang
Sent: Tuesday, February 12, 2013 8:43 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] questions on bootstrapper
Jocob,
Thank you for your detailed answer. I have another question related to
1.
Besides .Net 3.5, I need another dependency (eg. CredUI.msi) for my BA UX.
I need to use this dependency in one of my BA UX. Is there possible I get
it installed automatically before my BAUX gets launched. I tried the
chained package approach, and found the installation of the credUI.msi will
be invoked when the MSI is launched. That doesn't meet my requirement. Is
Re: [WiX-users] [SPAM] Re: Detect Complete- freezed
Hi Rob, Thanks for your reply. I already checked with this, waited around one hour, there is no progress even log file. Its started soon if I restarted the machine. Thanks, Kannan -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Detect-Complete-freezed-tp7583517p7583595.html Sent from the wix-users mailing list archive at Nabble.com. -- Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] [SPAM] Re: [SPAM] Re: Detect Complete- freezed
It looks like you have a custom BA. If that is correct, you'll want to debug your BA. On Thu, Feb 14, 2013 at 9:42 AM, Kannan24 skan...@syncfusion.com wrote: Hi Rob, Thanks for your reply. I already checked with this, waited around one hour, there is no progress even log file. Its started soon if I restarted the machine. Thanks, Kannan -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Detect-Complete-freezed-tp7583517p7583595.html Sent from the wix-users mailing list archive at Nabble.com. -- Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] How do you turn off REPAIR in the boostrapper in ARP or Programs and Features?
Hello, I have noticed that the DisableRepair=yes in the Bundle element in the bootstrapper doesn't work. How do you turn off repair in the bootstrapper? Thanks, Steve -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/How-do-you-turn-off-REPAIR-in-the-boostrapper-in-ARP-or-Programs-and-Features-tp7583597.html Sent from the wix-users mailing list archive at Nabble.com. -- Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] When is ExecuteFilesInUse invoked for custom .NET bootstrapper
I found this issue as well and already opened a bug for it: http://sourceforge.net/p/wix/bugs/3160/ http://sourceforge.net/p/wix/bugs/3160/ -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/When-is-ExecuteFilesInUse-invoked-for-custom-NET-bootstrapper-tp7583469p7583598.html Sent from the wix-users mailing list archive at Nabble.com. -- Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] [SPAM] Re: How do you turn off REPAIR in the boostrapper in ARP or Programs and Features?
Documentation for DisableRepair: DisableRepair YesNoTypemk:@MSITStore:C:\Program%20Files%20(x86)\WiX%20Toolset%20v3.7\doc\WiX.chm::/html/wix_xsd_simple_type_yesnotype.htm This attribute has been deprecated. The WiX.chm is pretty explicit about controling the ARP buttons for a Bundle with DisableModify and DisableRemove On Thu, Feb 14, 2013 at 10:32 AM, StevenOgilvie sogil...@msn.com wrote: Hello, I have noticed that the DisableRepair=yes in the Bundle element in the bootstrapper doesn't work. How do you turn off repair in the bootstrapper? Thanks, Steve -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/How-do-you-turn-off-REPAIR-in-the-boostrapper-in-ARP-or-Programs-and-Features-tp7583597.html Sent from the wix-users mailing list archive at Nabble.com. -- Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] [SPAM] Re: When is ExecuteFilesInUse invoked for custom .NET bootstrapper
Wow, totally blanked on that. sigh/ I expect this will get fixed in v3.8. On Thu, Feb 14, 2013 at 10:38 AM, jhennessey jack.hennes...@hyland.comwrote: I found this issue as well and already opened a bug for it: http://sourceforge.net/p/wix/bugs/3160/ http://sourceforge.net/p/wix/bugs/3160/ -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/When-is-ExecuteFilesInUse-invoked-for-custom-NET-bootstrapper-tp7583469p7583598.html Sent from the wix-users mailing list archive at Nabble.com. -- Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Burn ALLUSERS on the bundle and ALLUSERS on the package
I have a bundle that is installing .NET 4.0 and installing either a 32 bit or
64 bit version of a msi.
The msi that gets installed has a Just Me scope option that sets ALLUSERS to
{}. However this does not work well since it seems that the bundle is set
to perMachine scope so the uninstall feature doesn't work well.
Is there a good way to handle this case?
Some solutions that I thought may work.
1. Write a custom UI and do the ALLUSER dialog there then set the msi
properties.
2. Have the Remove program dialog actually point to the package instead of
the bundle (I have no idea if this is possible or how to do it).
3. ???
What should I do to solve this?
Thanks.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-ALLUSERS-on-the-bundle-and-ALLUSERS-on-the-package-tp7583602.html
Sent from the wix-users mailing list archive at Nabble.com.
--
Free Next-Gen Firewall Hardware Offer
Buy your Sophos next-gen firewall before the end March 2013
and get the hardware for free! Learn more.
http://p.sf.net/sfu/sophos-d2d-feb
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Can't run bundle installer with ManagedBA with TrenMicro office scan
Hello,
I've built a installer using ManagedBA and everything runs and installs fine
without TrendMicro AV. Then with TrendMicroAV installed the installer quits
almost immediately. This is with any version of the AV, free trial for my
test.
I also tried installing just the MSIs with the AV and I get no problems
installing. The bundler just installs two MSIs and possibly .NET if not
present.
Here is the Setup.exe log
[0808:0B9C][2013-02-14T12:31:02]: Burn v3.6.3303.0, Windows v5.1 (Build
2600: Service Pack 3), path: C:\Documents and
Settings\testAdmin\Desktop\Setup.exe, cmdline: ''
[0808:0B9C][2013-02-14T12:31:02]: Setting string variable 'WixBundleLog' to
value 'C:\DOCUME~1\TESTAD~1\LOCALS~1\Temp\Setup_20130214123102.log'
[0808:0B9C][2013-02-14T12:31:02]: Setting string variable
'WixBundleOriginalSource' to value 'C:\Documents and
Settings\testAdmin\Desktop\Setup'
[0808:0B9C][2013-02-14T12:31:02]: Setting string variable 'WixBundleName' to
value 'Setup'
[0808:0B9C][2013-02-14T12:31:03]: Loading managed bootstrapper application.
[0808:0B9C][2013-02-14T12:31:04]: Creating BA thread to run asynchronously.
[0808:0D20][2013-02-14T12:31:04]: Running the UX BA.
[0808:0B9C][2013-02-14T12:31:04]: Detect 4 packages
[0808:0D20][2013-02-14T12:31:04]: Creating a UI.
[0808:0B9C][2013-02-14T12:31:04]: Setting string variable
'NETFRAMEWORK40CLIENT' to value '1'
[0808:0B9C][2013-02-14T12:31:04]: Condition 'NETFRAMEWORK40CLIENT' evaluates
to true.
[0808:0B9C][2013-02-14T12:31:04]: Detected package: NetFx40ClientWeb, state:
Present, cached: None
[0808:0B9C][2013-02-14T12:31:04]: Detected package: Packagex86, state:
Absent, cached: None
[0808:0B9C][2013-02-14T12:31:04]: Detected package: Packagex64, state:
Absent, cached: None
[0808:0B9C][2013-02-14T12:31:04]: Detected package: QPackage, state: Absent,
cached: None
[0808:0B9C][2013-02-14T12:31:04]: ParseCommandLine():
[0808:0B9C][2013-02-14T12:31:04]: Detect complete, result: 0x0
[0808:0B9C][2013-02-14T12:31:07]: Plan 4 packages, action: Install
[0808:0B9C][2013-02-14T12:31:07]: Skipping dependency registration on
package with no dependency providers: NetFx40ClientWeb
[0808:0B9C][2013-02-14T12:31:07]: Condition '(NOT VersionNT64)' evaluates to
true.
[0808:0B9C][2013-02-14T12:31:07]: Setting string variable
'WixBundleRollbackLog_Packagex86' to value
'C:\DOCUME~1\TESTAD~1\LOCALS~1\Temp\Setup_20130214123102_0_Packagex86_rollback.log'
[0808:0B9C][2013-02-14T12:31:07]: Setting string variable
'WixBundleLog_Packagex86' to value
'C:\DOCUME~1\TESTAD~1\LOCALS~1\Temp\Setup_20130214123102_0_Packagex86.log'
[0808:0B9C][2013-02-14T12:31:07]: Condition '(VersionNT64)' evaluates to
false.
[0808:0B9C][2013-02-14T12:31:07]: Setting string variable
'WixBundleRollbackLog_QPackage' to value
'C:\DOCUME~1\TESTAD~1\LOCALS~1\Temp\Setup_20130214123102_1_QPackage_rollback.log'
[0808:0B9C][2013-02-14T12:31:07]: Setting string variable
'WixBundleLog_QPackage' to value
'C:\DOCUME~1\TESTAD~1\LOCALS~1\Temp\Setup_20130214123102_1_QPackage.log'
[0808:0B9C][2013-02-14T12:31:07]: Planned package: NetFx40ClientWeb, state:
Present, default requested: Present, ba requested: Present, execute: None,
rollback: None, cache: No, uncache: No, dependency: None
[0808:0B9C][2013-02-14T12:31:07]: Planned package: Packagex86, state:
Absent, default requested: Present, ba requested: Present, execute: Install,
rollback: Uninstall, cache: Yes, uncache: No, dependency: Register
[0808:0B9C][2013-02-14T12:31:07]: Planned package: Packagex64, state:
Absent, default requested: Absent, ba requested: Absent, execute: None,
rollback: None, cache: No, uncache: No, dependency: None
[0808:0B9C][2013-02-14T12:31:07]: Planned package: QPackage, state: Absent,
default requested: Present, ba requested: Present, execute: Install,
rollback: Uninstall, cache: Yes, uncache: No, dependency: Register
[0808:0B9C][2013-02-14T12:31:07]: Plan complete, result: 0x0
[0808:0B9C][2013-02-14T12:31:07]: Apply begin
[0C0C:0904][2013-02-14T12:31:08]: Creating a system restore point.
[0C0C:0904][2013-02-14T12:31:11]: Created a system restore point.
[0C0C:0904][2013-02-14T12:31:11]: Caching bundle from:
'C:\DOCUME~1\TESTAD~1\LOCALS~1\Temp\{----bbea6bc27533}\.be\Setup.exe'
to: 'C:\Documents and Settings\All Users\Application Data\Package
Cache\{----bbea6bc27533}\Setup.exe'
[0808:0B9C][2013-02-14T12:31:12]: Error 0x800700e8: Failed to write message
type to pipe.
[0808:0B9C][2013-02-14T12:31:12]: Error 0x800700e8: Failed to write send
message to pipe.
[0808:0B9C][2013-02-14T12:31:12]: Error 0x800700e8: Failed to send message
to per-machine process.
[0808:0B9C][2013-02-14T12:31:12]: Error 0x800700e8: Failed to save engine
state in per-machine process.
[0808:0B9C][2013-02-14T12:31:12]: The state file could not be saved, error:
0x12fa04. Continuing...
[0808:05C8][2013-02-14T12:31:16]: Error 0x800700e8: Failed to write message
type to pipe.
[0808:05C8][2013-02-14T12:31:16]: Error 0x800700e8: Failed to write send
message to
[WiX-users] [SPAM] Re: ** SPAM ** [SPAM] Re: How do you turn off REPAIR in the boostrapper in ARP or Programs and Features?
Repair is only supported for MSIs. On Thu, Feb 14, 2013 at 11:55 AM, Steven Ogilvie steven.ogil...@titus.comwrote: Why is disabling Repair not available? That is not mentioned in the WIX help file... -Original Message- From: Rob Mensching [mailto:r...@robmensching.com] Sent: February-14-13 2:10 PM To: General discussion for Windows Installer XML toolset. Subject: ** SPAM **[WiX-users] [SPAM] Re: How do you turn off REPAIR in the boostrapper in ARP or Programs and Features? Documentation for DisableRepair: DisableRepair YesNoTypemk:@MSITStore :C:\Program%20Files%20(x86)\WiX%20Toolset%20v3.7\doc\WiX.chm::/html/wix_xsd_simple_type_yesnotype.htm This attribute has been deprecated. The WiX.chm is pretty explicit about controling the ARP buttons for a Bundle with DisableModify and DisableRemove On Thu, Feb 14, 2013 at 10:32 AM, StevenOgilvie sogil...@msn.com wrote: Hello, I have noticed that the DisableRepair=yes in the Bundle element in the bootstrapper doesn't work. How do you turn off repair in the bootstrapper? Thanks, Steve -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/How-do-y ou-turn-off-REPAIR-in-the-boostrapper-in-ARP-or-Programs-and-Features- tp7583597.html Sent from the wix-users mailing list archive at Nabble.com. -- Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] [SPAM] Re: Burn ALLUSERS on the bundle and ALLUSERS on the package
If the MSI package is per-user, the Bundle will be per-user as well.
On Thu, Feb 14, 2013 at 11:54 AM, joshh joshuadeanh...@gmail.com wrote:
I have a bundle that is installing .NET 4.0 and installing either a 32 bit
or
64 bit version of a msi.
The msi that gets installed has a Just Me scope option that sets ALLUSERS
to
{}. However this does not work well since it seems that the bundle is set
to perMachine scope so the uninstall feature doesn't work well.
Is there a good way to handle this case?
Some solutions that I thought may work.
1. Write a custom UI and do the ALLUSER dialog there then set the msi
properties.
2. Have the Remove program dialog actually point to the package instead of
the bundle (I have no idea if this is possible or how to do it).
3. ???
What should I do to solve this?
Thanks.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-ALLUSERS-on-the-bundle-and-ALLUSERS-on-the-package-tp7583602.html
Sent from the wix-users mailing list archive at Nabble.com.
--
Free Next-Gen Firewall Hardware Offer
Buy your Sophos next-gen firewall before the end March 2013
and get the hardware for free! Learn more.
http://p.sf.net/sfu/sophos-d2d-feb
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
Free Next-Gen Firewall Hardware Offer
Buy your Sophos next-gen firewall before the end March 2013
and get the hardware for free! Learn more.
http://p.sf.net/sfu/sophos-d2d-feb
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] ** SPAM ** [SPAM] Re: ** SPAM ** [SPAM] Re: How do you turn off REPAIR in the boostrapper in ARP or Programs and Features?
Okay I am confused (or dense) If it is NOT supported in the bootstrapper, then WHY is there a button repair in the bootstrapper when I goto ARP and select my product (click Uninstall) the repair button as well as Uninstall/Close is present... Bundle Name=$(var.ProductName) Version=$(var.ProductVersion) Manufacturer=$(var.ProductCompany) UpgradeCode=a GUID DisableModify=yes DisableRemove=no HelpTelephone=555-555- How do I disable the repair button... Steve -Original Message- From: Rob Mensching [mailto:r...@robmensching.com] Sent: February-14-13 4:10 PM To: General discussion for Windows Installer XML toolset. Subject: ** SPAM **[WiX-users] [SPAM] Re: ** SPAM ** [SPAM] Re: How do you turn off REPAIR in the boostrapper in ARP or Programs and Features? Repair is only supported for MSIs. On Thu, Feb 14, 2013 at 11:55 AM, Steven Ogilvie steven.ogil...@titus.comwrote: Why is disabling Repair not available? That is not mentioned in the WIX help file... -Original Message- From: Rob Mensching [mailto:r...@robmensching.com] Sent: February-14-13 2:10 PM To: General discussion for Windows Installer XML toolset. Subject: ** SPAM **[WiX-users] [SPAM] Re: How do you turn off REPAIR in the boostrapper in ARP or Programs and Features? Documentation for DisableRepair: DisableRepair YesNoTypemk:@MSITStore :C:\Program%20Files%20(x86)\WiX%20Toolset%20v3.7\doc\WiX.chm::/html/wi x_xsd_simple_type_yesnotype.htm This attribute has been deprecated. The WiX.chm is pretty explicit about controling the ARP buttons for a Bundle with DisableModify and DisableRemove On Thu, Feb 14, 2013 at 10:32 AM, StevenOgilvie sogil...@msn.com wrote: Hello, I have noticed that the DisableRepair=yes in the Bundle element in the bootstrapper doesn't work. How do you turn off repair in the bootstrapper? Thanks, Steve -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/How-do -y ou-turn-off-REPAIR-in-the-boostrapper-in-ARP-or-Programs-and-Feature s- tp7583597.html Sent from the wix-users mailing list archive at Nabble.com. -- Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] [SPAM] Re: ** SPAM ** [SPAM] Re: ** SPAM ** [SPAM] Re: How do you turn off REPAIR in the boostrapper in ARP or Programs and Features?
Oh, you mean the Repair button in the WiX Standard Bootstrapper Application? That is controlled by the WixStandardBootstrapperApplication element. On Thu, Feb 14, 2013 at 1:19 PM, Steven Ogilvie steven.ogil...@titus.comwrote: Okay I am confused (or dense) If it is NOT supported in the bootstrapper, then WHY is there a button repair in the bootstrapper when I goto ARP and select my product (click Uninstall) the repair button as well as Uninstall/Close is present... Bundle Name=$(var.ProductName) Version=$(var.ProductVersion) Manufacturer=$(var.ProductCompany) UpgradeCode=a GUID DisableModify=yes DisableRemove=no HelpTelephone=555-555- How do I disable the repair button... Steve -Original Message- From: Rob Mensching [mailto:r...@robmensching.com] Sent: February-14-13 4:10 PM To: General discussion for Windows Installer XML toolset. Subject: ** SPAM **[WiX-users] [SPAM] Re: ** SPAM ** [SPAM] Re: How do you turn off REPAIR in the boostrapper in ARP or Programs and Features? Repair is only supported for MSIs. On Thu, Feb 14, 2013 at 11:55 AM, Steven Ogilvie steven.ogil...@titus.comwrote: Why is disabling Repair not available? That is not mentioned in the WIX help file... -Original Message- From: Rob Mensching [mailto:r...@robmensching.com] Sent: February-14-13 2:10 PM To: General discussion for Windows Installer XML toolset. Subject: ** SPAM **[WiX-users] [SPAM] Re: How do you turn off REPAIR in the boostrapper in ARP or Programs and Features? Documentation for DisableRepair: DisableRepair YesNoTypemk:@MSITStore :C:\Program%20Files%20(x86)\WiX%20Toolset%20v3.7\doc\WiX.chm::/html/wi x_xsd_simple_type_yesnotype.htm This attribute has been deprecated. The WiX.chm is pretty explicit about controling the ARP buttons for a Bundle with DisableModify and DisableRemove On Thu, Feb 14, 2013 at 10:32 AM, StevenOgilvie sogil...@msn.com wrote: Hello, I have noticed that the DisableRepair=yes in the Bundle element in the bootstrapper doesn't work. How do you turn off repair in the bootstrapper? Thanks, Steve -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/How-do -y ou-turn-off-REPAIR-in-the-boostrapper-in-ARP-or-Programs-and-Feature s- tp7583597.html Sent from the wix-users mailing list archive at Nabble.com. -- Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb
Re: [WiX-users] Install Prerequisites (.NET Framework)
When the bootstrapper are hidden in ARP and the msi is shown, how to uninstall the bootstrapper when the user uninstalls the msi? The bootstrapper needs to be removed upon msi uninstall action... //Sam 13 feb 2013 kl. 17:30 skrev Pally Sandher pally.sand...@iesve.com: You have to write your own Bootstrapper Application to replace the use of WiXBalExtension in that case - http://wix.sourceforge.net/manual-wix3/bootstrapper_application.htm Palbinder Sandher Software Platform Engineer T: +44 (0) 141 945 8500 F: +44 (0) 141 945 8501 http://www.iesve.com **Design, Simulate + Innovate with the Virtual Environment** Integrated Environmental Solutions Limited. Registered in Scotland No. SC151456 Registered Office - Helix Building, West Of Scotland Science Park, Glasgow G20 0SP Email Disclaimer -Original Message- From: Sam Boman [mailto:s...@samb.se] Sent: 13 February 2013 16:16 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Install Prerequisites (.NET Framework) But even though setting: Bundle ... DisableModify=yes DisableRemove=yes MsiPackage ... *DisplayInternalUI=yes Visible=yes*/ I stil get the Bootstrapper UI visible first. Then When I click Install I got the MSI UI visible in front of Bootstrapper UI. And when MSI UI are finnish the Bootstrapper UI are closed. My intention are just not see anything of the Bootstrapper UI if the .NET Framework are present. Just like the old Visual Studio Setup/Deploy projects... //Sam On Wed, Feb 13, 2013 at 3:49 PM, Sam Boman s...@samb.se wrote: Thanks for this good explanations! Regarding this: You should probably set the Burn bundle as related to the MSI so when a user uninstalls the MSI it also uninstalls the Burn bundle. Otherwise the user's system will have the (invisible) Burn bundle still registered which could cause problems if they attempt to reinstall or install a newer release at a later time etc. How do I specify that? //Sam On Tue, Feb 12, 2013 at 6:04 PM, Pally Sandher pally.sand...@iesve.comwrote: For MSI UI - http://wix.sourceforge.net/manual-wix3/wix_xsd_msipackage.htm see the DisplayInternalUI attribute. To list your MSI in Programs Features and not the Burn bundle - http://wix.sourceforge.net/manual-wix3/wix_xsd_bundle.htm see the DisableModify and DisableRemove attributes. Also you will need to set the Visible attribute to yes on your MsiPackage element . You should probably set the Burn bundle as related to the MSI so when a user uninstalls the MSI it also uninstalls the Burn bundle. Otherwise the user's system will have the (invisible) Burn bundle still registered which could cause problems if they attempt to reinstall or install a newer release at a later time etc. Palbinder Sandher Software Platform Engineer T: +44 (0) 141 945 8500 F: +44 (0) 141 945 8501 http://www.iesve.com **Design, Simulate + Innovate with the Virtual Environment** Integrated Environmental Solutions Limited. Registered in Scotland No. SC151456 Registered Office - Helix Building, West Of Scotland Science Park, Glasgow G20 0SP Email Disclaimer -Original Message- From: Sam Boman [mailto:s...@samb.se] Sent: 12 February 2013 16:52 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Install Prerequisites (.NET Framework) Ok, but I have this issue, or maybe its just the way it works... I have set the Msi project to use: UIRef Id=WixUI_InstallDir/ And then I have added the license agreement rtf-file to it. But when I have added this to the Bootstrapper project: *BootstrapperApplicationRef Id=WixStandardBootstrapperApplication.RtfLicense /* Chain PackageGroupRef Id= Netfx4Full/ ...your msi stuff goes here... /Chain I end up in not getting the Msi UI at all, and in Controlpanel - Programs I just see my bootstrapper projectname... Not the original Msi name and version... I thought that the Bootstrapper just would do its checks, and then handover to the Msi UI, and not display any thing to the user if all is Okay (.NET version are the right.). Thanks! //Sam On Tue, Feb 12, 2013 at 3:37 PM, Pally Sandher pally.sand...@iesve.com wrote: You need 2 projects. You have 2 outputs, an MSI a Burn executable which wraps the MSI and deals with your pre-reqs. You can configure your burn package not to register itself or to not register your MSI. See the Burn documentation - http://wix.sourceforge.net/manual-wix3/authoring_bundle_intro.htm BTW all that extra code Steven posted is completely superfluous. All you literally need in your Burn bundle XML is Chain PackageGroupRef Id= Netfx4Full/ ...your msi stuff goes here... /Chain As WiXNetFxExtension has all the authoring required to do all the checks downloading etc. (and has been checked tested by everyone who uses it on a
Re: [WiX-users] Install Prerequisites (.NET Framework)
I did the reverse, I turned off ARP within the MSI's and I am using the ARP in the bootstrapper. I have my OS pre requisites as permanent and my company MSI's as not permanent, so when I uninstall the bootstrapper it removes the bootstrapper and the company MSI's :) Steve -Original Message- From: Sam [mailto:s...@samb.se] Sent: February-14-13 5:20 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Install Prerequisites (.NET Framework) When the bootstrapper are hidden in ARP and the msi is shown, how to uninstall the bootstrapper when the user uninstalls the msi? The bootstrapper needs to be removed upon msi uninstall action... //Sam 13 feb 2013 kl. 17:30 skrev Pally Sandher pally.sand...@iesve.com: You have to write your own Bootstrapper Application to replace the use of WiXBalExtension in that case - http://wix.sourceforge.net/manual-wix3/bootstrapper_application.htm Palbinder Sandher Software Platform Engineer T: +44 (0) 141 945 8500 F: +44 (0) 141 945 8501 http://www.iesve.com **Design, Simulate + Innovate with the Virtual Environment** Integrated Environmental Solutions Limited. Registered in Scotland No. SC151456 Registered Office - Helix Building, West Of Scotland Science Park, Glasgow G20 0SP Email Disclaimer -Original Message- From: Sam Boman [mailto:s...@samb.se] Sent: 13 February 2013 16:16 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Install Prerequisites (.NET Framework) But even though setting: Bundle ... DisableModify=yes DisableRemove=yes MsiPackage ... *DisplayInternalUI=yes Visible=yes*/ I stil get the Bootstrapper UI visible first. Then When I click Install I got the MSI UI visible in front of Bootstrapper UI. And when MSI UI are finnish the Bootstrapper UI are closed. My intention are just not see anything of the Bootstrapper UI if the .NET Framework are present. Just like the old Visual Studio Setup/Deploy projects... //Sam On Wed, Feb 13, 2013 at 3:49 PM, Sam Boman s...@samb.se wrote: Thanks for this good explanations! Regarding this: You should probably set the Burn bundle as related to the MSI so when a user uninstalls the MSI it also uninstalls the Burn bundle. Otherwise the user's system will have the (invisible) Burn bundle still registered which could cause problems if they attempt to reinstall or install a newer release at a later time etc. How do I specify that? //Sam On Tue, Feb 12, 2013 at 6:04 PM, Pally Sandher pally.sand...@iesve.comwrote: For MSI UI - http://wix.sourceforge.net/manual-wix3/wix_xsd_msipackage.htm see the DisplayInternalUI attribute. To list your MSI in Programs Features and not the Burn bundle - http://wix.sourceforge.net/manual-wix3/wix_xsd_bundle.htm see the DisableModify and DisableRemove attributes. Also you will need to set the Visible attribute to yes on your MsiPackage element . You should probably set the Burn bundle as related to the MSI so when a user uninstalls the MSI it also uninstalls the Burn bundle. Otherwise the user's system will have the (invisible) Burn bundle still registered which could cause problems if they attempt to reinstall or install a newer release at a later time etc. Palbinder Sandher Software Platform Engineer T: +44 (0) 141 945 8500 F: +44 (0) 141 945 8501 http://www.iesve.com **Design, Simulate + Innovate with the Virtual Environment** Integrated Environmental Solutions Limited. Registered in Scotland No. SC151456 Registered Office - Helix Building, West Of Scotland Science Park, Glasgow G20 0SP Email Disclaimer -Original Message- From: Sam Boman [mailto:s...@samb.se] Sent: 12 February 2013 16:52 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Install Prerequisites (.NET Framework) Ok, but I have this issue, or maybe its just the way it works... I have set the Msi project to use: UIRef Id=WixUI_InstallDir/ And then I have added the license agreement rtf-file to it. But when I have added this to the Bootstrapper project: *BootstrapperApplicationRef Id=WixStandardBootstrapperApplication.RtfLicense /* Chain PackageGroupRef Id= Netfx4Full/ ...your msi stuff goes here... /Chain I end up in not getting the Msi UI at all, and in Controlpanel - Programs I just see my bootstrapper projectname... Not the original Msi name and version... I thought that the Bootstrapper just would do its checks, and then handover to the Msi UI, and not display any thing to the user if all is Okay (.NET version are the right.). Thanks! //Sam On Tue, Feb 12, 2013 at 3:37 PM, Pally Sandher pally.sand...@iesve.com wrote: You need 2 projects. You have 2 outputs, an MSI a Burn executable which wraps the MSI and deals with your pre-reqs. You can configure your burn package not to register itself or to
Re: [WiX-users] [SPAM] Re: msi.dll crashes during transaction.Commit()
Thanks for the quick response Rob. I'll report it to the Windows Installer team. Cheers, Anton -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/msi-dll-crashes-during-transaction-Commit-tp7583567p7583611.html Sent from the wix-users mailing list archive at Nabble.com. -- Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Install Prerequisites (.NET Framework)
Steve has it right. On Thu, Feb 14, 2013 at 2:54 PM, Steven Ogilvie steven.ogil...@titus.comwrote: I did the reverse, I turned off ARP within the MSI's and I am using the ARP in the bootstrapper. I have my OS pre requisites as permanent and my company MSI's as not permanent, so when I uninstall the bootstrapper it removes the bootstrapper and the company MSI's :) Steve -Original Message- From: Sam [mailto:s...@samb.se] Sent: February-14-13 5:20 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Install Prerequisites (.NET Framework) When the bootstrapper are hidden in ARP and the msi is shown, how to uninstall the bootstrapper when the user uninstalls the msi? The bootstrapper needs to be removed upon msi uninstall action... //Sam 13 feb 2013 kl. 17:30 skrev Pally Sandher pally.sand...@iesve.com: You have to write your own Bootstrapper Application to replace the use of WiXBalExtension in that case - http://wix.sourceforge.net/manual-wix3/bootstrapper_application.htm Palbinder Sandher Software Platform Engineer T: +44 (0) 141 945 8500 F: +44 (0) 141 945 8501 http://www.iesve.com **Design, Simulate + Innovate with the Virtual Environment** Integrated Environmental Solutions Limited. Registered in Scotland No. SC151456 Registered Office - Helix Building, West Of Scotland Science Park, Glasgow G20 0SP Email Disclaimer -Original Message- From: Sam Boman [mailto:s...@samb.se] Sent: 13 February 2013 16:16 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Install Prerequisites (.NET Framework) But even though setting: Bundle ... DisableModify=yes DisableRemove=yes MsiPackage ... *DisplayInternalUI=yes Visible=yes*/ I stil get the Bootstrapper UI visible first. Then When I click Install I got the MSI UI visible in front of Bootstrapper UI. And when MSI UI are finnish the Bootstrapper UI are closed. My intention are just not see anything of the Bootstrapper UI if the .NET Framework are present. Just like the old Visual Studio Setup/Deploy projects... //Sam On Wed, Feb 13, 2013 at 3:49 PM, Sam Boman s...@samb.se wrote: Thanks for this good explanations! Regarding this: You should probably set the Burn bundle as related to the MSI so when a user uninstalls the MSI it also uninstalls the Burn bundle. Otherwise the user's system will have the (invisible) Burn bundle still registered which could cause problems if they attempt to reinstall or install a newer release at a later time etc. How do I specify that? //Sam On Tue, Feb 12, 2013 at 6:04 PM, Pally Sandher pally.sand...@iesve.com wrote: For MSI UI - http://wix.sourceforge.net/manual-wix3/wix_xsd_msipackage.htm see the DisplayInternalUI attribute. To list your MSI in Programs Features and not the Burn bundle - http://wix.sourceforge.net/manual-wix3/wix_xsd_bundle.htm see the DisableModify and DisableRemove attributes. Also you will need to set the Visible attribute to yes on your MsiPackage element . You should probably set the Burn bundle as related to the MSI so when a user uninstalls the MSI it also uninstalls the Burn bundle. Otherwise the user's system will have the (invisible) Burn bundle still registered which could cause problems if they attempt to reinstall or install a newer release at a later time etc. Palbinder Sandher Software Platform Engineer T: +44 (0) 141 945 8500 F: +44 (0) 141 945 8501 http://www.iesve.com **Design, Simulate + Innovate with the Virtual Environment** Integrated Environmental Solutions Limited. Registered in Scotland No. SC151456 Registered Office - Helix Building, West Of Scotland Science Park, Glasgow G20 0SP Email Disclaimer -Original Message- From: Sam Boman [mailto:s...@samb.se] Sent: 12 February 2013 16:52 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Install Prerequisites (.NET Framework) Ok, but I have this issue, or maybe its just the way it works... I have set the Msi project to use: UIRef Id=WixUI_InstallDir/ And then I have added the license agreement rtf-file to it. But when I have added this to the Bootstrapper project: *BootstrapperApplicationRef Id=WixStandardBootstrapperApplication.RtfLicense /* Chain PackageGroupRef Id= Netfx4Full/ ...your msi stuff goes here... /Chain I end up in not getting the Msi UI at all, and in Controlpanel - Programs I just see my bootstrapper projectname... Not the original Msi name and version... I thought that the Bootstrapper just would do its checks, and then handover to the Msi UI, and not display any thing to the user if all is Okay (.NET version are the right.). Thanks! //Sam On Tue, Feb 12, 2013 at 3:37 PM, Pally Sandher pally.sand...@iesve.com wrote: You need 2 projects.
Re: [WiX-users] Problem installing 3.7 on XP
Anyone got any ideas about this? Neil Have a Windows XP machine that is running 3.6 ok but when I try to upgrade to 3.7 it fails, in the logs I see this repeated a few times: [1028:3280][2013-02-08T08:34:00]e000: Error 0x800b0110: Failed authenticode verification of payload: C:\Documents and Settings\All Users\Application Data\Package Cache\.unverified\Wix [1028:3280][2013-02-08T08:34:00]e000: Error 0x800b0110: Failed to verify signature of payload: Wix [1028:3280][2013-02-08T08:34:00]e310: Failed to verify payload: Wix at path: C:\Documents and Settings\All Users\Application Data\Package Cache\.unverified\Wix, error: 0x800b0110. Deleting file. The error 0x800b0110 means The certificate is not valid for the requested usage. Anyone else see this or know how to fix it? Neil Neil Sleightholm X2 Systems Limited n...@x2systems.com -- Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
