[WiX-users] Custom Action Build Error
When I attempt to build my CustomAction project Visual Studio exits with a code of 3. I have tracked the issue to the way wix.ca.targets references the path to MakeSfxCA.exe. In wix.ca.targets the following is what creates the path: CreateProperty Value=$(WixToolPath)..\sdk\ Condition= '$(WixSdkPath)' == '' Output TaskParameter=Value PropertyName=WixSdkPath / /CreateProperty When VS 2012 uses this path it is interpreted as C:\Program Files (x86)\WiX ToolSet v3.8\bin..\sdk\MakeSfxCA.exe and VS apparently doesn't like the \bin.. (specifically the '..' to move up one directory). I can run the task in a command window after removing \bin.. but I would like to have this work within VS so that I don't have to go to a command window to rebuild my project after a change. Is there something that can be changed so that this executes correctly in VS or am I doing something wrong when building my project? Brian If you can't explain it simply, you don't understand it well enough. - Albert Einstein -- CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Shared component syntax...
Today several of our installers create a logs folder in a unique location. We are planning on moving this folder to a location that is common for all of our applications. How best should I define this component in each of my installers? I assume I should have the same Guid for each, right? ComponentGroup Id=LogsFolderComp Directory=LOGSDIR Component Id=LogsComp Guid=XXX KeyPath=yes CreateFolder/ /Component /ComponentGroup Also, I assume the best way to build this component is to create a tiny wixlib that just contains this component. And, then, reference this component in each of my applications, right? -- Tony -- CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Custom Action Build Error
Try Editing wix.ca.targets to read CreateProperty Value=$(WixToolPath)\..\sdk\ Condition= '$(WixSdkPath)' == '' Output TaskParameter=Value PropertyName=WixSdkPath / /CreateProperty Looks like the Preprocessor Variable for $(WixToolPath) doesn't contain the last trailing slash for the path, then submit a Bug Request to the WiX Bugtracker and reference this Post, if and only if the fix works. If all goes well, the bug fix will reqire editing the preprocer variable to include the trailing slash. Once that's done you can remove the manual edit we created from the targets file. Carter Quoting Brian Enderle bria...@gmail.com: When I attempt to build my CustomAction project Visual Studio exits with a code of 3. I have tracked the issue to the way wix.ca.targets references the path to MakeSfxCA.exe. snip -- CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Custom Action Build Error
Thanks, it is actually the file at C:\Program Files (x86)\MSBuild\Microsoft\WiX\v3.x\wix.ca.targets that needed updated. Brian Brian If you can't explain it simply, you don't understand it well enough. - Albert Einstein On Fri, Jan 10, 2014 at 10:51 AM, Carter Young ecyo...@grandecom.netwrote: Try Editing wix.ca.targets to read CreateProperty Value=$(WixToolPath)\..\sdk\ Condition= '$(WixSdkPath)' == '' Output TaskParameter=Value PropertyName=WixSdkPath / /CreateProperty Looks like the Preprocessor Variable for $(WixToolPath) doesn't contain the last trailing slash for the path, then submit a Bug Request to the WiX Bugtracker and reference this Post, if and only if the fix works. If all goes well, the bug fix will reqire editing the preprocer variable to include the trailing slash. Once that's done you can remove the manual edit we created from the targets file. Carter Quoting Brian Enderle bria...@gmail.com: When I attempt to build my CustomAction project Visual Studio exits with a code of 3. I have tracked the issue to the way wix.ca.targets references the path to MakeSfxCA.exe. snip -- CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Bootstrapper inherited from WixBA
Hi all,
We are trying to generate a Bootstrapper Application
CustomBootstrapperApplication which inheritate from WixBA (which we got
from the sources of Wix 3.8).
***
using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
using System.Threading.Tasks;
using WixToolset.UX;
using System.Windows.Forms;
namespace CustomBA3
{
public class CustomBootstrapperApplication : WixBA
{
protected override void Run()
{
MessageBox.Show(Lets Go);
base.Run();
}
}
}
***
The AssemblyInfo contains
[assembly: BootstrapperApplication(typeof(CustomBootstrapperApplication))]
We have tried different bootstrapperCore.config, as
***
?xml version=1.0 encoding=utf-8 ?
configuration
configSections
sectionGroup name=wix.bootstrapper
type=Microsoft.Tools.WindowsInstallerXml.Bootstrapper.BootstrapperSectionGroup,
BootstrapperCore
section name=host
type=Microsoft.Tools.WindowsInstallerXml.Bootstrapper.HostSection,
BootstrapperCore /
/sectionGroup
/configSections
startup useLegacyV2RuntimeActivationPolicy=true
supportedRuntime version=v4.0 /
/startup
wix.bootstrapper
host assemblyName=CustomBootstrapperApplication
supportedFramework version=v4\Full /
supportedFramework version=v4\Client /
/host
/wix.bootstrapper
/configuration
***
or
using
(...)
sectionGroup name=wix.bootstrapper
type=WixToolset.Bootstrapper.BootstrapperSectionGroup, BootstrapperCore
section name=host type=WixToolset.Bootstrapper.HostSection,
BootstrapperCore /
(...)
Our bootstrapper is defined with
(...)
Bundle Name=Bootstrapper Version=1.0.0.0
Manufacturer=Us UpgradeCode=bccd71e0-acc1-4691-a990-4bc251bdcf3f
BootstrapperApplicationRef Id='ManagedBootstrapperApplicationHost'
Payload SourceFile=..\CustomBA3\Bin\Release\CustomBA3.dll /
Payload Name=BootstrapperCore.config
SourceFile=..\CustomBA3\BootstrapperCore.config/
Payload SourceFile=..\CustomBA3\Bin\Release\BootstrapperCore.dll
/
Payload SourceFile=..\CustomBA3\Bin\Release\WixBA.dll /
Payload
SourceFile=..\CustomBA3\Bin\Release\Microsoft.Deployment.WindowsInstaller.dll/
/BootstrapperApplicationRef
(...)
but unfortunately,
all our tries lead to the following error
[1490:1238][2014-01-09T18:54:13]i001: Burn v3.8.1128.0, Windows v6.2 (Build
9200: Service Pack 0), path:
D:\repository\WebForce\Production\v7.0.0\MI_7.0.0_ServicePacks\InstallerProjects\BootstrapperMI\Bootstrapper\bin\Release\Bootstrapper.exe,
cmdline: ''
[1490:1238][2014-01-09T18:54:13]i000: Setting string variable
'WixBundleLog' to value
'C:\Users\spaes\AppData\Local\Temp\Bootstrapper_20140109185413.log'
[1490:1238][2014-01-09T18:54:13]i000: Setting string variable
'WixBundleOriginalSource' to value
'D:\repository\WebForce\Production\v7.0.0\MI_7.0.0_ServicePacks\InstallerProjects\BootstrapperMI\Bootstrapper\bin\Release\Bootstrapper.exe'
[1490:1238][2014-01-09T18:54:13]i000: Setting string variable
'WixBundleName' to value 'Bootstrapper'
[1490:1238][2014-01-09T18:54:13]i000: Loading managed bootstrapper
application.
[1490:1238][2014-01-09T18:54:13]e000: Error 0x80131040: Failed to create
the managed bootstrapper application.
[1490:1238][2014-01-09T18:54:13]e000: Error 0x80131040: Failed to create UX.
[1490:1238][2014-01-09T18:54:13]e000: Error 0x80131040: Failed to load UX.
[1490:1238][2014-01-09T18:54:13]e000: Error 0x80131040: Failed while
running
[1490:1238][2014-01-09T18:54:13]i410: Variable: WixBundleAction = 4
[1490:1238][2014-01-09T18:54:13]i410: Variable: WixBundleElevated = 0
[1490:1238][2014-01-09T18:54:13]i410: Variable: WixBundleLog =
C:\Users\spaes\AppData\Local\Temp\Bootstrapper_20140109185413.log
[1490:1238][2014-01-09T18:54:13]i410: Variable: WixBundleManufacturer = Us
[1490:1238][2014-01-09T18:54:13]i410: Variable: WixBundleName = Bootstrapper
[1490:1238][2014-01-09T18:54:13]i410: Variable: WixBundleOriginalSource =
D:\repository\WebForce\Production\v7.0.0\MI_7.0.0_ServicePacks\InstallerProjects\BootstrapperMI\Bootstrapper\bin\Release\Bootstrapper.exe
[1490:1238][2014-01-09T18:54:13]i410: Variable: WixBundleProviderKey =
{22fc06d5-55ec-4512-9a67-f12297e8920b}
[1490:1238][2014-01-09T18:54:13]i410: Variable: WixBundleTag =
[1490:1238][2014-01-09T18:54:13]i410: Variable: WixBundleVersion = 1.0.0.0
[1490:1238][2014-01-09T18:54:13]e000: Error 0x80131040: Failed to run
per-user mode.
[1490:1238][2014-01-09T18:54:13]i007: Exit code: 0x80131040, restarting: No
--
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink
Re: [WiX-users] Custom Action Issue during MSI installation rollback
Looking at a complete verbose log may help. Otherwise there's not enough info here to say what's wrong. It doesn't help much to say that the CA is something like this. For example, what type is it? We could assume it's deferred, but it's better to know for a fact. 1. I assume the V1 install has an uninstall CA to remove the driver. If so, at the end of REP of V1 there will be no driver on the system. Does it uninstall the driver? 2. When V2 fails, has it installed the V2 version of the kernel driver? If so, does it have a rollback custom action to remove it? At the point where V2 fails we don't know whether there is a V2 kernel driver on the system or not, and if there is a rollback CA in V2 to uninstall it. Anyway the log will show the sequence of events and conditions that resulted in this situation so you should be able to why V1's re-install of the driver didn't happen. If it says the condition evaluated to false, it occurs to me that the re-install of V1 may actually be part of the rollback transaction, in which case you need a rollback CA to re-install the driver, not an install CA. However I'm not sure of that - I forget the details of how that all hangs together. Phil Wilson On Thu, Jan 9, 2014 at 3:43 PM, Suryadeep Biswal surya6...@hotmail.comwrote: We ship a MSI which supports upgrades. We schedule the RemoveExistingProducts custom action after InstallInitialize using MajorUpgrade element – MajorUpgrade Schedule=afterInstallInitialize AllowDowngrades=yes / The MSI performs a variety of things including GACing, writing to registry and also includes a custom action which is used to install a kernel mode driver. We have been running into an issue in the following scenario - 1. V1 MSI is installed first. 2. V2 MSI is installed at a later point. a. For cases, there is a bug in v2 MSI, we expect the MSI installation to roll back and finally leave the system with v1 installed. b. We see everything rolling back to v1 (including the registry keys, file versions etc.) except for the kernel driver. After the previous rollback, we no longer see the kernel mode driver. In the log file, I did not see the custom action being run when v1 is reinstalled. InstallExecuteSequence for the custom action that installs the kernel driver looks something like this – Custom Action=InstallDrivers Before=WriteRegistryValues (NOT REMOVE) AND Privileged /Custom I am wondering if the conditions have something to do with this? I would appreciate any help in figuring out the root cause for this issue. Regards, Surya -- CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Chaining MSPs
I asked this question previously in an older, slightly unrelated thread but I'm thinking it might be more appropriate as its own thread. I have a bundle (lets call it Bundle 1.0) with 3 MSIs (lets say A, B, and C; also all version 1.0). Some of the content in B and C has changed, so I produced an updated 1.0.1 MSI for B and C, and also a MSP for each. I then create Bundle 1.0.1 (a major update to Bundle 1.0 with all three updated MSIs) and BundlePatch 1.0.1 with just the patches for B and C. The behavior I would like to see would be for it not to matter if the user installs Bundle 1.0 followed by BundlePatch 1.0.1, or just Bundle 1.0.1 (i.e., new users can download and install the latest full version while current users only need the much smaller patch version). The closest I've been able to come to this is to give BundlePatch 1.0.1 a different UpgradeCode, and add in a RelatedBundle tag with Bundle's upgrade code and Patch as the action. This installs the two patches and leaves everything else the same, however, it doesn't update the version number in the Programs and Features control panel (we still see Bundle 1.0). In the Installed Updates control panel we do see BundlePatch 1.0.1 listed as an update. Most other things I have tried result in the patches getting installed, and then MSI A being uninstalled. Does anyone know if what I'm trying to do is even possible? -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Chaining-MSPs-tp7591695.html Sent from the wix-users mailing list archive at Nabble.com. -- CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Chaining .NET 3.5 in Burn
Niel provides the infor in his blog. http://neilsleightholm.blogspot.com/2012/05/wix-burn-tipstricks.html -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Chaining-NET-3-5-in-Burn-tp7591622p7591696.html Sent from the wix-users mailing list archive at Nabble.com. -- CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Chaining MSPs
There are a couple options. 1. One include the original B and C MSIs *plus* the new B and C MSPs in the updated Burn. Burn will only download the B and C MSIs if they are missing and Burn will slipstream the MSPs when possible. 2. Make the new Bundle a patch bundle. -Original Message- From: KG [mailto:kelly.gr...@toltech.net] Sent: Friday, January 10, 2014 11:46 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Chaining MSPs I asked this question previously in an older, slightly unrelated thread but I'm thinking it might be more appropriate as its own thread. I have a bundle (lets call it Bundle 1.0) with 3 MSIs (lets say A, B, and C; also all version 1.0). Some of the content in B and C has changed, so I produced an updated 1.0.1 MSI for B and C, and also a MSP for each. I then create Bundle 1.0.1 (a major update to Bundle 1.0 with all three updated MSIs) and BundlePatch 1.0.1 with just the patches for B and C. The behavior I would like to see would be for it not to matter if the user installs Bundle 1.0 followed by BundlePatch 1.0.1, or just Bundle 1.0.1 (i.e., new users can download and install the latest full version while current users only need the much smaller patch version). The closest I've been able to come to this is to give BundlePatch 1.0.1 a different UpgradeCode, and add in a RelatedBundle tag with Bundle's upgrade code and Patch as the action. This installs the two patches and leaves everything else the same, however, it doesn't update the version number in the Programs and Features control panel (we still see Bundle 1.0). In the Installed Updates control panel we do see BundlePatch 1.0.1 listed as an update. Most other things I have tried result in the patches getting installed, and then MSI A being uninstalled. Does anyone know if what I'm trying to do is even possible? -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Chaining-MSPs-tp7591695.html Sent from the wix-users mailing list archive at Nabble.com. -- CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Setup does not work on non-en OS
Thanks. AuthenticatedUser worked! On Monday, January 6, 2014 6:14 PM, Hoover, Jacob jacob.hoo...@greenheck.com wrote: Have you tried User=AuthenticatedUser ? -Original Message- From: Goran Malovic [mailto:malov...@yahoo.com] Sent: Monday, January 06, 2014 10:56 AM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Setup does not work on non-en OS Hi, I just realized that there is a detailed log file for the msi, and I by looking at it I found that that the problem was in resolving sid for authenticated users. How can I set the permiossion for a file in CommonAppData\Application\ to Authenticated users? Component Id=dutch.xml Guid=* File Id=dutch.xml Source=Resources\Localization\Languages\dutch.xml KeyPath=yes util:PermissionEx Append=yes GenericAll=yes User=S-1-5-11 / /File /Component MSI (s) (04:B0) [03:41:27:307]: Hello, I'm your 32bit Elevated custom action server. ExecSecureObjects: Error 0x80070534: failed to get sid for account: Authenticated Users CustomAction ExecSecureObjects returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox) MSI (s) (04:CC) [03:41:27:437]: User policy value 'DisableRollback' is 0 MSI (s) (04:CC) [03:41:27:437]: Machine policy value 'DisableRollback' is 0 Action ended 3:41:27: InstallFinalize. Return value 3. -- Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Chaining MSPs
robmen wrote 1. One include the original B and C MSIs *plus* the new B and C MSPs in the updated Burn. Burn will only download the B and C MSIs if they are missing and Burn will slipstream the MSPs when possible. This seems to work and give me the desired behavior. Thanks! I also just found this: Bundle Version and patching http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Bundle-Version-and-patching-td7579655.html#a7584962 which references Feature Request 725 http://sourceforge.net/p/wix/feature-requests/725/ . That is pretty much the problem I was having. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Chaining-MSPs-tp7591695p7591702.html Sent from the wix-users mailing list archive at Nabble.com. -- CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Custom Action Build Error
In both Windows Installer and in MSBuild all directory paths are always expected to end with the trailing backslash. In fact, if you look at all of the built-in properties for MSBuild all of the directory paths always end with the backslash. The fact that your WixToolPath ends in a letter instead of the backslash caused your build error. -Blair From: bria...@gmail.com Date: Fri, 10 Jan 2014 11:23:26 -0500 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Custom Action Build Error Thanks, it is actually the file at C:\Program Files (x86)\MSBuild\Microsoft\WiX\v3.x\wix.ca.targets that needed updated. Brian Brian If you can't explain it simply, you don't understand it well enough. - Albert Einstein On Fri, Jan 10, 2014 at 10:51 AM, Carter Young ecyo...@grandecom.netwrote: Try Editing wix.ca.targets to read CreateProperty Value=$(WixToolPath)\..\sdk\ Condition= '$(WixSdkPath)' == '' Output TaskParameter=Value PropertyName=WixSdkPath / /CreateProperty Looks like the Preprocessor Variable for $(WixToolPath) doesn't contain the last trailing slash for the path, then submit a Bug Request to the WiX Bugtracker and reference this Post, if and only if the fix works. If all goes well, the bug fix will reqire editing the preprocer variable to include the trailing slash. Once that's done you can remove the manual edit we created from the targets file. Carter Quoting Brian Enderle bria...@gmail.com: When I attempt to build my CustomAction project Visual Studio exits with a code of 3. I have tracked the issue to the way wix.ca.targets references the path to MakeSfxCA.exe. snip -- CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Custom Action Issue during MSI installation rollback
Most of the time if you can condition your custom actions on the action states of some related component you will have more reliability in all use cases. Date: Fri, 10 Jan 2014 11:22:29 -0800 From: phildgwil...@gmail.com To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Custom Action Issue during MSI installation rollback Looking at a complete verbose log may help. Otherwise there's not enough info here to say what's wrong. It doesn't help much to say that the CA is something like this. For example, what type is it? We could assume it's deferred, but it's better to know for a fact. 1. I assume the V1 install has an uninstall CA to remove the driver. If so, at the end of REP of V1 there will be no driver on the system. Does it uninstall the driver? 2. When V2 fails, has it installed the V2 version of the kernel driver? If so, does it have a rollback custom action to remove it? At the point where V2 fails we don't know whether there is a V2 kernel driver on the system or not, and if there is a rollback CA in V2 to uninstall it. Anyway the log will show the sequence of events and conditions that resulted in this situation so you should be able to why V1's re-install of the driver didn't happen. If it says the condition evaluated to false, it occurs to me that the re-install of V1 may actually be part of the rollback transaction, in which case you need a rollback CA to re-install the driver, not an install CA. However I'm not sure of that - I forget the details of how that all hangs together. Phil Wilson On Thu, Jan 9, 2014 at 3:43 PM, Suryadeep Biswal surya6...@hotmail.comwrote: We ship a MSI which supports upgrades. We schedule the RemoveExistingProducts custom action after InstallInitialize using MajorUpgrade element – MajorUpgrade Schedule=afterInstallInitialize AllowDowngrades=yes / The MSI performs a variety of things including GACing, writing to registry and also includes a custom action which is used to install a kernel mode driver. We have been running into an issue in the following scenario - 1. V1 MSI is installed first. 2. V2 MSI is installed at a later point. a. For cases, there is a bug in v2 MSI, we expect the MSI installation to roll back and finally leave the system with v1 installed. b. We see everything rolling back to v1 (including the registry keys, file versions etc.) except for the kernel driver. After the previous rollback, we no longer see the kernel mode driver. In the log file, I did not see the custom action being run when v1 is reinstalled. InstallExecuteSequence for the custom action that installs the kernel driver looks something like this – Custom Action=InstallDrivers Before=WriteRegistryValues (NOT REMOVE) AND Privileged /Custom I am wondering if the conditions have something to do with this? I would appreciate any help in figuring out the root cause for this issue. Regards, Surya -- CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Chaining MSPs
FYI: That feature request on SF now lives at http://wixtoolset.org/issues/3962/. Date: Fri, 10 Jan 2014 13:35:30 -0800 From: kelly.gr...@toltech.net To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Chaining MSPs robmen wrote 1. One include the original B and C MSIs *plus* the new B and C MSPs in the updated Burn. Burn will only download the B and C MSIs if they are missing and Burn will slipstream the MSPs when possible. This seems to work and give me the desired behavior. Thanks! I also just found this: Bundle Version and patching http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Bundle-Version-and-patching-td7579655.html#a7584962 which references Feature Request 725 http://sourceforge.net/p/wix/feature-requests/725/ . That is pretty much the problem I was having. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Chaining-MSPs-tp7591695p7591702.html Sent from the wix-users mailing list archive at Nabble.com. -- CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
