[WiX-users] WixUtilExtension XmlFile uninstall behavior
Hey. I have a question regarding the XmlFile element. In my installer, I'm using it to modify a Unity configuration in an existing installation of another program (I'm replacing one plug-in with another). The way I'm doing it looks like so: However, on uninstall, the value is not returned to its original state, as one would expect from setting Permanent="no" on the element. The documentation claims "Specifies whether or not the modification should be removed on uninstall." Yet, after uninstallation, the value of that field is still "MyProg.MyPlugin, MyProg, Version=1.0.0.0, Culture=neutral, PublicKeyToken=abcdef12345678900", not whatever it was before the installation took place. Is this expected behavior? Am I missing a setting somewhere; is setting Permanent="no" not enough? Help would be appreciated. Best regards ALEXANDER K. SCHRØDER -- BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA The must-attend event for mobile developers. Connect with experts. Get tools for creating Super Apps. See the latest technologies. Sessions, hands-on labs, demos & much more. Register early & save! http://p.sf.net/sfu/rim-blackberry-1 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Question about Patching And Installs
I have a setup that installs as v1.0.0. Then I have a created a patch that updates to v1.0.1 and second patch that will update either a v1.0.0 or v1.0.1 to v1.0.2. This works as expected. These are all minor upgrades (Product and Upgrade Code stay the same with only changes to the product version). In the creation of these patches I used the style defined in the WiX documentation as "Using Purely WiX". So in this process I have a MSI for v1.0.0, v1.0.1 and v1.0.2. When I use the v1.0.1 MSI to do my initial install, I can no longer use the v1.0.2 patch. When I attempt to install I get "Installation success or error status: 1642." error. I presume this is expected behavior? Or should I be setting something else with my Patch file? Here is my Patch and PatchFamily elements. --Brian -- BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA The must-attend event for mobile developers. Connect with experts. Get tools for creating Super Apps. See the latest technologies. Sessions, hands-on labs, demos & much more. Register early & save! http://p.sf.net/sfu/rim-blackberry-1 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Trouble with ManagedBootStrapperApplication
Looking forward to getting feedback about what doesn't work in Burn, yet.
On Tue, Aug 2, 2011 at 5:33 PM, wrote:
> Hi Rob,
>
> Thank you so much for your very prompt reply! I knew it had to be something
> trivial.
>
> Renaming test.config to Test.BootstrapperCore.config and changing the line:
>
>
>
> to
>
> SourceFile='Test.BootstrapperCore.config' />
>
> Fixed the problem. I greatly look forward to using burn on my project!
>
> Best Regards,
>
> Phil Podlevsky
>
> -Original Message-
> From: Rob Mensching [mailto:r...@robmensching.com]
> Sent: Tuesday, August 02, 2011 5:10 PM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Trouble with ManagedBootStrapperApplication
>
> IIRC, "test.config" must be called "BootrapperCore.config". It's the config
> for the BootstrapperCore.dll not for your .dll
>
> On Tue, Aug 2, 2011 at 4:17 PM, Phil Podlevsky
> wrote:
>
> > Hi Everyone,
> >
> > I am trying to build a very simple ManagedBootstrapperApplication and
> > for some reason I am getting the following error every time I run my
> > executable.
> >
> > [0558:0EAC][2011-08-02T15:34:29]: Burn v3.6.1929.0, path:
> > C:\Users\ppodlevsky\Desktop\Bootstrapper1\bin\Debug\Bootstrapper1.exe,
> > cmdline: '-burn.unelevated
> > BurnPipe.{CB4F9B8D-2328-4C37-83C6-51AA3D161E23}
> > {8025EB40-A355-448A-A877-7555CBFB28EE} 6980'
> > [0558:0EAC][2011-08-02T15:34:29]: Setting string variable 'WixBundleName'
> > to
> > value 'Bootstrapper1'
> > [0558:0EAC][2011-08-02T15:34:29]: Setting string variable
> > 'WixBundleLog' to value
> > 'C:\Users\PPODLE~1\AppData\Local\Temp\Bootstrapper1_20110802153429.log'
> > [0558:0EAC][2011-08-02T15:34:29]: Setting string variable
> > 'WixBundleOriginalSource' to value
> > 'C:\Users\ppodlevsky\Desktop\Bootstrapper1\bin\Debug\Bootstrapper1.exe'
> > [0558:0EAC][2011-08-02T15:34:31]: Loading prerequisite bootstrapper
> > application because managed host could not be loaded, error: 0x8007006e.
> > [0558:0EAC][2011-08-02T15:34:31]: Detect 1 packages
> > [0558:0EAC][2011-08-02T15:34:31]: Detected related bundle:
> > {0e8da8e7-83d8-4590-81e9-ab6344096478}, scope: PerMachine, version:
> > 1.0.0.0,
> > operation: None
> > [0558:0EAC][2011-08-02T15:34:31]: Detected related bundle:
> > {404fda75-53c4-41f2-92ff-53e7f2448d8f}, scope: PerMachine, version:
> > 1.0.0.0,
> > operation: None
> > [0558:0EAC][2011-08-02T15:34:31]: Detected related bundle:
> > {54b3aedd-aec9-40bc-b4cf-d511d55f35e3}, scope: PerMachine, version:
> > 1.0.0.0,
> > operation: None
> > [0558:0EAC][2011-08-02T15:34:31]: Detected related bundle:
> > {5c4b1a4e-c47f-4962-8643-61d6fed0d5f0}, scope: PerMachine, version:
> > 1.0.0.0,
> > operation: None
> > [0558:0EAC][2011-08-02T15:34:31]: Detected related bundle:
> > {5ea6379f-2aa4-46fe-9d51-883c8f46c55b}, scope: PerMachine, version:
> > 1.0.0.0,
> > operation: None
> > [0558:0EAC][2011-08-02T15:34:31]: Detected related bundle:
> > {89495e12-6f5f-493b-9bab-32d806c5b0f8}, scope: PerMachine, version:
> > 1.0.0.0,
> > operation: None
> > [0558:0EAC][2011-08-02T15:34:31]: Detected related bundle:
> > {a9117d7c-8964-4cb0-b831-373a8d01391c}, scope: PerMachine, version:
> > 1.0.0.0,
> > operation: None
> > [0558:0EAC][2011-08-02T15:34:31]: Detected related bundle:
> > {bf69ddd6-52fa-4ba2-af75-7931896c4853}, scope: PerMachine, version:
> > 1.0.0.0,
> > operation: None
> > [0558:0EAC][2011-08-02T15:34:31]: Detected related bundle:
> > {c0434e35-f8fb-488d-acc7-2ff2c73374a3}, scope: PerMachine, version:
> > 1.0.0.0,
> > operation: None
> > [0558:0EAC][2011-08-02T15:34:31]: Detected related bundle:
> > {f4451ce5-84cd-462f-a38d-57331103ca7b}, scope: PerMachine, version:
> > 1.0.0.0,
> > operation: None
> > [0558:0EAC][2011-08-02T15:34:31]: Detect 1 msi features for package:
> > Installer
> > [0558:0EAC][2011-08-02T15:34:31]: Detected feature: ProductFeature,
> state:
> > Absent
> > [0558:0EAC][2011-08-02T15:34:31]: Detected package: MCSInstaller, state:
> > Absent, cached: No
> > [0558:0EAC][2011-08-02T15:34:31]: Detect complete, result: 0x0
> > [0558:0EAC][2011-08-02T15:34:36]: Shutting down, exit code: 0x80070642
> > [0558:0EAC][2011-08-02T15:34:36]: The prerequisites were not
> > successfully installed, error: 0x0. The bootstrapper application will be
> not reloaded.
> >
> > To give a bit of background:
> >
> > - I read all the posts I could find on the wix-users email list in
> > regards to ManagedBootstrapperApplication. From what I can tell I am
> > doing
> > everything right.
> > - I am running .NET Framework 4.0 SP1, Visual Studio 2010, and WiX
> > Toolset v.3.6.1929.0.
> >
> > I am running BootStrapper1.exe on the same machine I compiled it on so
> > I know .NET Framework 4.0 SP1 is installed. It looks like WiX is
> > falling back to running the pre-requisites because it can't find
> > test.dll but I have it and test.config in the same directory as
> > Bundle.wxs. I have tried absolute paths to the .DLL and config and it
> > still doesn't wor
Re: [WiX-users] Installing https WCF Webservices
Ug, batch files? It doesn't look like this supports repair and thus won't
work for patching or minor upgrades (probably all scenarios you cut). Of
course, no error reporting either.
A better way is to build a declarative custom action that is reusable. There
is already one in WiX-contrib (http://wixcontrib.codeplex.com/) that does
most of the work. Why not finish it rather than writing batch files that
don't support the full range of scenarios...?
On Tue, Aug 2, 2011 at 9:10 AM, Nick Ramirez wrote:
> We've had quite a bit of hands on experience with this sort of thing
> lately.
> In one project, we bound a certificate to a port during the install so that
> we could use SSL (the same as if you were to go into IIS and set the
> binding
> and choose a certificate). In another case, we used ws-security in the
> web.config by altering the XML at install time. Here I'll just talk about
> the former -- simply binding a certificate to a port.
>
> To get a port to communicate over SSL, you have to bind a certificate to
> that port. The *netsh* command-line utility works nicely for this. Given an
> IP, port and thumbprint of the certificate you want to use, it can bind
> that
> certificate to the port.
>
> I use the following .cmd script, passing in the necessary thumbprint (which
> I call "CERTHASH"), and IP and port to bind to.
> *
> @ECHO OFF
> REM Sets the certificate for for the port where the WCF runs
> REM Note that we get the appid values from the GUIDs in the AssemblyInfo.cs
> files for the WCF
>
> REM Dev cert hash example: d4675cce6b8e85678826c3d426dd213ce4731e5d
>
> SET CERTHASH=%1
> SET IP=%2
> SET PORT=%3
>
> ECHO Binding certificate to port %port%
>
> REM Bind the certificate to the WCF port
> netsh http add sslcert ipport=%IP%:%PORT% certhash=%CERTHASH%
> appid={01C40DD4-FF57-445F-BEDA-06E473DE8589}
>
> ECHO Done.
>
> @ECHO ON*
>
> The appId comes from the Properties\AssemblyInfo.cs file, where I use the
> [assembly: Guid ...]. The netsh documentation is actually kind of vague
> about this, so I probably could have used any GUID. Oh well.
>
> I've also got a similar "rollback" script:
>
> *@ECHO OFF
>
> SET IP=%1
> SET PORT=%2
>
> ECHO Deleting certificate from port binding for port %PORT%
>
> netsh http delete sslcert ipport=%IP%:%PORT%
>
> ECHO Done.
>
> @ECHO ON*
>
> I install these two shell scripts along with my application. Here are the
> components I use:
>
>
>Guid="30B2D226-03C6-4230-9988-9977889BA8AC">
> Source="$(var.sourceDir)bind_cert_to_port.cmd"
> KeyPath="yes" />
>
>
>Guid="BC5F4999-2B17-420F-84E9-D4768B8A02A0">
> Source="$(var.sourceDir)delete_cert_from_port.cmd"
> KeyPath="yes" />
>
>
> I set up some custom actions:
>
>
> Directory="SystemFolder"
> Impersonate="yes"
> Execute="deferred"
> ExeCommand="[SystemFolder]cmd.exe /C
> "[meCCServiceDir]bind_cert_to_port.cmd [WCF_PORT_CERT_THUMBPRINT]
> [ASMX_WEBSITE_IP] [WCF_PORT]""
> Return="check" />
>
>
> Directory="SystemFolder"
> Impersonate="yes"
> Execute="rollback"
> ExeCommand="[SystemFolder]cmd.exe /C
> "[meCCServiceDir]delete_cert_from_port.cmd [ASMX_WEBSITE_IP]
> [WCF_PORT]""
> Return="ignore" />
>
> Directory="SystemFolder"
> Impersonate="yes"
> Execute="deferred"
> ExeCommand="[SystemFolder]cmd.exe /C
> "[meCCServiceDir]delete_cert_from_port.cmd [ASMX_WEBSITE_IP]
> [WCF_PORT]""
> Return="ignore" />
>
> And then I schedule them:
>
>
>
>After="InstallInitialize">1
>After="CA_SetAsmxDnsFromRegistry">REMOVE="ALL"
>
>
> *Before="CA_BindCertToPort">NOT Installed
> NOT
> Installed
>Before="RemoveFiles">REMOVE="ALL"*
>
>
>
> Notice that I also used another custom action to get the IP address based
> on
> the DNS of the website (I used C# for that) and one to get the port I'd
> bound to, if this is happening during an uninstall, from the registry. That
> way, I would have the port again, even though the user didn't enter them
> into a UI.
>
> If you're going the ws-security route, that's another thing. I'm saying a
> lot of stuff here. The main thing is just to use netsh to bind the
> certificate to the port and presto you're ready for HTTPS. We even use this
> to have SSL over a port other than 443.
>
> --
> View this message in context:
> http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Installing-https-WCF-Webservices-tp6641855p6645377.html
> Sent from the wix-users mailing list archive at Nabble.com.
>
>
> -
Re: [WiX-users] Selectively uninstall features when using Burn
If you schedule the MSI for removal (aka: plan = absent) then your request states for Features will be trumped by the MSI removal. To remove features, you need to ensure the MSI is at least present, then modify the Feature states to remove them. On Tue, Aug 2, 2011 at 1:02 PM, Shruthi Achutha wrote: > > > > > Hi, I have a managed custom bootstrapper application used in a bundle with > mulitple MSIs. I am able to select features in the MSIs for install by > setting feature state in the bootstrapper's PlanMsiFeature callback. The > same method however doesn't work for the uninstall case. Does Burn support > selective feature uninstallation? Thanks,Shruthi > > -- > BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA > The must-attend event for mobile developers. Connect with experts. > Get tools for creating Super Apps. See the latest technologies. > Sessions, hands-on labs, demos & much more. Register early & save! > http://p.sf.net/sfu/rim-blackberry-1 > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > -- virtually, Rob Mensching - http://RobMensching.com LLC -- BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA The must-attend event for mobile developers. Connect with experts. Get tools for creating Super Apps. See the latest technologies. Sessions, hands-on labs, demos & much more. Register early & save! http://p.sf.net/sfu/rim-blackberry-1 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Burn - Determine if bundle is already installed
You know if you were installed *much* earlier than detection. The Application.Command struct has a ResumeType in it that tells you whether your bundle is registered or not. The ResumeType.Arp is a little misleading and could probably better be named "Registered". On Tue, Aug 2, 2011 at 10:40 AM, jhennessey wrote: > I am using a managed bootstrapper application and I am trying to figure out > how to detect if the bundle is already installed. > > I am able to detect the packages by handling the *DetectPackageComplete* > event but I can't just assume that the bundle is installed by detecting one > of the packages in it (it might have been installed outside of the bundle). > > I also tried handling the *DetectRelatedBundle* event but it never fires > (and judging by the name I wouldn't expect it to in this case). > > To be honest I was expecting there to be something like a DetectBundle > event > but I don't see one. > > *All that being said, anybody have any clue on how to detect if the current > bundle is already installed?* > > -- > View this message in context: > http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-Determine-if-bundle-is-already-installed-tp6645777p6645777.html > Sent from the wix-users mailing list archive at Nabble.com. > > > -- > BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA > The must-attend event for mobile developers. Connect with experts. > Get tools for creating Super Apps. See the latest technologies. > Sessions, hands-on labs, demos & much more. Register early & save! > http://p.sf.net/sfu/rim-blackberry-1 > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > -- virtually, Rob Mensching - http://RobMensching.com LLC -- BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA The must-attend event for mobile developers. Connect with experts. Get tools for creating Super Apps. See the latest technologies. Sessions, hands-on labs, demos & much more. Register early & save! http://p.sf.net/sfu/rim-blackberry-1 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Trouble with ManagedBootStrapperApplication
Hi Rob,
Thank you so much for your very prompt reply! I knew it had to be something
trivial.
Renaming test.config to Test.BootstrapperCore.config and changing the line:
to
Fixed the problem. I greatly look forward to using burn on my project!
Best Regards,
Phil Podlevsky
-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: Tuesday, August 02, 2011 5:10 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Trouble with ManagedBootStrapperApplication
IIRC, "test.config" must be called "BootrapperCore.config". It's the config
for the BootstrapperCore.dll not for your .dll
On Tue, Aug 2, 2011 at 4:17 PM, Phil Podlevsky
wrote:
> Hi Everyone,
>
> I am trying to build a very simple ManagedBootstrapperApplication and
> for some reason I am getting the following error every time I run my
> executable.
>
> [0558:0EAC][2011-08-02T15:34:29]: Burn v3.6.1929.0, path:
> C:\Users\ppodlevsky\Desktop\Bootstrapper1\bin\Debug\Bootstrapper1.exe,
> cmdline: '-burn.unelevated
> BurnPipe.{CB4F9B8D-2328-4C37-83C6-51AA3D161E23}
> {8025EB40-A355-448A-A877-7555CBFB28EE} 6980'
> [0558:0EAC][2011-08-02T15:34:29]: Setting string variable 'WixBundleName'
> to
> value 'Bootstrapper1'
> [0558:0EAC][2011-08-02T15:34:29]: Setting string variable
> 'WixBundleLog' to value
> 'C:\Users\PPODLE~1\AppData\Local\Temp\Bootstrapper1_20110802153429.log'
> [0558:0EAC][2011-08-02T15:34:29]: Setting string variable
> 'WixBundleOriginalSource' to value
> 'C:\Users\ppodlevsky\Desktop\Bootstrapper1\bin\Debug\Bootstrapper1.exe'
> [0558:0EAC][2011-08-02T15:34:31]: Loading prerequisite bootstrapper
> application because managed host could not be loaded, error: 0x8007006e.
> [0558:0EAC][2011-08-02T15:34:31]: Detect 1 packages
> [0558:0EAC][2011-08-02T15:34:31]: Detected related bundle:
> {0e8da8e7-83d8-4590-81e9-ab6344096478}, scope: PerMachine, version:
> 1.0.0.0,
> operation: None
> [0558:0EAC][2011-08-02T15:34:31]: Detected related bundle:
> {404fda75-53c4-41f2-92ff-53e7f2448d8f}, scope: PerMachine, version:
> 1.0.0.0,
> operation: None
> [0558:0EAC][2011-08-02T15:34:31]: Detected related bundle:
> {54b3aedd-aec9-40bc-b4cf-d511d55f35e3}, scope: PerMachine, version:
> 1.0.0.0,
> operation: None
> [0558:0EAC][2011-08-02T15:34:31]: Detected related bundle:
> {5c4b1a4e-c47f-4962-8643-61d6fed0d5f0}, scope: PerMachine, version:
> 1.0.0.0,
> operation: None
> [0558:0EAC][2011-08-02T15:34:31]: Detected related bundle:
> {5ea6379f-2aa4-46fe-9d51-883c8f46c55b}, scope: PerMachine, version:
> 1.0.0.0,
> operation: None
> [0558:0EAC][2011-08-02T15:34:31]: Detected related bundle:
> {89495e12-6f5f-493b-9bab-32d806c5b0f8}, scope: PerMachine, version:
> 1.0.0.0,
> operation: None
> [0558:0EAC][2011-08-02T15:34:31]: Detected related bundle:
> {a9117d7c-8964-4cb0-b831-373a8d01391c}, scope: PerMachine, version:
> 1.0.0.0,
> operation: None
> [0558:0EAC][2011-08-02T15:34:31]: Detected related bundle:
> {bf69ddd6-52fa-4ba2-af75-7931896c4853}, scope: PerMachine, version:
> 1.0.0.0,
> operation: None
> [0558:0EAC][2011-08-02T15:34:31]: Detected related bundle:
> {c0434e35-f8fb-488d-acc7-2ff2c73374a3}, scope: PerMachine, version:
> 1.0.0.0,
> operation: None
> [0558:0EAC][2011-08-02T15:34:31]: Detected related bundle:
> {f4451ce5-84cd-462f-a38d-57331103ca7b}, scope: PerMachine, version:
> 1.0.0.0,
> operation: None
> [0558:0EAC][2011-08-02T15:34:31]: Detect 1 msi features for package:
> Installer
> [0558:0EAC][2011-08-02T15:34:31]: Detected feature: ProductFeature, state:
> Absent
> [0558:0EAC][2011-08-02T15:34:31]: Detected package: MCSInstaller, state:
> Absent, cached: No
> [0558:0EAC][2011-08-02T15:34:31]: Detect complete, result: 0x0
> [0558:0EAC][2011-08-02T15:34:36]: Shutting down, exit code: 0x80070642
> [0558:0EAC][2011-08-02T15:34:36]: The prerequisites were not
> successfully installed, error: 0x0. The bootstrapper application will be
not reloaded.
>
> To give a bit of background:
>
> - I read all the posts I could find on the wix-users email list in
> regards to ManagedBootstrapperApplication. From what I can tell I am
> doing
> everything right.
> - I am running .NET Framework 4.0 SP1, Visual Studio 2010, and WiX
> Toolset v.3.6.1929.0.
>
> I am running BootStrapper1.exe on the same machine I compiled it on so
> I know .NET Framework 4.0 SP1 is installed. It looks like WiX is
> falling back to running the pre-requisites because it can't find
> test.dll but I have it and test.config in the same directory as
> Bundle.wxs. I have tried absolute paths to the .DLL and config and it
> still doesn't work. I also tried enabling the fusion log to see if it
> was having trouble loading an assembly via reflection and still no dice.
>
> Here is all the code I am using. Does anyone have any ideas? I love
> the burn concept and want to use it on my project at work but this
> error is making me want to pull my hair out. Is there any way to step
> through what burn is trying to
Re: [WiX-users] Quite Execution Custom action not sync!?
Can you share the exact code causing the problem? I agree that it should work. On Tue, Aug 2, 2011 at 1:14 PM, Marc Bauer wrote: > Hi > > trying to run exe files with the WiX custom actions and it looks like setup > does not wait for the exe to complete. It's configured as "deferred" action > with return=check and impersonate=no. > > I've see the setup is now installing files before the custom action has > been > finished it's execution. This shouldn't be the case. I need to wait until > the EXE has finished. I thought return=check will make setup to wait for > the > exe... > > What I'm doing wrong? > > Regards > Marc > > > > -- > BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA > The must-attend event for mobile developers. Connect with experts. > Get tools for creating Super Apps. See the latest technologies. > Sessions, hands-on labs, demos & much more. Register early & save! > http://p.sf.net/sfu/rim-blackberry-1 > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > -- virtually, Rob Mensching - http://RobMensching.com LLC -- BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA The must-attend event for mobile developers. Connect with experts. Get tools for creating Super Apps. See the latest technologies. Sessions, hands-on labs, demos & much more. Register early & save! http://p.sf.net/sfu/rim-blackberry-1 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Trouble with ManagedBootStrapperApplication
IIRC, "test.config" must be called "BootrapperCore.config". It's the config
for the BootstrapperCore.dll not for your .dll
On Tue, Aug 2, 2011 at 4:17 PM, Phil Podlevsky wrote:
> Hi Everyone,
>
> I am trying to build a very simple ManagedBootstrapperApplication and for
> some reason I am getting the following error every time I run my
> executable.
>
> [0558:0EAC][2011-08-02T15:34:29]: Burn v3.6.1929.0, path:
> C:\Users\ppodlevsky\Desktop\Bootstrapper1\bin\Debug\Bootstrapper1.exe,
> cmdline: '-burn.unelevated BurnPipe.{CB4F9B8D-2328-4C37-83C6-51AA3D161E23}
> {8025EB40-A355-448A-A877-7555CBFB28EE} 6980'
> [0558:0EAC][2011-08-02T15:34:29]: Setting string variable 'WixBundleName'
> to
> value 'Bootstrapper1'
> [0558:0EAC][2011-08-02T15:34:29]: Setting string variable 'WixBundleLog' to
> value
> 'C:\Users\PPODLE~1\AppData\Local\Temp\Bootstrapper1_20110802153429.log'
> [0558:0EAC][2011-08-02T15:34:29]: Setting string variable
> 'WixBundleOriginalSource' to value
> 'C:\Users\ppodlevsky\Desktop\Bootstrapper1\bin\Debug\Bootstrapper1.exe'
> [0558:0EAC][2011-08-02T15:34:31]: Loading prerequisite bootstrapper
> application because managed host could not be loaded, error: 0x8007006e.
> [0558:0EAC][2011-08-02T15:34:31]: Detect 1 packages
> [0558:0EAC][2011-08-02T15:34:31]: Detected related bundle:
> {0e8da8e7-83d8-4590-81e9-ab6344096478}, scope: PerMachine, version:
> 1.0.0.0,
> operation: None
> [0558:0EAC][2011-08-02T15:34:31]: Detected related bundle:
> {404fda75-53c4-41f2-92ff-53e7f2448d8f}, scope: PerMachine, version:
> 1.0.0.0,
> operation: None
> [0558:0EAC][2011-08-02T15:34:31]: Detected related bundle:
> {54b3aedd-aec9-40bc-b4cf-d511d55f35e3}, scope: PerMachine, version:
> 1.0.0.0,
> operation: None
> [0558:0EAC][2011-08-02T15:34:31]: Detected related bundle:
> {5c4b1a4e-c47f-4962-8643-61d6fed0d5f0}, scope: PerMachine, version:
> 1.0.0.0,
> operation: None
> [0558:0EAC][2011-08-02T15:34:31]: Detected related bundle:
> {5ea6379f-2aa4-46fe-9d51-883c8f46c55b}, scope: PerMachine, version:
> 1.0.0.0,
> operation: None
> [0558:0EAC][2011-08-02T15:34:31]: Detected related bundle:
> {89495e12-6f5f-493b-9bab-32d806c5b0f8}, scope: PerMachine, version:
> 1.0.0.0,
> operation: None
> [0558:0EAC][2011-08-02T15:34:31]: Detected related bundle:
> {a9117d7c-8964-4cb0-b831-373a8d01391c}, scope: PerMachine, version:
> 1.0.0.0,
> operation: None
> [0558:0EAC][2011-08-02T15:34:31]: Detected related bundle:
> {bf69ddd6-52fa-4ba2-af75-7931896c4853}, scope: PerMachine, version:
> 1.0.0.0,
> operation: None
> [0558:0EAC][2011-08-02T15:34:31]: Detected related bundle:
> {c0434e35-f8fb-488d-acc7-2ff2c73374a3}, scope: PerMachine, version:
> 1.0.0.0,
> operation: None
> [0558:0EAC][2011-08-02T15:34:31]: Detected related bundle:
> {f4451ce5-84cd-462f-a38d-57331103ca7b}, scope: PerMachine, version:
> 1.0.0.0,
> operation: None
> [0558:0EAC][2011-08-02T15:34:31]: Detect 1 msi features for package:
> Installer
> [0558:0EAC][2011-08-02T15:34:31]: Detected feature: ProductFeature, state:
> Absent
> [0558:0EAC][2011-08-02T15:34:31]: Detected package: MCSInstaller, state:
> Absent, cached: No
> [0558:0EAC][2011-08-02T15:34:31]: Detect complete, result: 0x0
> [0558:0EAC][2011-08-02T15:34:36]: Shutting down, exit code: 0x80070642
> [0558:0EAC][2011-08-02T15:34:36]: The prerequisites were not successfully
> installed, error: 0x0. The bootstrapper application will be not reloaded.
>
> To give a bit of background:
>
> - I read all the posts I could find on the wix-users email list in
> regards to ManagedBootstrapperApplication. From what I can tell I am
> doing
> everything right.
> - I am running .NET Framework 4.0 SP1, Visual Studio 2010, and WiX
> Toolset v.3.6.1929.0.
>
> I am running BootStrapper1.exe on the same machine I compiled it on so I
> know .NET Framework 4.0 SP1 is installed. It looks like WiX is falling back
> to running the pre-requisites because it can't find test.dll but I have it
> and test.config in the same directory as Bundle.wxs. I have tried absolute
> paths to the .DLL and config and it still doesn't work. I also tried
> enabling the fusion log to see if it was having trouble loading an assembly
> via reflection and still no dice.
>
> Here is all the code I am using. Does anyone have any ideas? I love the
> burn
> concept and want to use it on my project at work but this error is making
> me
> want to pull my hair out. Is there any way to step through what burn is
> trying to when running my installer? Knowing my luck this has got to be
> something trivial...
>
> Best Regards,
>
> Phil Podlevsky
>
> BootStrapper1 project, Output type: Executable Package (.exe)
>
> Bundle.wxs:
>
> xmlns="http://schemas.microsoft.com/wix/2006/wi";
> xmlns:util="http://schemas.microsoft.com/wix/UtilExtension";> Name="Bootstrapper1" Version="1.0.0.0" Manufacturer="Bootstrapper1"
> UpgradeCode="5390236b-bb16-4fd5-b662-a1022046f3db"> Id="WixMbaPrereqPackageId" Value="Netfx4Full" /> Id="WixMbaPrereqLicenseUrl" Value="NetfxLi
Re: [WiX-users] Wix36 Installer Hangs
Possibly configuring Visual Studio? Can you go in %TEMP% and look at the WiX log files there... that will help us diagnose futher. On Tue, Aug 2, 2011 at 1:48 PM, wix-user wrote: > I'm interested in Burn so I've uninstalled Wix35 and am now trying to > load Wix36. The installer appears to hang and just shows Installing in > the upper left and "Up to date" in the middle left. What's the deal? > > > > -- > BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA > The must-attend event for mobile developers. Connect with experts. > Get tools for creating Super Apps. See the latest technologies. > Sessions, hands-on labs, demos & much more. Register early & save! > http://p.sf.net/sfu/rim-blackberry-1 > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > -- virtually, Rob Mensching - http://RobMensching.com LLC -- BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA The must-attend event for mobile developers. Connect with experts. Get tools for creating Super Apps. See the latest technologies. Sessions, hands-on labs, demos & much more. Register early & save! http://p.sf.net/sfu/rim-blackberry-1 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Trouble with ManagedBootStrapperApplication
Hi Everyone,
I am trying to build a very simple ManagedBootstrapperApplication and for
some reason I am getting the following error every time I run my executable.
[0558:0EAC][2011-08-02T15:34:29]: Burn v3.6.1929.0, path:
C:\Users\ppodlevsky\Desktop\Bootstrapper1\bin\Debug\Bootstrapper1.exe,
cmdline: '-burn.unelevated BurnPipe.{CB4F9B8D-2328-4C37-83C6-51AA3D161E23}
{8025EB40-A355-448A-A877-7555CBFB28EE} 6980'
[0558:0EAC][2011-08-02T15:34:29]: Setting string variable 'WixBundleName' to
value 'Bootstrapper1'
[0558:0EAC][2011-08-02T15:34:29]: Setting string variable 'WixBundleLog' to
value
'C:\Users\PPODLE~1\AppData\Local\Temp\Bootstrapper1_20110802153429.log'
[0558:0EAC][2011-08-02T15:34:29]: Setting string variable
'WixBundleOriginalSource' to value
'C:\Users\ppodlevsky\Desktop\Bootstrapper1\bin\Debug\Bootstrapper1.exe'
[0558:0EAC][2011-08-02T15:34:31]: Loading prerequisite bootstrapper
application because managed host could not be loaded, error: 0x8007006e.
[0558:0EAC][2011-08-02T15:34:31]: Detect 1 packages
[0558:0EAC][2011-08-02T15:34:31]: Detected related bundle:
{0e8da8e7-83d8-4590-81e9-ab6344096478}, scope: PerMachine, version: 1.0.0.0,
operation: None
[0558:0EAC][2011-08-02T15:34:31]: Detected related bundle:
{404fda75-53c4-41f2-92ff-53e7f2448d8f}, scope: PerMachine, version: 1.0.0.0,
operation: None
[0558:0EAC][2011-08-02T15:34:31]: Detected related bundle:
{54b3aedd-aec9-40bc-b4cf-d511d55f35e3}, scope: PerMachine, version: 1.0.0.0,
operation: None
[0558:0EAC][2011-08-02T15:34:31]: Detected related bundle:
{5c4b1a4e-c47f-4962-8643-61d6fed0d5f0}, scope: PerMachine, version: 1.0.0.0,
operation: None
[0558:0EAC][2011-08-02T15:34:31]: Detected related bundle:
{5ea6379f-2aa4-46fe-9d51-883c8f46c55b}, scope: PerMachine, version: 1.0.0.0,
operation: None
[0558:0EAC][2011-08-02T15:34:31]: Detected related bundle:
{89495e12-6f5f-493b-9bab-32d806c5b0f8}, scope: PerMachine, version: 1.0.0.0,
operation: None
[0558:0EAC][2011-08-02T15:34:31]: Detected related bundle:
{a9117d7c-8964-4cb0-b831-373a8d01391c}, scope: PerMachine, version: 1.0.0.0,
operation: None
[0558:0EAC][2011-08-02T15:34:31]: Detected related bundle:
{bf69ddd6-52fa-4ba2-af75-7931896c4853}, scope: PerMachine, version: 1.0.0.0,
operation: None
[0558:0EAC][2011-08-02T15:34:31]: Detected related bundle:
{c0434e35-f8fb-488d-acc7-2ff2c73374a3}, scope: PerMachine, version: 1.0.0.0,
operation: None
[0558:0EAC][2011-08-02T15:34:31]: Detected related bundle:
{f4451ce5-84cd-462f-a38d-57331103ca7b}, scope: PerMachine, version: 1.0.0.0,
operation: None
[0558:0EAC][2011-08-02T15:34:31]: Detect 1 msi features for package:
Installer
[0558:0EAC][2011-08-02T15:34:31]: Detected feature: ProductFeature, state:
Absent
[0558:0EAC][2011-08-02T15:34:31]: Detected package: MCSInstaller, state:
Absent, cached: No
[0558:0EAC][2011-08-02T15:34:31]: Detect complete, result: 0x0
[0558:0EAC][2011-08-02T15:34:36]: Shutting down, exit code: 0x80070642
[0558:0EAC][2011-08-02T15:34:36]: The prerequisites were not successfully
installed, error: 0x0. The bootstrapper application will be not reloaded.
To give a bit of background:
- I read all the posts I could find on the wix-users email list in
regards to ManagedBootstrapperApplication. From what I can tell I am doing
everything right.
- I am running .NET Framework 4.0 SP1, Visual Studio 2010, and WiX
Toolset v.3.6.1929.0.
I am running BootStrapper1.exe on the same machine I compiled it on so I
know .NET Framework 4.0 SP1 is installed. It looks like WiX is falling back
to running the pre-requisites because it can't find test.dll but I have it
and test.config in the same directory as Bundle.wxs. I have tried absolute
paths to the .DLL and config and it still doesn't work. I also tried
enabling the fusion log to see if it was having trouble loading an assembly
via reflection and still no dice.
Here is all the code I am using. Does anyone have any ideas? I love the burn
concept and want to use it on my project at work but this error is making me
want to pull my hair out. Is there any way to step through what burn is
trying to when running my installer? Knowing my luck this has got to be
something trivial...
Best Regards,
Phil Podlevsky
BootStrapper1 project, Output type: Executable Package (.exe)
Bundle.wxs:
http://schemas.microsoft.com/wix/2006/wi";
xmlns:util="http://schemas.microsoft.com/wix/UtilExtension";>
Test project, Output type: Class library (test.dll)
Test.config:
TestBA.cs:
namespace Test
{
public class TestBA : BootstrapperApplication
{
protected override void Run()
{
MessageBox.Show("My BA is running");
this.Engine.Quit(0);
}
}
}
AssemblyInfo.cs:
[assembly: BootstrapperApplication(typeof(TestBA))]
--
BlackBerry® DevCon Americas, Oct. 18-20, San F
Re: [WiX-users] Major upgrade opt-out ?
That won't be an issue if the dialog is only scheduled in the InstallUISequence as that is skipped on an unattended install. Neil -Original Message- From: John Cooper [mailto:jocoo...@jackhenry.com] Sent: 01 August 2011 18:05 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Major upgrade opt-out ? Condition your dialog on WIX_UPGRADE_DETECTED. However, is unattended upgrade or an install important? If it is, popping a dialog during an upgrade scenario is going to force an attended install. -- -- John Merryweather Cooper Jack Henry & Associates, Inc. (Premier Tech, Inc.) Build & Install Engineer - jXchange Office: 913-341-3434 x791011 jocoo...@jackhenry.com -Original Message- From: robert_y...@non.agilent.com [mailto:robert_y...@non.agilent.com] Sent: Monday, August 01, 2011 11:31 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Major upgrade opt-out ? We would like to be able to uninstall an older product, and install the new version. I tried out the MajorUpgrade element, and it works well. The only problem is that it seems to work silently .. apparently we need to be able to prompt the user and ask them if it's OK to perform the upgrade. Is this possible in Wix 3.5 ? Thanks ! -Rob -- Got Input? Slashdot Needs You. Take our quick survey online. Come on, we don't ask for help often. Plus, you'll get a chance to win $100 to spend on ThinkGeek. http://p.sf.net/sfu/slashdot-survey ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users NOTICE: This electronic mail message and any files transmitted with it are intended exclusively for the individual or entity to which it is addressed. The message, together with any attachment, may contain confidential and/or privileged information. Any unauthorized review, use, printing, saving, copying, disclosure or distribution is strictly prohibited. If you have received this message in error, please immediately advise the sender by reply email and delete all copies. -- Got Input? Slashdot Needs You. Take our quick survey online. Come on, we don't ask for help often. Plus, you'll get a chance to win $100 to spend on ThinkGeek. http://p.sf.net/sfu/slashdot-survey ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA The must-attend event for mobile developers. Connect with experts. Get tools for creating Super Apps. See the latest technologies. Sessions, hands-on labs, demos & much more. Register early & save! http://p.sf.net/sfu/rim-blackberry-1 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Wix36 Installer Hangs
I'm interested in Burn so I've uninstalled Wix35 and am now trying to load Wix36. The installer appears to hang and just shows Installing in the upper left and "Up to date" in the middle left. What's the deal? -- BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA The must-attend event for mobile developers. Connect with experts. Get tools for creating Super Apps. See the latest technologies. Sessions, hands-on labs, demos & much more. Register early & save! http://p.sf.net/sfu/rim-blackberry-1 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Quite Execution Custom action not sync!?
Hi trying to run exe files with the WiX custom actions and it looks like setup does not wait for the exe to complete. It's configured as "deferred" action with return=check and impersonate=no. I've see the setup is now installing files before the custom action has been finished it's execution. This shouldn't be the case. I need to wait until the EXE has finished. I thought return=check will make setup to wait for the exe... What I'm doing wrong? Regards Marc -- BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA The must-attend event for mobile developers. Connect with experts. Get tools for creating Super Apps. See the latest technologies. Sessions, hands-on labs, demos & much more. Register early & save! http://p.sf.net/sfu/rim-blackberry-1 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Component is not getting removed at uninstall
It should also be noted that if I run an Administrative console and uninstall the msi from there, the feature gets correctly removed. Even though this msi is installed not as an administrator, though I am logged in as an administrative user. - Original Message - From: The Eligible Bachelors To: General discussion for Windows Installer XML toolset. Cc: Sent: Tuesday, August 2, 2011 3:59 PM Subject: Re: [WiX-users] Component is not getting removed at uninstall I searched the verbose uninstall log for the name of the feature. The only difference is on the XP machine it says Feature: XYZ_feature; Installed: Local; Request: Absent; Action: Absent while on the Windows 7 machine it says Feature: XYZ_feature; Installed: Advertise; Request: Absent; Action: Absent The MSI I am using is the same on both machines. Could it be the problem that the feature is advertised? And if so, why would this be different across operating systems? - Original Message - From: Rob Mensching To: General discussion for Windows Installer XML toolset. Cc: Sent: Saturday, March 19, 2011 2:01 PM Subject: Re: [WiX-users] Component is not getting removed at uninstall Look at a verbose log file. It will show you the action states of the Components. On Wed, Mar 16, 2011 at 6:53 AM, The Eligible Bachelors < theeligiblebachel...@yahoo.com> wrote: > I am having trouble figuring out why a component is not being removed at > uninstall time. This problem happens when the MSI is run in Windows 7. When > run in XP, the component is getting removed as expected. > > The Wix file is somewhat complex and contains a REINSTALLMODE property. > > What I have done is generated a log during uninstall time for both the Win7 > and XP installers. But the diff is a mess. > > Any tips on how to debug this? > > > > > > -- > Colocation vs. Managed Hosting > A question and answer guide to determining the best fit > for your organization - today and in the future. > http://p.sf.net/sfu/internap-sfd2d > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > -- virtually, Rob Mensching - http://RobMensching.com LLC -- Colocation vs. Managed Hosting A question and answer guide to determining the best fit for your organization - today and in the future. http://p.sf.net/sfu/internap-sfd2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA The must-attend event for mobile developers. Connect with experts. Get tools for creating Super Apps. See the latest technologies. Sessions, hands-on labs, demos & much more. Register early & save! http://p.sf.net/sfu/rim-blackberry-1 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA The must-attend event for mobile developers. Connect with experts. Get tools for creating Super Apps. See the latest technologies. Sessions, hands-on labs, demos & much more. Register early & save! http://p.sf.net/sfu/rim-blackberry-1 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Rollback Script being deleted too early
Hi,
I am getting two errors when my installer does a rollback. An 1101 error (A
file stream could not be opened) then a 1712 error (A file needed for system
restore is missing). The rollback appears to have all worked correctly, so
this isn't a huge issue. It is just an annoyance since each one of these
errors pops up a error box with an ugly message that the user has to click
the 'OK' button on.
I ran process monitor to track the file that the msi is looking for. Msiexec
creates, writes to and reads from the file all throughout the
install/rollback process, until the very end. For some reason it closes the
file, deletes it and then tries to reopen it...?
Here is the logfile section:
Property(S): PrimaryVolumeSpaceRequired = 0
Property(S): PrimaryVolumeSpaceRemaining = 0
Property(S): SOURCEDIR = C:\Documents and Settings\walterty\Local
Settings\Temp\
Property(S): SourcedirProduct = {D6FB571C-F644-411A-8357-A51C5FEA6CE6}
Property(S): ProductToBeRegistered = 1
MSI (s) (28:AC) [10:43:17:352]: MainEngineThread is returning 1603
MSI (s) (28:D0) [10:43:17:352]: No System Restore sequence number for this
installation.
MSI (s) (28:D0) [10:43:17:383]: User policy value 'DisableRollback' is 0
MSI (s) (28:D0) [10:43:17:383]: Machine policy value 'DisableRollback' is 0
MSI (s) (28:D0) [10:43:17:399]: Incrementing counter to disable shutdown.
Counter after increment: 0
MSI (s) (28:D0) [10:43:17:414]: Note: 1: 1101 2: C:\Config.Msi\5d5877.rbs 3:
2
1: 1101 2: C:\Config.Msi\5d5877.rbs 3: 2
MSI (s) (28:D0) [10:43:18:993]: Note: 1: 1712
1: 1712
MSI (s) (28:D0) [10:43:20:039]: Decrementing counter to disable shutdown. If
counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (s) (28:D0) [10:43:20:039]: Restoring environment variables
MSI (s) (28:D0) [10:43:20:055]: Destroying RemoteAPI object.
MSI (s) (28:5C) [10:43:20:055]: Custom Action Manager thread ending.
MSI (c) (F4:44) [10:43:20:071]: Back from server. Return value: 1603
MSI (c) (F4:44) [10:43:20:086]: Decrementing counter to disable shutdown. If
counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (F4:44) [10:43:20:086]: PROPERTY CHANGE: Deleting SECONDSEQUENCE
property. Its current value is '1'.
Action ended 10:43:20: ExecuteAction. Return value 3.
MSI (c) (F4:44) [10:43:20:102]: Doing action: FatalError
Action 10:43:20: FatalError.
Action start 10:43:20: FatalError.
Action 10:43:20: FatalError. Dialog created
Action ended 10:43:21: FatalError. Return value 2.
Action ended 10:43:21: INSTALL. Return value 3.
Property(C): UpgradeCode = {58AF670A-1128-441C-AB64-C1CCB8D3C386}
Property(C): ProductCode = {D6FB571C-F644-411A-8357-A51C5FEA6CE6}
Property(C): INSTANCENAME = EXAMPLE Author 0
Property(C): INSTALLLOCATION = C:\Program Files\Duck Creek Technologies\
.
Custom Action Setup:
NOT Installed AND
REMOVEINSTALLSHIELD
NOT Installed AND
REMOVEINSTALLSHIELD
Thanks for any input.
--
Tyler Walters
--
BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA
The must-attend event for mobile developers. Connect with experts.
Get tools for creating Super Apps. See the latest technologies.
Sessions, hands-on labs, demos & much more. Register early & save!
http://p.sf.net/sfu/rim-blackberry-1
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Selectively uninstall features when using Burn
Hi, I have a managed custom bootstrapper application used in a bundle with mulitple MSIs. I am able to select features in the MSIs for install by setting feature state in the bootstrapper's PlanMsiFeature callback. The same method however doesn't work for the uninstall case. Does Burn support selective feature uninstallation? Thanks,Shruthi -- BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA The must-attend event for mobile developers. Connect with experts. Get tools for creating Super Apps. See the latest technologies. Sessions, hands-on labs, demos & much more. Register early & save! http://p.sf.net/sfu/rim-blackberry-1 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Component is not getting removed at uninstall
I searched the verbose uninstall log for the name of the feature. The only difference is on the XP machine it says Feature: XYZ_feature; Installed: Local; Request: Absent; Action: Absent while on the Windows 7 machine it says Feature: XYZ_feature; Installed: Advertise; Request: Absent; Action: Absent The MSI I am using is the same on both machines. Could it be the problem that the feature is advertised? And if so, why would this be different across operating systems? - Original Message - From: Rob Mensching To: General discussion for Windows Installer XML toolset. Cc: Sent: Saturday, March 19, 2011 2:01 PM Subject: Re: [WiX-users] Component is not getting removed at uninstall Look at a verbose log file. It will show you the action states of the Components. On Wed, Mar 16, 2011 at 6:53 AM, The Eligible Bachelors < theeligiblebachel...@yahoo.com> wrote: > I am having trouble figuring out why a component is not being removed at > uninstall time. This problem happens when the MSI is run in Windows 7. When > run in XP, the component is getting removed as expected. > > The Wix file is somewhat complex and contains a REINSTALLMODE property. > > What I have done is generated a log during uninstall time for both the Win7 > and XP installers. But the diff is a mess. > > Any tips on how to debug this? > > > > > > -- > Colocation vs. Managed Hosting > A question and answer guide to determining the best fit > for your organization - today and in the future. > http://p.sf.net/sfu/internap-sfd2d > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > -- virtually, Rob Mensching - http://RobMensching.com LLC -- Colocation vs. Managed Hosting A question and answer guide to determining the best fit for your organization - today and in the future. http://p.sf.net/sfu/internap-sfd2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA The must-attend event for mobile developers. Connect with experts. Get tools for creating Super Apps. See the latest technologies. Sessions, hands-on labs, demos & much more. Register early & save! http://p.sf.net/sfu/rim-blackberry-1 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Multiple RadioButtonGroup controls in the same dialog
Could you show the markup you're using for the controls? -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Multiple-RadioButtonGroup-controls-in-the-same-dialog-tp6644681p6646096.html Sent from the wix-users mailing list archive at Nabble.com. -- BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA The must-attend event for mobile developers. Connect with experts. Get tools for creating Super Apps. See the latest technologies. Sessions, hands-on labs, demos & much more. Register early & save! http://p.sf.net/sfu/rim-blackberry-1 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Executing a Batch File during Install
I'm not sure if you ever got this figured out. If not, can you show us the markup for the custom action? -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Executing-a-Batch-File-during-Install-tp6579146p6646053.html Sent from the wix-users mailing list archive at Nabble.com. -- BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA The must-attend event for mobile developers. Connect with experts. Get tools for creating Super Apps. See the latest technologies. Sessions, hands-on labs, demos & much more. Register early & save! http://p.sf.net/sfu/rim-blackberry-1 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Fileshare permissions
I am trying to create a file share using Wix. Here is the fileshare fragment I'm using: The user is defined as follows: and the value is passed in as a parameter during install. The install works without any error, and the file share gets created. I can even see the user account listed in the Sharing properties with Read/Write access. However, when I try to access it as \\localhost\SharedMQStorage I get an access denied error (see attached screenshots). Any ideas what might be going wrong? Thanks, Atul -- BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA The must-attend event for mobile developers. Connect with experts. Get tools for creating Super Apps. See the latest technologies. Sessions, hands-on labs, demos & much more. Register early & save! http://p.sf.net/sfu/rim-blackberry-1___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Burn - Determine if bundle is already installed
I am using a managed bootstrapper application and I am trying to figure out how to detect if the bundle is already installed. I am able to detect the packages by handling the *DetectPackageComplete* event but I can't just assume that the bundle is installed by detecting one of the packages in it (it might have been installed outside of the bundle). I also tried handling the *DetectRelatedBundle* event but it never fires (and judging by the name I wouldn't expect it to in this case). To be honest I was expecting there to be something like a DetectBundle event but I don't see one. *All that being said, anybody have any clue on how to detect if the current bundle is already installed?* -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-Determine-if-bundle-is-already-installed-tp6645777p6645777.html Sent from the wix-users mailing list archive at Nabble.com. -- BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA The must-attend event for mobile developers. Connect with experts. Get tools for creating Super Apps. See the latest technologies. Sessions, hands-on labs, demos & much more. Register early & save! http://p.sf.net/sfu/rim-blackberry-1 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Files aren't removed on uninstall
You'll need to generate a verbose log file. Edwin G. Castro Software Developer - Staff Digital Channels Fiserv Office: 503-746-0643 Fax: 503-617-0291 www.fiserv.com Please consider the environment before printing this e-mail > -Original Message- > From: Joe Tilley [mailto:jtil...@fwmurphy.com] > Sent: Tuesday, August 02, 2011 9:29 AM > To: wix-users@lists.sourceforge.net > Subject: [WiX-users] Files aren't removed on uninstall > > Based on the example in the book "WiX: A Developer's Guide To Windows > Installer XML", I added an Upgrade element along with a launch Condition > inside my Product element to detect older versions and remove them during > installation. That part works wonderfully. However, when I run the > uninstallation, only the desktop shortcut is removed. None of the > files/folders in Program Files are removed. > > This behavior started after I added the following section of markup: > > > > > > > >Maximum="$(var.ProductVersion)" IncludeMaximum="no" > OnlyDetect="no" IgnoreRemoveFailure="yes" MigrateFeatures="yes" /> >Minimum="$(var.ProductVersion)" IncludeMinimum="no" OnlyDetect="yes" > /> > > > > > > > > > There is probably something I'm doing wrong in there. The uninstall > completes with no error. Any ideas as to what I'm doing wrong? > > Thanks in advance > _ > > Joe Tilley > > FW Murphy > > Software Engineer > > Office > > (918) 317-4130 > > Email > > jtil...@fwmurphy.com > > > > > > > “This message and any attachments may contain FW Murphy > information that is highly confidential, privileged, and exempt from > disclosure. Any recipient other than the intended recipient is advised that > dissemination, distribution, copying, or other use of this message is strictly > prohibited. If you have received this message in error, please notify the > sender immediately, plus delete the message and any backups.” > > -- > BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA The must- > attend event for mobile developers. Connect with experts. > Get tools for creating Super Apps. See the latest technologies. > Sessions, hands-on labs, demos & much more. Register early & save! > http://p.sf.net/sfu/rim-blackberry-1 > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users -- BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA The must-attend event for mobile developers. Connect with experts. Get tools for creating Super Apps. See the latest technologies. Sessions, hands-on labs, demos & much more. Register early & save! http://p.sf.net/sfu/rim-blackberry-1 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Files aren't removed on uninstall
Based on the example in the book "WiX: A Developer's Guide To Windows Installer XML", I added an Upgrade element along with a launch Condition inside my Product element to detect older versions and remove them during installation. That part works wonderfully. However, when I run the uninstallation, only the desktop shortcut is removed. None of the files/folders in Program Files are removed. This behavior started after I added the following section of markup: There is probably something I'm doing wrong in there. The uninstall completes with no error. Any ideas as to what I'm doing wrong? Thanks in advance _ Joe Tilley FW Murphy Software Engineer Office (918) 317-4130 Email jtil...@fwmurphy.com “This message and any attachments may contain FW Murphy information that is highly confidential, privileged, and exempt from disclosure. Any recipient other than the intended recipient is advised that dissemination, distribution, copying, or other use of this message is strictly prohibited. If you have received this message in error, please notify the sender immediately, plus delete the message and any backups.” -- BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA The must-attend event for mobile developers. Connect with experts. Get tools for creating Super Apps. See the latest technologies. Sessions, hands-on labs, demos & much more. Register early & save! http://p.sf.net/sfu/rim-blackberry-1 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Installing https WCF Webservices
We've had quite a bit of hands on experience with this sort of thing lately.
In one project, we bound a certificate to a port during the install so that
we could use SSL (the same as if you were to go into IIS and set the binding
and choose a certificate). In another case, we used ws-security in the
web.config by altering the XML at install time. Here I'll just talk about
the former -- simply binding a certificate to a port.
To get a port to communicate over SSL, you have to bind a certificate to
that port. The *netsh* command-line utility works nicely for this. Given an
IP, port and thumbprint of the certificate you want to use, it can bind that
certificate to the port.
I use the following .cmd script, passing in the necessary thumbprint (which
I call "CERTHASH"), and IP and port to bind to.
*
@ECHO OFF
REM Sets the certificate for for the port where the WCF runs
REM Note that we get the appid values from the GUIDs in the AssemblyInfo.cs
files for the WCF
REM Dev cert hash example: d4675cce6b8e85678826c3d426dd213ce4731e5d
SET CERTHASH=%1
SET IP=%2
SET PORT=%3
ECHO Binding certificate to port %port%
REM Bind the certificate to the WCF port
netsh http add sslcert ipport=%IP%:%PORT% certhash=%CERTHASH%
appid={01C40DD4-FF57-445F-BEDA-06E473DE8589}
ECHO Done.
@ECHO ON*
The appId comes from the Properties\AssemblyInfo.cs file, where I use the
[assembly: Guid ...]. The netsh documentation is actually kind of vague
about this, so I probably could have used any GUID. Oh well.
I've also got a similar "rollback" script:
*@ECHO OFF
SET IP=%1
SET PORT=%2
ECHO Deleting certificate from port binding for port %PORT%
netsh http delete sslcert ipport=%IP%:%PORT%
ECHO Done.
@ECHO ON*
I install these two shell scripts along with my application. Here are the
components I use:
I set up some custom actions:
And then I schedule them:
1
REMOVE="ALL"
* NOT Installed
NOT
Installed
REMOVE="ALL"*
Notice that I also used another custom action to get the IP address based on
the DNS of the website (I used C# for that) and one to get the port I'd
bound to, if this is happening during an uninstall, from the registry. That
way, I would have the port again, even though the user didn't enter them
into a UI.
If you're going the ws-security route, that's another thing. I'm saying a
lot of stuff here. The main thing is just to use netsh to bind the
certificate to the port and presto you're ready for HTTPS. We even use this
to have SSL over a port other than 443.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Installing-https-WCF-Webservices-tp6641855p6645377.html
Sent from the wix-users mailing list archive at Nabble.com.
--
BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA
The must-attend event for mobile developers. Connect with experts.
Get tools for creating Super Apps. See the latest technologies.
Sessions, hands-on labs, demos & much more. Register early & save!
http://p.sf.net/sfu/rim-blackberry-1
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] iis:WebSite - SiteId required for IIS 6 but not IIS 7?
In our development environment, we are installing to an existing website hosted in IIS 7 (Server 2008). However, in our QA environment, we are installing to an existing site hosted in IIS 6 (Server 2003). I've found that in IIS 6, the existing website can't be found unless we add the SiteId="*" attribute. Is this a known issue, maybe slated to be fixed in WiX 3.6? We're using WiX 3.5 now. Here are the two WebSite elements I'm using, wherein only one is used, depending on the environment. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/iis-WebSite-SiteId-required-for-IIS-6-but-not-IIS-7-tp6645304p6645304.html Sent from the wix-users mailing list archive at Nabble.com. -- BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA The must-attend event for mobile developers. Connect with experts. Get tools for creating Super Apps. See the latest technologies. Sessions, hands-on labs, demos & much more. Register early & save! http://p.sf.net/sfu/rim-blackberry-1 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Multiple RadioButtonGroup controls in the same dialog
Hello, I have placed 2 radiobuttongroup controls in the same dialog but the radio buttons in the second group appear to be disabled and so the selection can't be changed. The radio buttons in the first group work fine. Can anyone please explain what I am doing wrong? Thank you, Anil. -- BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA The must-attend event for mobile developers. Connect with experts. Get tools for creating Super Apps. See the latest technologies. Sessions, hands-on labs, demos & much more. Register early & save! http://p.sf.net/sfu/rim-blackberry-1 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Mutually Exclusive Patches
According to the patching whitepaper, it's impossible for both patches to supersede each other - one has to be a later in the sequence than the other, so in the usual one family scenario it isn't going to work. The default validation flags are to match all 3 fields of the targets product version. As long as you change the product version in both patches, then shouldn't installing one prevent the other from being applied ? You might need to ensure MinorUpdateTargetRTM=no, which I think is the default. -Original Message- From: Brian Lemke [mailto:brian.le...@apihealthcare.com] Sent: 01 August 2011 20:52 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Mutually Exclusive Patches Is there any way of creating a set of patches that are mutually exclusive? I have software that has two patches A and B. Now If the software has patch A installed it is to prevent install of B. I get this by sequencing A after B and marking A to supersede B (now if you uninstall patch A it would apply B I am fine with that). However I need to also ensure that if they installed B first that they cannot install A. The sequence mentioned before is directly opposite that and will allow for A to patch over B. I was contemplating writing some sort of custom action to do this logic check but wasn't sure if there was something I am overlooking in the sequencing or patching in general. Can anyone help me? Am I left to write some custom action to detect this scenario and prevent it myself? --Brian This message (including any attachments) contains confidential and privileged information intended for a specific purpose, and is protected by law. If you are not the intended recipient, you must delete this message and any attachments. You are hereby notified that any disclosure, copying, or distribution of this message, or any attachments, or the taking of any action based on it, is strictly prohibited. Opinions, conclusions, and other information in this message that do not relate to the official business of API Healthcare Corporation (API Healthcare) shall be understood as neither given nor endorsed by API Healthcare. API Healthcare Corporation 1550 Innovation Way Hartford, WI 53027 - - BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA The must-attend event for mobile developers. Connect with experts. Get tools for creating Super Apps. See the latest technologies. Sessions, hands-on labs, demos & much more. Register early & save! http://p.sf.net/sfu/rim-blackberry-1 ___ 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. -- BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA The must-attend event for mobile developers. Connect with experts. Get tools for creating Super Apps. See the latest technologies. Sessions, hands-on labs, demos & much more. Register early & save! http://p.sf.net/sfu/rim-blackberry-1 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
