date:20120426

Log file is created in %TEMP% by default.

On Thu, Apr 26, 2012 at 9:56 PM, Anirban Paul wrote:

> I downloaded wix36.exe and installed Wix Toolset V3.6.2221.0. The
> uninstallation UI does not specify anything about the log file when the
> uninstall operation fails. Please let me know how to generate the log file
> in this scenario.
> Anirban
>
> On Thu, Apr 26, 2012 at 8:00 PM, Rob Mensching 
> wrote:
>
> > Please provide the log file.
> >
> > On Wed, Apr 25, 2012 at 11:00 PM, Anirban Paul <
> ani.banti.24...@gmail.com
> > >wrote:
> >
> > > As you said, I downloaded the WiX v3.6 RC0 (Released: Apr 3 2012) and
> > tried
> > > to uninstall the already installed version ( Wix Toolset V3.6.2221.0 )
> of
> > > Wix. But that version is not getting uninstalled!!!
> > > Currently Wix Toolset V3.6.2221.0 is installed in my computer. But I
> > failed
> > > to uninstall the version. Whenever I go to Add Remove Program  and
> click
> > on
> > > the Remove button of
> > > Wix Toolset V3.6.2221.0, It says "Failed to unistall"
> > > Please help.
> > >
> > > On Thu, Apr 26, 2012 at 11:04 AM, Anirban Paul <
> > ani.banti.24...@gmail.com
> > > >wrote:
> > >
> > > > Ok I shall try that and get back to you.
> > > > But let me know the wix variable names that are used to set
> > bootstrapper
> > > > dialog title and bootstrapper dialog icon.
> > > >
> > > >
> > > > On Thu, Apr 26, 2012 at 10:53 AM, Rob Mensching <
> r...@robmensching.com
> > > >wrote:
> > > >
> > > >> Sounds like you are using an old version. Upgrade to latest build
> for
> > > all
> > > >> that to work.
> > > >>
> > > >> On Wed, Apr 25, 2012 at 9:15 PM, Anirban Paul <
> > > ani.banti.24...@gmail.com
> > > >> >wrote:
> > > >>
> > > >> > Hi,
> > > >> > I have created a bootstrapper (using burn in visual studio 2010)
> > which
> > > >> > installs .Net framework4 as prerequisite and then installs the
> > actual
> > > >> > msi. Following are the problem that I am facing and I really need
> > your
> > > >> help
> > > >> > to resolve those problems.
> > > >> >
> > > >> > 1> I don't want the bootstrapper to have an entry in Add Remove
> > > >> Program;so
> > > >> > I am not using "Name" attribute in "Bundle" tag. But as a result
> of
> > > >> that,
> > > >> > my bootstrapper dialog displays only the text "Setup". Please let
> me
> > > >> know
> > > >> > is there any way to set the title text without specifying "Name"
> > > >> attribute
> > > >> > in "Bundle" tag.
> > > >> >
> > > >> > 2> I am unable to set the icon of bootstrapper dialog. How to do
> > this?
> > > >> >
> > > >> > 3> The bootstrapper exe is working fine but whenever I try to
> cancel
> > > the
> > > >> > installation in midway the bootstrapper crashes. Is that a bug in
> > Win
> > > >> 3.6
> > > >> > or I am doing something wrong?
> > > >> >
> > > >> > Please help me to resolve these problems.
> > > >> >
> > > >> >  Thanks in advance.
> > > >> >
> > > >> >
> > > >>
> > >
> >
> --
> > > >> > Live Security Virtual Conference
> > > >> > Exclusive live event will cover all the ways today's security and
> > > >> > threat landscape has changed and how IT managers can respond.
> > > >> Discussions
> > > >> > will include endpoint security, mobile security and the latest in
> > > >> malware
> > > >> > threats.
> http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> > > >> > ___
> > > >> > WiX-users mailing list
> > > >> > WiX-users@lists.sourceforge.net
> > > >> > https://lists.sourceforge.net/lists/listinfo/wix-users
> > > >> >
> > > >>
> > > >>
> > > >>
> > > >> --
> > > >> virtually, Rob Mensching - http://RobMensching.com LLC
> > > >>
> > > >>
> > >
> >
> --
> > > >> Live Security Virtual Conference
> > > >> Exclusive live event will cover all the ways today's security and
> > > >> threat landscape has changed and how IT managers can respond.
> > > Discussions
> > > >> will include endpoint security, mobile security and the latest in
> > > malware
> > > >> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> > > >> ___
> > > >> WiX-users mailing list
> > > >> WiX-users@lists.sourceforge.net
> > > >> https://lists.sourceforge.net/lists/listinfo/wix-users
> > > >>
> > > >
> > > >
> > >
> > >
> >
> --
> > > Live Security Virtual Conference
> > > Exclusive live event will cover all the ways today's security and
> > > threat landscape has changed and how IT managers can respond.
> Discussions
> > > will include endpoint security, mobile security and the latest in
> malware
> > > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> > > ___
> > > WiX-users mailing list
> > > WiX-users@lists.sourceforge.net
> > > https:/

Re: [WiX-users] Bundle failing to build after upgrading to latest release (3.6.2823)

2012-04-26 Thread Heath Stewart

This should be fixed in the next build of WiX out Monday evening. Please
verify and let me know.

Thanks,

On Thu, Apr 26, 2012 at 7:10 PM, Heath Stewart  wrote:

> I've opened
> https://sourceforge.net/tracker/?func=detail&aid=3521813&group_id=105970&atid=642714
>  to
> track this.
>
>
> On Wed, Apr 25, 2012 at 9:30 AM, Bob Arnson  wrote:
>
>> On 25-Apr-12 11:45, Pally Sandher wrote:
>> >   Microsoft (R) Windows Installer Xml Linker version
>> 3.6.2823.0
>> >   Copyright (C) Microsoft Corporation. All rights reserved.
>> > light.exe(0,0): error LGHT0001: An item with the same key has already
>> been added.
>> >   Exception Type: System.ArgumentException
>> That's bad. Can you unzip the .pdbs into your WiX directory to get line
>> numbers and file a bug?
>>
>> --
>> sig://boB
>> http://joyofsetup.com/
>>
>>
>>
>> --
>> Live Security Virtual Conference
>> Exclusive live event will cover all the ways today's security and
>> threat landscape has changed and how IT managers can respond. Discussions
>> will include endpoint security, mobile security and the latest in malware
>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>> ___
>> WiX-users mailing list
>> WiX-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/wix-users
>>
>
>
>
> --
> *Heath Stewart
> *Visual Studio Professional Deployment Experience team, Microsoft
> http://blogs.msdn.com/heaths
>



-- 
*Heath Stewart
*Visual Studio Professional Deployment Experience team, Microsoft
http://blogs.msdn.com/heaths
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Wix 3.6 Bootstrapper Issues

2012-04-26 Thread Anirban Paul

I downloaded wix36.exe and installed Wix Toolset V3.6.2221.0. The
uninstallation UI does not specify anything about the log file when the
uninstall operation fails. Please let me know how to generate the log file
in this scenario.
Anirban

On Thu, Apr 26, 2012 at 8:00 PM, Rob Mensching  wrote:

> Please provide the log file.
>
> On Wed, Apr 25, 2012 at 11:00 PM, Anirban Paul  >wrote:
>
> > As you said, I downloaded the WiX v3.6 RC0 (Released: Apr 3 2012) and
> tried
> > to uninstall the already installed version ( Wix Toolset V3.6.2221.0 ) of
> > Wix. But that version is not getting uninstalled!!!
> > Currently Wix Toolset V3.6.2221.0 is installed in my computer. But I
> failed
> > to uninstall the version. Whenever I go to Add Remove Program  and click
> on
> > the Remove button of
> > Wix Toolset V3.6.2221.0, It says "Failed to unistall"
> > Please help.
> >
> > On Thu, Apr 26, 2012 at 11:04 AM, Anirban Paul <
> ani.banti.24...@gmail.com
> > >wrote:
> >
> > > Ok I shall try that and get back to you.
> > > But let me know the wix variable names that are used to set
> bootstrapper
> > > dialog title and bootstrapper dialog icon.
> > >
> > >
> > > On Thu, Apr 26, 2012 at 10:53 AM, Rob Mensching  > >wrote:
> > >
> > >> Sounds like you are using an old version. Upgrade to latest build for
> > all
> > >> that to work.
> > >>
> > >> On Wed, Apr 25, 2012 at 9:15 PM, Anirban Paul <
> > ani.banti.24...@gmail.com
> > >> >wrote:
> > >>
> > >> > Hi,
> > >> > I have created a bootstrapper (using burn in visual studio 2010)
> which
> > >> > installs .Net framework4 as prerequisite and then installs the
> actual
> > >> > msi. Following are the problem that I am facing and I really need
> your
> > >> help
> > >> > to resolve those problems.
> > >> >
> > >> > 1> I don't want the bootstrapper to have an entry in Add Remove
> > >> Program;so
> > >> > I am not using "Name" attribute in "Bundle" tag. But as a result of
> > >> that,
> > >> > my bootstrapper dialog displays only the text "Setup". Please let me
> > >> know
> > >> > is there any way to set the title text without specifying "Name"
> > >> attribute
> > >> > in "Bundle" tag.
> > >> >
> > >> > 2> I am unable to set the icon of bootstrapper dialog. How to do
> this?
> > >> >
> > >> > 3> The bootstrapper exe is working fine but whenever I try to cancel
> > the
> > >> > installation in midway the bootstrapper crashes. Is that a bug in
> Win
> > >> 3.6
> > >> > or I am doing something wrong?
> > >> >
> > >> > Please help me to resolve these problems.
> > >> >
> > >> >  Thanks in advance.
> > >> >
> > >> >
> > >>
> >
> --
> > >> > Live Security Virtual Conference
> > >> > Exclusive live event will cover all the ways today's security and
> > >> > threat landscape has changed and how IT managers can respond.
> > >> Discussions
> > >> > will include endpoint security, mobile security and the latest in
> > >> malware
> > >> > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> > >> > ___
> > >> > WiX-users mailing list
> > >> > WiX-users@lists.sourceforge.net
> > >> > https://lists.sourceforge.net/lists/listinfo/wix-users
> > >> >
> > >>
> > >>
> > >>
> > >> --
> > >> virtually, Rob Mensching - http://RobMensching.com LLC
> > >>
> > >>
> >
> --
> > >> Live Security Virtual Conference
> > >> Exclusive live event will cover all the ways today's security and
> > >> threat landscape has changed and how IT managers can respond.
> > Discussions
> > >> will include endpoint security, mobile security and the latest in
> > malware
> > >> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> > >> ___
> > >> WiX-users mailing list
> > >> WiX-users@lists.sourceforge.net
> > >> https://lists.sourceforge.net/lists/listinfo/wix-users
> > >>
> > >
> > >
> >
> >
> --
> > Live Security Virtual Conference
> > Exclusive live event will cover all the ways today's security and
> > threat landscape has changed and how IT managers can respond. Discussions
> > will include endpoint security, mobile security and the latest in malware
> > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> > ___
> > WiX-users mailing list
> > WiX-users@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/wix-users
> >
>
>
>
> --
> virtually, Rob Mensching - http://RobMensching.com LLC
>
> --
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the l

Re: [WiX-users] Bundle failing to build after upgrading to latest release (3.6.2823)

2012-04-26 Thread Heath Stewart

I've opened
https://sourceforge.net/tracker/?func=detail&aid=3521813&group_id=105970&atid=642714
to
track this.

On Wed, Apr 25, 2012 at 9:30 AM, Bob Arnson  wrote:

> On 25-Apr-12 11:45, Pally Sandher wrote:
> >   Microsoft (R) Windows Installer Xml Linker version
> 3.6.2823.0
> >   Copyright (C) Microsoft Corporation. All rights reserved.
> > light.exe(0,0): error LGHT0001: An item with the same key has already
> been added.
> >   Exception Type: System.ArgumentException
> That's bad. Can you unzip the .pdbs into your WiX directory to get line
> numbers and file a bug?
>
> --
> sig://boB
> http://joyofsetup.com/
>
>
>
> --
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>



-- 
*Heath Stewart
*Visual Studio Professional Deployment Experience team, Microsoft
http://blogs.msdn.com/heaths
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Install Failed, Log Attached

2012-04-26 Thread Chad Petersen

Not sure it's what you want, but what I typically do in this case is run
REGASM /Regfile to generate a .REG file and then use Heat to convert
that .REG file into a .WXS fragment that I can then include in my
project.

-Original Message-
From: Sam Youtsey [mailto:sam.yout...@gmail.com] 
Sent: Thursday, April 26, 2012 3:21 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Install Failed, Log Attached

I've built the DLL with an interface for interacting with other COM
components, how does this differ from being a Win32 COM DLL? Thanks for
the assistance with this!

On Thu, Apr 26, 2012 at 3:16 PM, Wilson, Phil
wrote:

> You really have to say if it's a Win32 COM Dll or not. I can't see a 
> definitive statement one way or another. However if it is Win32 COM, 
> just use Heat.exe to generate the WiX source for the registration.
>
> Phil W
>
> -Original Message-
> From: Sam Youtsey [mailto:sam.yout...@gmail.com]
> Sent: Thursday, April 26, 2012 3:13 PM
> To: wix-users@lists.sourceforge.net
> Subject: Re: [WiX-users] Install Failed, Log Attached
>
> Once I've installed it into the CommonFiles directory how can I 
> register and access it through the system? This is typically done with

> RegAsm.exe on the dev machine but this isn't available on the client 
> machine. Eventually, I want to be able to see this DLL's classes
through Excel.
>
>
> > Well you can install assemblies (that supply COM interfaces) into 
> > the
> GAC.
> > But you are trying to install a Win32 COM DLL into the GAC? That 
> > won't work, and it's not a WiX issue - it doesn't matter what you 
> > use to build your MSI file because it's MSI that's doing the
install.
> > If it's Win32 COM, just install it in CommonFiles for your Company.
> > Phil W
> > -Original Message-
> > From: Sam Youtsey [mailto:sam.youtsey@...]
> > Sent: Thursday, April 26, 2012 1:41 PM
> > To: wix-users@...
> > Subject: Re: [WiX-users] Install Failed, Log Attached Ah, I wasn't 
> > aware COM DLLs couldn't be installed into the GAC. What's an 
> > appropriate course of action for using them on the client system if 
> > I still wanted to use WiX?
> > > And the TLB file is in the same component as the assembly or is 
> > > somehow being installed to the GAC? That could explain an error 
> > > FUSION_E_UNEXPECTED_MODULE_FOUND.
> > > Phil W
> > > -Original Message-
> > > From: John Cooper [mailto:JoCooper@...]
> > > Sent: Thursday, April 26, 2012 12:35 PM
> > > To: General discussion for Windows Installer XML toolset.
> > > Subject: Re: [WiX-users] Install Failed, Log Attached A TLB files 
> > > strongly suggests that this is a COM and/or native DLL. I don't 
> > > think that's a candidate for the GAC either way.
> > > --
> > > John Merryweather Cooper
> > > Build & Install Engineer - ESA
> > > Jack Henry & Associates, Inc.(r)
> > > Shawnee Mission, KS 66227
> > > Office: 913-341-3434 x791011
> > > JoCooper@...
> > > http://www.jackhenry.com
> > > -Original Message-
> > > From: Sam Youtsey [mailto:sam.youtsey@...]
> > > Sent: Thursday, April 26, 2012 2:28 PM
> > > To: wix-users@...
> > > Subject: Re: [WiX-users] Install Failed, Log Attached Yeah, it's a

> > > DLL. There don't seem to be any config files associated, just the 
> > > TLB file. Anything else to look for?
> > > That HRESULT is FUSION_E_UNEXPECTED_MODULE_FOUND.
> > > > http://blogs.msdn.com/b/astebner/archive/2004/11/10/255346.aspx
> > > > Is there a config file associated with the assembly (maybe 
> > > > because it's a policy assembly)?
> > > > Is it actually a Dll?
> > > > Phil W
> > > > -Original Message-
> > > > From: Sam Youtsey [mailto:sam.youtsey@...]
> > > > Sent: Thursday, April 26, 2012 10:35 AM
> > > > To: wix-users@...
> > > > Subject: [WiX-users] Install Failed, Log Attached Hi all, My 
> > > > installer doesn't seem to be installing anything properly. Any 
> > > > chance I could get some help with it?
> > > > Here's the .wxs file:
> > > >   > > > xmlns="http://schemas.microsoft.com/wix/2006/wi";>
> > > >  > > > Name="MyProg"
> > > > Language="1033"
> > > > Version="$(var.ProductVersion)"
> > > > Manufacturer="MyCompany"
> > > > UpgradeCode="MyGuid2">
> > > >  > > InstallScope="perMachine"
> > > > />
> > > >   > > > EmbedCab="yes"/>  > > > Level="1">  
> > > > > > > Name="SourceDir">
> >  > > > Name="Program Files">  > > > Name="MyCompany"> 

> > > >  
> > > >  > > > Directory="INSTALLFOLDER">
> > > >  
>  > > > Source="..\MyProg\bin\Debug\MyProg.dll" KeyPath="yes"
> > > > Assembly=".net">
> > > >  > > > Source="..\MyProg\bin\Debug\MyProg.tlb">
> > > >  > > > Source="..\$(var.JavascriptNET)\Noesis.Javascript.dll" />  > > > Id="MyProg_Demo" Source="..\MyProg_Demo.xlsm">
> > > > 
> > > > 
> > > > 
> > > > 
> > > > And here's around the error that I'm seeing in the log:
> > > > MSI (s) (CC:68) [10:04:32:829]: Executing op:
> > > > UpgradeCodePublish(UpgradeCode={MyGuid3})
> > > > MSI (s) (CC:68) [10:04:32:829]:

Re: [WiX-users] Install Failed, Log Attached

I've built the DLL with an interface for interacting with other COM
components, how does this differ from being a Win32 COM DLL? Thanks for the
assistance with this!

On Thu, Apr 26, 2012 at 3:16 PM, Wilson, Phil wrote:

> You really have to say if it's a Win32 COM Dll or not. I can't see a
> definitive statement one way or another. However if it is Win32 COM, just
> use Heat.exe to generate the WiX source for the registration.
>
> Phil W
>
> -Original Message-
> From: Sam Youtsey [mailto:sam.yout...@gmail.com]
> Sent: Thursday, April 26, 2012 3:13 PM
> To: wix-users@lists.sourceforge.net
> Subject: Re: [WiX-users] Install Failed, Log Attached
>
> Once I've installed it into the CommonFiles directory how can I register
> and access it through the system? This is typically done with RegAsm.exe on
> the dev machine but this isn't available on the client machine. Eventually,
> I want to be able to see this DLL's classes through Excel.
>
>
> > Well you can install assemblies (that supply COM interfaces) into the
> GAC.
> > But you are trying to install a Win32 COM DLL into the GAC? That won't
> > work, and it's not a WiX issue - it doesn't matter what you use to
> > build your MSI file because it's MSI that's doing the install.
> > If it's Win32 COM, just install it in CommonFiles for your Company.
> > Phil W
> > -Original Message-
> > From: Sam Youtsey [mailto:sam.youtsey@...]
> > Sent: Thursday, April 26, 2012 1:41 PM
> > To: wix-users@...
> > Subject: Re: [WiX-users] Install Failed, Log Attached Ah, I wasn't
> > aware COM DLLs couldn't be installed into the GAC. What's an
> > appropriate course of action for using them on the client system if I
> > still wanted to use WiX?
> > > And the TLB file is in the same component as the assembly or is
> > > somehow being installed to the GAC? That could explain an error
> > > FUSION_E_UNEXPECTED_MODULE_FOUND.
> > > Phil W
> > > -Original Message-
> > > From: John Cooper [mailto:JoCooper@...]
> > > Sent: Thursday, April 26, 2012 12:35 PM
> > > To: General discussion for Windows Installer XML toolset.
> > > Subject: Re: [WiX-users] Install Failed, Log Attached A TLB files
> > > strongly suggests that this is a COM and/or native DLL. I don't
> > > think that's a candidate for the GAC either way.
> > > --
> > > John Merryweather Cooper
> > > Build & Install Engineer - ESA
> > > Jack Henry & Associates, Inc.(r)
> > > Shawnee Mission, KS 66227
> > > Office: 913-341-3434 x791011
> > > JoCooper@...
> > > http://www.jackhenry.com
> > > -Original Message-
> > > From: Sam Youtsey [mailto:sam.youtsey@...]
> > > Sent: Thursday, April 26, 2012 2:28 PM
> > > To: wix-users@...
> > > Subject: Re: [WiX-users] Install Failed, Log Attached Yeah, it's a
> > > DLL. There don't seem to be any config files associated, just the
> > > TLB file. Anything else to look for?
> > > That HRESULT is FUSION_E_UNEXPECTED_MODULE_FOUND.
> > > > http://blogs.msdn.com/b/astebner/archive/2004/11/10/255346.aspx
> > > > Is there a config file associated with the assembly (maybe because
> > > > it's a policy assembly)?
> > > > Is it actually a Dll?
> > > > Phil W
> > > > -Original Message-
> > > > From: Sam Youtsey [mailto:sam.youtsey@...]
> > > > Sent: Thursday, April 26, 2012 10:35 AM
> > > > To: wix-users@...
> > > > Subject: [WiX-users] Install Failed, Log Attached Hi all, My
> > > > installer doesn't seem to be installing anything properly. Any
> > > > chance I could get some help with it?
> > > > Here's the .wxs file:
> > > >   > > > xmlns="http://schemas.microsoft.com/wix/2006/wi";>
> > > >  > > > Name="MyProg"
> > > > Language="1033"
> > > > Version="$(var.ProductVersion)"
> > > > Manufacturer="MyCompany"
> > > > UpgradeCode="MyGuid2">
> > > >  > > InstallScope="perMachine"
> > > > />
> > > >   > > > EmbedCab="yes"/>  > > > Level="1">  
> > > >   
> >  > > > Name="Program Files">  > > > Name="MyCompany"> 
> > > > 
> > > > 
> > > >  
>  > > > Source="..\MyProg\bin\Debug\MyProg.dll" KeyPath="yes"
> > > > Assembly=".net">
> > > >  > > > Source="..\MyProg\bin\Debug\MyProg.tlb">
> > > >  > > > Source="..\$(var.JavascriptNET)\Noesis.Javascript.dll" />  > > > Id="MyProg_Demo" Source="..\MyProg_Demo.xlsm">
> > > > 
> > > > 
> > > > 
> > > > 
> > > > And here's around the error that I'm seeing in the log:
> > > > MSI (s) (CC:68) [10:04:32:829]: Executing op:
> > > > UpgradeCodePublish(UpgradeCode={MyGuid3})
> > > > MSI (s) (CC:68) [10:04:32:829]: Executing op:
> > > > SourceListPublish(NumberOfDisks=1)
> > > > MSI (s) (CC:68) [10:04:32:839]: Note: 1: 1402 2:
> > > > UNKNOWN\Installer\Products\xxx\SourceList 3: 2 MSI (s) (CC:68)
> > > > [10:04:32:859]: Executing op: ProductPublishClient(,,) MSI (s)
> > > > (CC:68)
> > > > [10:04:32:879]: Executing op:
> > > >
> > > > SourceListRegisterLastUsed(SourceProduct={MyGuid3},LastUsedSource=C:
> > > > \U
> > > > sers\Clean\Downloads\) MSI (s) (CC:68) [10:04:32:919]: Entering
> > > > CMsiConfigurationManager::SetLastUsedSou

Re: [WiX-users] Install Failed, Log Attached

You really have to say if it's a Win32 COM Dll or not. I can't see a definitive 
statement one way or another. However if it is Win32 COM, just use Heat.exe to 
generate the WiX source for the registration.

Phil W

-Original Message-
From: Sam Youtsey [mailto:sam.yout...@gmail.com]
Sent: Thursday, April 26, 2012 3:13 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Install Failed, Log Attached

Once I've installed it into the CommonFiles directory how can I register and 
access it through the system? This is typically done with RegAsm.exe on the dev 
machine but this isn't available on the client machine. Eventually, I want to 
be able to see this DLL's classes through Excel.


> Well you can install assemblies (that supply COM interfaces) into the GAC.
> But you are trying to install a Win32 COM DLL into the GAC? That won't
> work, and it's not a WiX issue - it doesn't matter what you use to
> build your MSI file because it's MSI that's doing the install.
> If it's Win32 COM, just install it in CommonFiles for your Company.
> Phil W
> -Original Message-
> From: Sam Youtsey [mailto:sam.youtsey@...]
> Sent: Thursday, April 26, 2012 1:41 PM
> To: wix-users@...
> Subject: Re: [WiX-users] Install Failed, Log Attached Ah, I wasn't
> aware COM DLLs couldn't be installed into the GAC. What's an
> appropriate course of action for using them on the client system if I
> still wanted to use WiX?
> > And the TLB file is in the same component as the assembly or is
> > somehow being installed to the GAC? That could explain an error
> > FUSION_E_UNEXPECTED_MODULE_FOUND.
> > Phil W
> > -Original Message-
> > From: John Cooper [mailto:JoCooper@...]
> > Sent: Thursday, April 26, 2012 12:35 PM
> > To: General discussion for Windows Installer XML toolset.
> > Subject: Re: [WiX-users] Install Failed, Log Attached A TLB files
> > strongly suggests that this is a COM and/or native DLL. I don't
> > think that's a candidate for the GAC either way.
> > --
> > John Merryweather Cooper
> > Build & Install Engineer - ESA
> > Jack Henry & Associates, Inc.(r)
> > Shawnee Mission, KS 66227
> > Office: 913-341-3434 x791011
> > JoCooper@...
> > http://www.jackhenry.com
> > -Original Message-
> > From: Sam Youtsey [mailto:sam.youtsey@...]
> > Sent: Thursday, April 26, 2012 2:28 PM
> > To: wix-users@...
> > Subject: Re: [WiX-users] Install Failed, Log Attached Yeah, it's a
> > DLL. There don't seem to be any config files associated, just the
> > TLB file. Anything else to look for?
> > That HRESULT is FUSION_E_UNEXPECTED_MODULE_FOUND.
> > > http://blogs.msdn.com/b/astebner/archive/2004/11/10/255346.aspx
> > > Is there a config file associated with the assembly (maybe because
> > > it's a policy assembly)?
> > > Is it actually a Dll?
> > > Phil W
> > > -Original Message-
> > > From: Sam Youtsey [mailto:sam.youtsey@...]
> > > Sent: Thursday, April 26, 2012 10:35 AM
> > > To: wix-users@...
> > > Subject: [WiX-users] Install Failed, Log Attached Hi all, My
> > > installer doesn't seem to be installing anything properly. Any
> > > chance I could get some help with it?
> > > Here's the .wxs file:
> > >   > > xmlns="http://schemas.microsoft.com/wix/2006/wi";>
> > >  > > Name="MyProg"
> > > Language="1033"
> > > Version="$(var.ProductVersion)"
> > > Manufacturer="MyCompany"
> > > UpgradeCode="MyGuid2">
> > >  > InstallScope="perMachine"
> > > />
> > >   > > EmbedCab="yes"/>  > > Level="1">  
> > >   
>  > > Name="Program Files">  > > Name="MyCompany"> 
> > > 
> > > 
> > >> > Id="MyProgDLL"
> > > Source="..\MyProg\bin\Debug\MyProg.dll" KeyPath="yes"
> > > Assembly=".net">
> > >  > > Source="..\MyProg\bin\Debug\MyProg.tlb">
> > >  > > Source="..\$(var.JavascriptNET)\Noesis.Javascript.dll" />  > > Id="MyProg_Demo" Source="..\MyProg_Demo.xlsm">
> > > 
> > > 
> > > 
> > > 
> > > And here's around the error that I'm seeing in the log:
> > > MSI (s) (CC:68) [10:04:32:829]: Executing op:
> > > UpgradeCodePublish(UpgradeCode={MyGuid3})
> > > MSI (s) (CC:68) [10:04:32:829]: Executing op:
> > > SourceListPublish(NumberOfDisks=1)
> > > MSI (s) (CC:68) [10:04:32:839]: Note: 1: 1402 2:
> > > UNKNOWN\Installer\Products\xxx\SourceList 3: 2 MSI (s) (CC:68)
> > > [10:04:32:859]: Executing op: ProductPublishClient(,,) MSI (s)
> > > (CC:68)
> > > [10:04:32:879]: Executing op:
> > >
> > > SourceListRegisterLastUsed(SourceProduct={MyGuid3},LastUsedSource=C:
> > > \U
> > > sers\Clean\Downloads\) MSI (s) (CC:68) [10:04:32:919]: Entering
> > > CMsiConfigurationManager::SetLastUsedSource.
> > > MSI (s) (CC:68) [10:04:32:939]: Setting cached product context:
> > > machine assigned for product: xxx MSI (s) (CC:68) [10:04:32:949]:
> > > Specifed source is already in a list.
> > > MSI (s) (CC:68) [10:04:32:979]: User policy value 'SearchOrder' is
> 'nmu'
> > > MSI (s) (CC:68) [10:04:32:989]: Adding new sources is allowed.
> > > MSI (s) (CC:68) [10:04:33:009]: Set LastUsedSource to:
> > > C:\Users\Clean\Downloads

Re: [WiX-users] Install Failed, Log Attached

Once I've installed it into the CommonFiles directory how can I register
and access it through the system? This is typically done with RegAsm.exe on
the dev machine but this isn't available on the client machine. Eventually,
I want to be able to see this DLL's classes through Excel.


> Well you can install assemblies (that supply COM interfaces) into the GAC.
> But you are trying to install a Win32 COM DLL into the GAC? That won't
> work, and it's not a WiX issue - it doesn't matter what you use to build
> your MSI file because it's MSI that's doing the install.
> If it's Win32 COM, just install it in CommonFiles for your Company.
> Phil W
> -Original Message-
> From: Sam Youtsey [mailto:sam.youtsey@...]
> Sent: Thursday, April 26, 2012 1:41 PM
> To: wix-users@...
> Subject: Re: [WiX-users] Install Failed, Log Attached
> Ah, I wasn't aware COM DLLs couldn't be installed into the GAC. What's an
> appropriate course of action for using them on the client system if I still
> wanted to use WiX?
> > And the TLB file is in the same component as the assembly or is
> > somehow being installed to the GAC? That could explain an error
> > FUSION_E_UNEXPECTED_MODULE_FOUND.
> > Phil W
> > -Original Message-
> > From: John Cooper [mailto:JoCooper@...]
> > Sent: Thursday, April 26, 2012 12:35 PM
> > To: General discussion for Windows Installer XML toolset.
> > Subject: Re: [WiX-users] Install Failed, Log Attached A TLB files
> > strongly suggests that this is a COM and/or native DLL. I don't think
> > that's a candidate for the GAC either way.
> > --
> > John Merryweather Cooper
> > Build & Install Engineer - ESA
> > Jack Henry & Associates, Inc.(r)
> > Shawnee Mission, KS 66227
> > Office: 913-341-3434 x791011
> > JoCooper@...
> > http://www.jackhenry.com
> > -Original Message-
> > From: Sam Youtsey [mailto:sam.youtsey@...]
> > Sent: Thursday, April 26, 2012 2:28 PM
> > To: wix-users@...
> > Subject: Re: [WiX-users] Install Failed, Log Attached Yeah, it's a
> > DLL. There don't seem to be any config files associated, just the TLB
> > file. Anything else to look for?
> > That HRESULT is FUSION_E_UNEXPECTED_MODULE_FOUND.
> > > http://blogs.msdn.com/b/astebner/archive/2004/11/10/255346.aspx
> > > Is there a config file associated with the assembly (maybe because
> > > it's a policy assembly)?
> > > Is it actually a Dll?
> > > Phil W
> > > -Original Message-
> > > From: Sam Youtsey [mailto:sam.youtsey@...]
> > > Sent: Thursday, April 26, 2012 10:35 AM
> > > To: wix-users@...
> > > Subject: [WiX-users] Install Failed, Log Attached Hi all, My
> > > installer doesn't seem to be installing anything properly. Any
> > > chance I could get some help with it?
> > > Here's the .wxs file:
> > >   > > xmlns="http://schemas.microsoft.com/wix/2006/wi";>
> > >  > > Name="MyProg"
> > > Language="1033"
> > > Version="$(var.ProductVersion)"
> > > Manufacturer="MyCompany"
> > > UpgradeCode="MyGuid2">
> > >  > InstallScope="perMachine"
> > > />
> > >   > > EmbedCab="yes"/>  > > Level="1">  
> > >   
>  > > Name="Program Files">  > > Name="MyCompany"> 
> > > 
> > > 
> > > 
> > >   > > Source="..\MyProg\bin\Debug\MyProg.dll" KeyPath="yes"
> > > Assembly=".net">
> > >  > > Source="..\MyProg\bin\Debug\MyProg.tlb">
> > >  > > Source="..\$(var.JavascriptNET)\Noesis.Javascript.dll" />  > > Id="MyProg_Demo" Source="..\MyProg_Demo.xlsm">
> > > 
> > > 
> > > 
> > > 
> > > And here's around the error that I'm seeing in the log:
> > > MSI (s) (CC:68) [10:04:32:829]: Executing op:
> > > UpgradeCodePublish(UpgradeCode={MyGuid3})
> > > MSI (s) (CC:68) [10:04:32:829]: Executing op:
> > > SourceListPublish(NumberOfDisks=1)
> > > MSI (s) (CC:68) [10:04:32:839]: Note: 1: 1402 2:
> > > UNKNOWN\Installer\Products\xxx\SourceList 3: 2 MSI (s) (CC:68)
> > > [10:04:32:859]: Executing op: ProductPublishClient(,,) MSI (s)
> > > (CC:68)
> > > [10:04:32:879]: Executing op:
> > >
> > > SourceListRegisterLastUsed(SourceProduct={MyGuid3},LastUsedSource=C:
> > > \U
> > > sers\Clean\Downloads\) MSI (s) (CC:68) [10:04:32:919]: Entering
> > > CMsiConfigurationManager::SetLastUsedSource.
> > > MSI (s) (CC:68) [10:04:32:939]: Setting cached product context:
> > > machine assigned for product: xxx MSI (s) (CC:68) [10:04:32:949]:
> > > Specifed source is already in a list.
> > > MSI (s) (CC:68) [10:04:32:979]: User policy value 'SearchOrder' is
> 'nmu'
> > > MSI (s) (CC:68) [10:04:32:989]: Adding new sources is allowed.
> > > MSI (s) (CC:68) [10:04:33:009]: Set LastUsedSource to:
> > > C:\Users\Clean\Downloads\.
> > > MSI (s) (CC:68) [10:04:33:029]: Set LastUsedType to: n.
> > > MSI (s) (CC:68) [10:04:33:039]: Set LastUsedIndex to: 1.
> > > MSI (s) (CC:68) [10:04:33:059]: Executing op:
> > > End(Checksum=0,ProgressTotalHDWord=0,ProgressTotalLDWord=4286641)
> > > MSI (s) (CC:68) [10:04:33:089]: Note: 1: 1935 2: {MyGuid3} 3:
> > > 0x80131043
> > 4:
> > > IAssemblyCacheItem 5: Commit
> > > 6:
> > >
> >
> MyProg,version="1.0.0.0",culture="neutra

Re: [WiX-users] Burn - Uninstall from programs & features causes reinstall of WiX built MSI package

PS: Thank you for dogfooding.

Based on your comment below, I take it you were not around in the days of
WiX v2.0. Back then things were still pretty raw, there was basically no
documentation, error messages were near uselss and we were still figuring
out the best way to solve some key problems.

The pioneers of those days helped us get to the product you see today in
WiX v3.5 and WiX v3.6 (minus Burn). Thanks for testing out the cutting edge
of WiX v3.6.

If it gets to be too much, you can always go back to WiX v3.5 and wait for
us to get WiX v3.6 production ready. Of course, it is always possible we'd
miss a bug that is core to some scenario you have and we'd queue the issue
to be addressed in WiX v3.7 (or WiX v4.0).

The cutting edge is named incredibly appropriately. 



On Thu, Apr 26, 2012 at 2:44 PM, Rob Mensching  wrote:

> I don't see the Reinstall in the log file. It looks like the ve2012.msi is
> being uninstalled and there was a user cancel.
>
>
> On Thu, Apr 26, 2012 at 7:56 AM, Pally Sandher wrote:
>
>>  >  SourceFile="..\..\..\install\ve2012.msi"
>>  After="SharedContentPatch"
>>  Compressed="yes"
>>  DisplayInternalUI="yes"
>>  ForcePerMachine="yes"
>>  Visible="no"
>>  Vital="yes"  />
>>
>> [06A0:0B6C][2012-04-26T14:56:20]: Burn v3.6.2816.0, Windows v6.1 (Build
>> 7601: Service Pack 1), path: C:\ProgramData\Package
>> Cache\{c4017423-730a-47fe-b473-eec0fa8071db}\ve2012setup.exe, cmdline:
>> '/uninstall -burn.unelevated
>> BurnPipe.{07CEB968-F392-4BE0-A3CF-F00525E5A2C7}
>> {50F4EFE9-76A5-45EF-B018-BF523A1D39A7} 1796'
>> [06A0:0B6C][2012-04-26T14:56:20]: Setting string variable 'WixBundleLog'
>> to value
>> 'C:\Users\zxc\AppData\Local\Temp\IES_Virtual_Environment_2012_20120426145620.log'
>> [06A0:0B6C][2012-04-26T14:56:21]: Detect 3 packages
>> [06A0:0B6C][2012-04-26T14:56:21]: Setting string variable 'NET4Installed'
>> to value '1'
>> [06A0:0B6C][2012-04-26T14:56:21]: Calculating patch applicability for
>> target product code: {92E2C426-6CDB-44D4-8D48-6414A442231D}, context:
>> Machine
>> [06A0:0B6C][2012-04-26T14:56:21]: Condition 'NET4Installed = 1' evaluates
>> to true.
>> [06A0:0B6C][2012-04-26T14:56:21]: Detected package: NET4.0, state:
>> Present, cached: Complete
>> [06A0:0B6C][2012-04-26T14:56:21]: Detected package: SharedContentPatch,
>> state: Present, cached: Complete
>> [06A0:0B6C][2012-04-26T14:56:21]: Detected package: SharedContentPatch
>> target: {92E2C426-6CDB-44D4-8D48-6414A442231D}, state: Present
>> [06A0:0B6C][2012-04-26T14:56:21]: Detected package: ve, state: Present,
>> cached: Complete
>> [06A0:0B6C][2012-04-26T14:56:21]: Detect complete, result: 0x0
>> [06A0:0B6C][2012-04-26T14:56:22]: Plan 3 packages, action: Uninstall
>> [06A0:0B6C][2012-04-26T14:56:22]: Setting string variable
>> 'WixBundleRollbackLog_ve' to value
>> 'C:\Users\zxc\AppData\Local\Temp\IES_Virtual_Environment_2012_20120426145620_0_ve_rollback.log'
>> [06A0:0B6C][2012-04-26T14:56:22]: Setting string variable
>> 'WixBundleLog_ve' to value
>> 'C:\Users\zxc\AppData\Local\Temp\IES_Virtual_Environment_2012_20120426145620_0_ve.log'
>> [06A0:0B6C][2012-04-26T14:56:22]: Skipping dependency registration on
>> package with no dependency providers: SharedContentPatch
>> [06A0:0B6C][2012-04-26T14:56:22]: Skipping dependency registration on
>> package with no dependency providers: NET4.0
>> [06A0:0B6C][2012-04-26T14:56:22]: Planned package: ve, state: Present,
>> default requested: Absent, ba requested: Absent, execute: Uninstall,
>> rollback: Install, cache: No, uncache: Yes, dependency: Unregister
>> [06A0:0B6C][2012-04-26T14:56:22]: Planned package: SharedContentPatch,
>> state: Present, default requested: None, ba requested: None, execute: None,
>> rollback: None, cache: No, uncache: No, dependency: None
>> [06A0:0B6C][2012-04-26T14:56:22]: Planned package: NET4.0, state:
>> Present, default requested: None, ba requested: None, execute: None,
>> rollback: None, cache: No, uncache: No, dependency: None
>> [06A0:0B6C][2012-04-26T14:56:22]: Plan complete, result: 0x0
>> [06A0:0B6C][2012-04-26T14:56:22]: Apply begin
>> [0704:05D4][2012-04-26T14:56:22]: Creating a system restore point.
>> [0704:05D4][2012-04-26T14:56:36]: Created a system restore point.
>> [0704:0B64][2012-04-26T14:56:39]: Verified existing payload: ve at path:
>> C:\ProgramData\Package
>> Cache\{4C98F99A-3A95-4291-915E-D869C8FD4814}v12.1.0.0\ve2012.msi.
>> [0704:05D4][2012-04-26T14:56:39]: Removed dependency:
>> {c4017423-730a-47fe-b473-eec0fa8071db} on package provider:
>> {4C98F99A-3A95-4291-915E-D869C8FD4814}, package ve
>> [0704:05D4][2012-04-26T14:56:39]: Applying execute package: ve, action:
>> Uninstall, path: C:\ProgramData\Package
>> Cache\{4C98F99A-3A95-4291-915E-D869C8FD4814}v12.1.0.0\ve2012.msi,
>> arguments: ' ALLUSERS="1" ARPSYSTEMCOMPONENT="1" MSIFASTINSTALL="7"'
>> [0704:05D4][2012-04-26T14:56:55]: Error 0x80070642:

Re: [WiX-users] Burn - MSIPackage InstallCondition evaluates to false, attempts minor upgrade

Uhh, you can't Major Upgrade if the ProductCode is the same. I'm confused.
People (maybe not you) have been asking for support for support for Minor
Updates for a long time. Burn automatically handles it when an MSI doesn't
change it's ProductCode but has a higher version. Burn also notifies the BA
when a higher version of the MSI (Minor Update or Major Upgrade MSIs) is
already present on the machine as a "downgrade".

I also don't understand the comment about patching. You can include patches
in Burn and it will install them. You can even "slipstream" MSPs and Burn
will be able to install the original MSI and the MSP in one transaction if
the MSI isn't present already and only install the MSP if the MSI is
already installed. It's really cool.

On Thu, Apr 26, 2012 at 8:06 AM, Pally Sandher wrote:

> Not too bothered about 3 so I'll ignore it for now. Just mentioned it as
> one our QA guys noticed it today.
>
> Regarding 4, I do have the same product code & higher version however my
> Upgrade Table code looks like the following:
>
>
>  
>   Property="NEWERVERSIONDETECTED" />
>   IncludeMaximum="yes" IgnoreRemoveFailure="no" OnlyDetect="no"
> Property="OLDERVERSIONBEINGUPGRADED" />
>
>
> Burn is trying to be too clever for its own good & changing the expected
> behaviour. I create a patch to upgrade from 2.0 or 2.1 to 2.2 as it's less
> than half the size of the full installer & I don't want to make users
> download something they don't need.
> Forcing someone to use a Minor Upgrade when they actually want either
> Major Upgrade or disallow installation seems rather counter-intuitive.
>
> I'll raise bugs in the SourceForge tracker for the other issues.
>
> Palbinder Sandher
> Software Platform Engineer
> T: +44 (0) 141 945 8500
> F: +44 (0) 141 945 8501
> http://www.iesve.com
>
> **Design, Simulate + Innovate with the **
> Integrated Environmental Solutions Limited. Registered in Scotland No.
> SC151456
> Registered Office - Helix Building, West Of Scotland Science Park, Glasgow
> G20 0SP
> Email Disclaimer
>
>
>
> -Original Message-
> From: Rob Mensching [mailto:r...@robmensching.com]
> Sent: 26 April 2012 15:41
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Burn - MSIPackage InstallCondition evaluates to
> false, attempts minor upgrade
>
> 1. Agree about the InstallCondition doc. Want to file a bug?
> 2. DisplayInternalUI on MSP might be broken. Want to file a bug?
> 3. Burn calculates size of installed packages + their cache size if they
> are cached. I'd need more details about the size being wrong to be more
> helpful.
> 4. The log file should explain when an MSI is being minor upgraded.
> Basically, if you have same product code but higher version, minor upgrade
> kicks in.
>
> On Thu, Apr 26, 2012 at 3:11 AM, Pally Sandher  >wrote:
>
> > I've removed the InstallCondition for the patch & it's now working as
> > intended. Thanks for the input on this however I would point out the
> > documentation mentions nothing about "patch applicability" & the
> > InstallCondition description says "A condition to evaluate before
> > installing the package. The package will only be installed if the
> condition
> > evaluates to true." which it's not unreasonable to assume the converse
> > (i.e. if InstallCondition evaluates to false, the package is not
> installed)
> > -> http://wix.sourceforge.net/manual-wix3/wix_xsd_msppackage.htm
> >
> > Anyone have any input on the previous questions I posted in this thread?
> > Why is DisplayInternalUI="yes" being ignored for MspPackage. Also
> > InstallSize seems to be ignored in MspPackage & ExePackage (tried setting
> > it to 0 and 1, same results with burn size entry in ARP showing the total
> > of all packages in the chain which is vastly inflated).
> >
> > My original question is still unanswered. Even without an
> InstallCondition
> > attribute for the MsiPackage it will still attempt a minor upgrade which
> is
> > contrary to the behaviour it exhibits when the MSI is manually run.
> >
> > Palbinder Sandher
> > Software Platform Engineer
> > T:+44 (0) 141 945 8500
> > F:+44 (0) 141 945 8501
> > http://www.iesve.com
> >
> > **Design, Simulate + Innovate with the **
> > Integrated Environmental Solutions Limited. Registered in Scotland No.
> > SC151456
> > Registered Office - Helix Building, West Of Scotland Science Park,
> Glasgow
> > G20 0SP
> > Email Disclaimer
> >
> >
> > -Original Message-
> > From: Rob Mensching [mailto:r...@robmensching.com]
> > Sent: 26 April 2012 06:51
> > To: General discussion for Windows Installer XML toolset.
> > Subject: Re: [WiX-users] Burn - MSIPackage InstallCondition evaluates to
> > false, attempts minor upgrade
> >
> > Sounds like we should scan patches for those that disallow removal and
> mark
> > them permanent.
> >
> > The InstallCondition behavior is expected. If the InstallCondition is
> false
> > that means "this Package should not be Installed" (aka: shou

Re: [WiX-users] Burn - Uninstall from programs & features causes reinstall of WiX built MSI package

I don't see the Reinstall in the log file. It looks like the ve2012.msi is
being uninstalled and there was a user cancel.

On Thu, Apr 26, 2012 at 7:56 AM, Pally Sandher wrote:

>SourceFile="..\..\..\install\ve2012.msi"
>  After="SharedContentPatch"
>  Compressed="yes"
>  DisplayInternalUI="yes"
>  ForcePerMachine="yes"
>  Visible="no"
>  Vital="yes"  />
>
> [06A0:0B6C][2012-04-26T14:56:20]: Burn v3.6.2816.0, Windows v6.1 (Build
> 7601: Service Pack 1), path: C:\ProgramData\Package
> Cache\{c4017423-730a-47fe-b473-eec0fa8071db}\ve2012setup.exe, cmdline:
> '/uninstall -burn.unelevated
> BurnPipe.{07CEB968-F392-4BE0-A3CF-F00525E5A2C7}
> {50F4EFE9-76A5-45EF-B018-BF523A1D39A7} 1796'
> [06A0:0B6C][2012-04-26T14:56:20]: Setting string variable 'WixBundleLog'
> to value
> 'C:\Users\zxc\AppData\Local\Temp\IES_Virtual_Environment_2012_20120426145620.log'
> [06A0:0B6C][2012-04-26T14:56:21]: Detect 3 packages
> [06A0:0B6C][2012-04-26T14:56:21]: Setting string variable 'NET4Installed'
> to value '1'
> [06A0:0B6C][2012-04-26T14:56:21]: Calculating patch applicability for
> target product code: {92E2C426-6CDB-44D4-8D48-6414A442231D}, context:
> Machine
> [06A0:0B6C][2012-04-26T14:56:21]: Condition 'NET4Installed = 1' evaluates
> to true.
> [06A0:0B6C][2012-04-26T14:56:21]: Detected package: NET4.0, state:
> Present, cached: Complete
> [06A0:0B6C][2012-04-26T14:56:21]: Detected package: SharedContentPatch,
> state: Present, cached: Complete
> [06A0:0B6C][2012-04-26T14:56:21]: Detected package: SharedContentPatch
> target: {92E2C426-6CDB-44D4-8D48-6414A442231D}, state: Present
> [06A0:0B6C][2012-04-26T14:56:21]: Detected package: ve, state: Present,
> cached: Complete
> [06A0:0B6C][2012-04-26T14:56:21]: Detect complete, result: 0x0
> [06A0:0B6C][2012-04-26T14:56:22]: Plan 3 packages, action: Uninstall
> [06A0:0B6C][2012-04-26T14:56:22]: Setting string variable
> 'WixBundleRollbackLog_ve' to value
> 'C:\Users\zxc\AppData\Local\Temp\IES_Virtual_Environment_2012_20120426145620_0_ve_rollback.log'
> [06A0:0B6C][2012-04-26T14:56:22]: Setting string variable
> 'WixBundleLog_ve' to value
> 'C:\Users\zxc\AppData\Local\Temp\IES_Virtual_Environment_2012_20120426145620_0_ve.log'
> [06A0:0B6C][2012-04-26T14:56:22]: Skipping dependency registration on
> package with no dependency providers: SharedContentPatch
> [06A0:0B6C][2012-04-26T14:56:22]: Skipping dependency registration on
> package with no dependency providers: NET4.0
> [06A0:0B6C][2012-04-26T14:56:22]: Planned package: ve, state: Present,
> default requested: Absent, ba requested: Absent, execute: Uninstall,
> rollback: Install, cache: No, uncache: Yes, dependency: Unregister
> [06A0:0B6C][2012-04-26T14:56:22]: Planned package: SharedContentPatch,
> state: Present, default requested: None, ba requested: None, execute: None,
> rollback: None, cache: No, uncache: No, dependency: None
> [06A0:0B6C][2012-04-26T14:56:22]: Planned package: NET4.0, state: Present,
> default requested: None, ba requested: None, execute: None, rollback: None,
> cache: No, uncache: No, dependency: None
> [06A0:0B6C][2012-04-26T14:56:22]: Plan complete, result: 0x0
> [06A0:0B6C][2012-04-26T14:56:22]: Apply begin
> [0704:05D4][2012-04-26T14:56:22]: Creating a system restore point.
> [0704:05D4][2012-04-26T14:56:36]: Created a system restore point.
> [0704:0B64][2012-04-26T14:56:39]: Verified existing payload: ve at path:
> C:\ProgramData\Package
> Cache\{4C98F99A-3A95-4291-915E-D869C8FD4814}v12.1.0.0\ve2012.msi.
> [0704:05D4][2012-04-26T14:56:39]: Removed dependency:
> {c4017423-730a-47fe-b473-eec0fa8071db} on package provider:
> {4C98F99A-3A95-4291-915E-D869C8FD4814}, package ve
> [0704:05D4][2012-04-26T14:56:39]: Applying execute package: ve, action:
> Uninstall, path: C:\ProgramData\Package
> Cache\{4C98F99A-3A95-4291-915E-D869C8FD4814}v12.1.0.0\ve2012.msi,
> arguments: ' ALLUSERS="1" ARPSYSTEMCOMPONENT="1" MSIFASTINSTALL="7"'
> [0704:05D4][2012-04-26T14:56:55]: Error 0x80070642: Failed to uninstall
> MSI package.
> [0704:05D4][2012-04-26T14:56:55]: Error 0x80070642: Failed to execute MSI
> package.
> [06A0:0B6C][2012-04-26T14:56:55]: Error 0x80070642: Failed to configure
> per-machine MSI package.
> [06A0:0B6C][2012-04-26T14:56:55]: Applied execute package: ve, result:
> 0x80070642, restart: None
> [06A0:0B6C][2012-04-26T14:56:55]: Error 0x80070642: Failed to execute MSI
> package.
> [0704:05D4][2012-04-26T14:56:55]: Skipped rollback of package: ve, action:
> Install, already: Present
> [06A0:0B6C][2012-04-26T14:56:55]: Applied rollback package: ve, result:
> 0x0, restart: None
> [0704:05D4][2012-04-26T14:56:55]: Registering dependency:
> {c4017423-730a-47fe-b473-eec0fa8071db} on package provider:
> {4C98F99A-3A95-4291-915E-D869C8FD4814}, package: ve
> [06A0:0B6C][2012-04-26T14:56:55]: Apply complete, result: 0x80070642,
> restart: None, ba requested restart:  No
>
>
> The MSI uninst

Re: [WiX-users] WiX3.6 Uninstall Failed / Installing Votive

Weird, log is only visible in nabble.

Anyway, it looks like you were the victim of an intermittent bug in that
build. You need to get the core.msi off your machine.  To do that try:

msiexec /x {0C317C74-81FB-4140-BE3C-33C074D511DE}

After that is removed, the bundle will hopefully uninstall correctly. If
not, you can try upgrading a newer version.

On Thu, Apr 26, 2012 at 10:31 AM, Dmuller720  wrote:

> The log is in the OP
>
> --
> View this message in context:
> http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/WiX3-6-Uninstall-Failed-Installing-Votive-tp7500775p7503666.html
> Sent from the wix-users mailing list archive at Nabble.com.
>
>
> --
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>



-- 
virtually, Rob Mensching - http://RobMensching.com LLC
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Install Failed, Log Attached

Well you can install assemblies (that supply COM interfaces) into the GAC. But 
you are trying to install a Win32 COM DLL into the GAC? That won't work, and 
it's not a WiX issue - it doesn't matter what you use to build your MSI file 
because it's MSI that's doing the install.  

If it's Win32 COM, just install it in CommonFiles for your Company. 

Phil W 

-Original Message-
From: Sam Youtsey [mailto:sam.yout...@gmail.com] 
Sent: Thursday, April 26, 2012 1:41 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Install Failed, Log Attached

Ah, I wasn't aware COM DLLs couldn't be installed into the GAC. What's an 
appropriate course of action for using them on the client system if I still 
wanted to use WiX?


> And the TLB file is in the same component as the assembly or is 
> somehow being installed to the GAC? That could explain an error 
> FUSION_E_UNEXPECTED_MODULE_FOUND.
> Phil W
> -Original Message-
> From: John Cooper [mailto:JoCooper@...]
> Sent: Thursday, April 26, 2012 12:35 PM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Install Failed, Log Attached A TLB files 
> strongly suggests that this is a COM and/or native DLL. I don't think 
> that's a candidate for the GAC either way.
> --
> John Merryweather Cooper
> Build & Install Engineer - ESA
> Jack Henry & Associates, Inc.(r)
> Shawnee Mission, KS 66227
> Office: 913-341-3434 x791011
> JoCooper@...
> http://www.jackhenry.com
> -Original Message-
> From: Sam Youtsey [mailto:sam.youtsey@...]
> Sent: Thursday, April 26, 2012 2:28 PM
> To: wix-users@...
> Subject: Re: [WiX-users] Install Failed, Log Attached Yeah, it's a 
> DLL. There don't seem to be any config files associated, just the TLB 
> file. Anything else to look for?
> That HRESULT is FUSION_E_UNEXPECTED_MODULE_FOUND.
> > http://blogs.msdn.com/b/astebner/archive/2004/11/10/255346.aspx
> > Is there a config file associated with the assembly (maybe because 
> > it's a policy assembly)?
> > Is it actually a Dll?
> > Phil W
> > -Original Message-
> > From: Sam Youtsey [mailto:sam.youtsey@...]
> > Sent: Thursday, April 26, 2012 10:35 AM
> > To: wix-users@...
> > Subject: [WiX-users] Install Failed, Log Attached Hi all, My 
> > installer doesn't seem to be installing anything properly. Any 
> > chance I could get some help with it?
> > Here's the .wxs file:
> >   > xmlns="http://schemas.microsoft.com/wix/2006/wi";>
> >  > Name="MyProg"
> > Language="1033"
> > Version="$(var.ProductVersion)"
> > Manufacturer="MyCompany"
> > UpgradeCode="MyGuid2">
> >  InstallScope="perMachine"
> > />
> >   > EmbedCab="yes"/>  > Level="1">   
> >
> >  > Name="Program Files">  > Name="MyCompany">  
> >  
> > 
> >  
> >   > Source="..\MyProg\bin\Debug\MyProg.dll" KeyPath="yes"
> > Assembly=".net">
> >  > Source="..\MyProg\bin\Debug\MyProg.tlb">
> >  > Source="..\$(var.JavascriptNET)\Noesis.Javascript.dll" />  > Id="MyProg_Demo" Source="..\MyProg_Demo.xlsm">
> > 
> > 
> > 
> > 
> > And here's around the error that I'm seeing in the log:
> > MSI (s) (CC:68) [10:04:32:829]: Executing op:
> > UpgradeCodePublish(UpgradeCode={MyGuid3})
> > MSI (s) (CC:68) [10:04:32:829]: Executing op:
> > SourceListPublish(NumberOfDisks=1)
> > MSI (s) (CC:68) [10:04:32:839]: Note: 1: 1402 2:
> > UNKNOWN\Installer\Products\xxx\SourceList 3: 2 MSI (s) (CC:68)
> > [10:04:32:859]: Executing op: ProductPublishClient(,,) MSI (s) 
> > (CC:68)
> > [10:04:32:879]: Executing op:
> >
> > SourceListRegisterLastUsed(SourceProduct={MyGuid3},LastUsedSource=C:
> > \U
> > sers\Clean\Downloads\) MSI (s) (CC:68) [10:04:32:919]: Entering 
> > CMsiConfigurationManager::SetLastUsedSource.
> > MSI (s) (CC:68) [10:04:32:939]: Setting cached product context:
> > machine assigned for product: xxx MSI (s) (CC:68) [10:04:32:949]:
> > Specifed source is already in a list.
> > MSI (s) (CC:68) [10:04:32:979]: User policy value 'SearchOrder' is 'nmu'
> > MSI (s) (CC:68) [10:04:32:989]: Adding new sources is allowed.
> > MSI (s) (CC:68) [10:04:33:009]: Set LastUsedSource to:
> > C:\Users\Clean\Downloads\.
> > MSI (s) (CC:68) [10:04:33:029]: Set LastUsedType to: n.
> > MSI (s) (CC:68) [10:04:33:039]: Set LastUsedIndex to: 1.
> > MSI (s) (CC:68) [10:04:33:059]: Executing op:
> > End(Checksum=0,ProgressTotalHDWord=0,ProgressTotalLDWord=4286641)
> > MSI (s) (CC:68) [10:04:33:089]: Note: 1: 1935 2: {MyGuid3} 3: 
> > 0x80131043
> 4:
> > IAssemblyCacheItem 5: Commit
> > 6:
> >
> MyProg,version="1.0.0.0",culture="neutral",publicKeyToken="1BC84BAF13B2B399",processorArchitecture="MSIL"
> > MSI (s) (CC:68) [10:04:33:280]: Note: 1: 2205 2: 3: Error MSI (s)
> > (CC:68)
> > [10:04:33:350]: Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM 
> > `Error` WHERE `Error` = 1935 MSI (c) (20:B0) [10:04:34:051]: Font
> created. Charset:
> > Req=0, Ret=0, Font:
> > Req=MS Shell Dlg, Ret=MS Shell Dlg
> > Error 1935. An error occurred during the installation of assembly
> >
> 'MyProg,version="1.0

Re: [WiX-users] Install Failed, Log Attached

Ah, I wasn't aware COM DLLs couldn't be installed into the GAC. What's an
appropriate course of action for using them on the client system if I still
wanted to use WiX?


> And the TLB file is in the same component as the assembly or is somehow
> being installed to the GAC? That could explain an error
> FUSION_E_UNEXPECTED_MODULE_FOUND.
> Phil W
> -Original Message-
> From: John Cooper [mailto:JoCooper@...]
> Sent: Thursday, April 26, 2012 12:35 PM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Install Failed, Log Attached
> A TLB files strongly suggests that this is a COM and/or native DLL. I
> don't think that's a candidate for the GAC either way.
> --
> John Merryweather Cooper
> Build & Install Engineer - ESA
> Jack Henry & Associates, Inc.(r)
> Shawnee Mission, KS 66227
> Office: 913-341-3434 x791011
> JoCooper@...
> http://www.jackhenry.com
> -Original Message-
> From: Sam Youtsey [mailto:sam.youtsey@...]
> Sent: Thursday, April 26, 2012 2:28 PM
> To: wix-users@...
> Subject: Re: [WiX-users] Install Failed, Log Attached
> Yeah, it's a DLL. There don't seem to be any config files associated, just
> the TLB file. Anything else to look for?
> That HRESULT is FUSION_E_UNEXPECTED_MODULE_FOUND.
> > http://blogs.msdn.com/b/astebner/archive/2004/11/10/255346.aspx
> > Is there a config file associated with the assembly (maybe because
> > it's a policy assembly)?
> > Is it actually a Dll?
> > Phil W
> > -Original Message-
> > From: Sam Youtsey [mailto:sam.youtsey@...]
> > Sent: Thursday, April 26, 2012 10:35 AM
> > To: wix-users@...
> > Subject: [WiX-users] Install Failed, Log Attached Hi all, My installer
> > doesn't seem to be installing anything properly. Any chance I could
> > get some help with it?
> > Here's the .wxs file:
> >   > xmlns="http://schemas.microsoft.com/wix/2006/wi";>
> >  > Name="MyProg"
> > Language="1033"
> > Version="$(var.ProductVersion)"
> > Manufacturer="MyCompany"
> > UpgradeCode="MyGuid2">
> >  InstallScope="perMachine"
> > />
> >> Id="ProductFeature" Title="MyProg" Level="1">  > Id="ProductComponents" /> > Id="TARGETDIR" Name="SourceDir">  > Name="Program Files">  > Name="MyCompany"> 
> > 
> > 
> > 
> >   > Source="..\MyProg\bin\Debug\MyProg.dll" KeyPath="yes"
> > Assembly=".net">
> >  > Source="..\MyProg\bin\Debug\MyProg.tlb">
> >  > Source="..\$(var.JavascriptNET)\Noesis.Javascript.dll" />  > Id="MyProg_Demo" Source="..\MyProg_Demo.xlsm">
> > 
> > 
> > 
> > 
> > And here's around the error that I'm seeing in the log:
> > MSI (s) (CC:68) [10:04:32:829]: Executing op:
> > UpgradeCodePublish(UpgradeCode={MyGuid3})
> > MSI (s) (CC:68) [10:04:32:829]: Executing op:
> > SourceListPublish(NumberOfDisks=1)
> > MSI (s) (CC:68) [10:04:32:839]: Note: 1: 1402 2:
> > UNKNOWN\Installer\Products\xxx\SourceList 3: 2 MSI (s) (CC:68)
> > [10:04:32:859]: Executing op: ProductPublishClient(,,) MSI (s) (CC:68)
> > [10:04:32:879]: Executing op:
> >
> > SourceListRegisterLastUsed(SourceProduct={MyGuid3},LastUsedSource=C:\U
> > sers\Clean\Downloads\) MSI (s) (CC:68) [10:04:32:919]: Entering
> > CMsiConfigurationManager::SetLastUsedSource.
> > MSI (s) (CC:68) [10:04:32:939]: Setting cached product context:
> > machine assigned for product: xxx MSI (s) (CC:68) [10:04:32:949]:
> > Specifed source is already in a list.
> > MSI (s) (CC:68) [10:04:32:979]: User policy value 'SearchOrder' is 'nmu'
> > MSI (s) (CC:68) [10:04:32:989]: Adding new sources is allowed.
> > MSI (s) (CC:68) [10:04:33:009]: Set LastUsedSource to:
> > C:\Users\Clean\Downloads\.
> > MSI (s) (CC:68) [10:04:33:029]: Set LastUsedType to: n.
> > MSI (s) (CC:68) [10:04:33:039]: Set LastUsedIndex to: 1.
> > MSI (s) (CC:68) [10:04:33:059]: Executing op:
> > End(Checksum=0,ProgressTotalHDWord=0,ProgressTotalLDWord=4286641)
> > MSI (s) (CC:68) [10:04:33:089]: Note: 1: 1935 2: {MyGuid3} 3: 0x80131043
> 4:
> > IAssemblyCacheItem 5: Commit
> > 6:
> >
> MyProg,version="1.0.0.0",culture="neutral",publicKeyToken="1BC84BAF13B2B399",processorArchitecture="MSIL"
> > MSI (s) (CC:68) [10:04:33:280]: Note: 1: 2205 2: 3: Error MSI (s)
> > (CC:68)
> > [10:04:33:350]: Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM
> > `Error` WHERE `Error` = 1935 MSI (c) (20:B0) [10:04:34:051]: Font
> created. Charset:
> > Req=0, Ret=0, Font:
> > Req=MS Shell Dlg, Ret=MS Shell Dlg
> > Error 1935. An error occurred during the installation of assembly
> >
> 'MyProg,version="1.0.0.0",culture="neutral",publicKeyToken="1BC84BAF13B2B399",processorArchitecture="MSIL"'.
> > Please refer to Help and Support for more information. HRESULT:
> 0x80131043.
> > assembly interface: IAssemblyCacheItem, function: Commit, component:
> > {MyGuid3}
> > MSI (s) (CC:68) [10:04:35:623]: Note: 1: 2205 2: 3: Error MSI (s)
> > (CC:68)
> > [10:04:35:633]: Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM
> > `Error` WHERE `Error` = 1709 MSI (s) (CC:68) [10:04:35:643]: Product:
> > MyProg -- Error 1935. An error occurred d

Re: [WiX-users] Install Failed, Log Attached

And the TLB file is in the same component as the assembly or is somehow being 
installed to the GAC? That could explain an error 
FUSION_E_UNEXPECTED_MODULE_FOUND. 
Phil W 

-Original Message-
From: John Cooper [mailto:jocoo...@jackhenry.com] 
Sent: Thursday, April 26, 2012 12:35 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Install Failed, Log Attached

A TLB files strongly suggests that this is a COM and/or native DLL.  I don't 
think that's a candidate for the GAC either way.

--
John Merryweather Cooper
Build & Install Engineer - ESA
Jack Henry & Associates, Inc.(r)
Shawnee Mission, KS  66227
Office:  913-341-3434 x791011
jocoo...@jackhenry.com
www.jackhenry.com 



-Original Message-
From: Sam Youtsey [mailto:sam.yout...@gmail.com]
Sent: Thursday, April 26, 2012 2:28 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Install Failed, Log Attached

 Yeah, it's a DLL. There don't seem to be any config files associated, just the 
TLB file. Anything else to look for?

That HRESULT is FUSION_E_UNEXPECTED_MODULE_FOUND.
> http://blogs.msdn.com/b/astebner/archive/2004/11/10/255346.aspx
> Is there a config file associated with the assembly (maybe because 
> it's a policy assembly)?
> Is it actually a Dll?
> Phil W
> -Original Message-
> From: Sam Youtsey [mailto:sam.youtsey@...]
> Sent: Thursday, April 26, 2012 10:35 AM
> To: wix-users@...
> Subject: [WiX-users] Install Failed, Log Attached Hi all, My installer 
> doesn't seem to be installing anything properly. Any chance I could 
> get some help with it?
> Here's the .wxs file:
>   xmlns="http://schemas.microsoft.com/wix/2006/wi";>
>  Name="MyProg"
> Language="1033"
> Version="$(var.ProductVersion)"
> Manufacturer="MyCompany"
> UpgradeCode="MyGuid2">
>  />
>Id="ProductFeature" Title="MyProg" Level="1">  Id="ProductComponents" /> Id="TARGETDIR" Name="SourceDir">  Name="Program Files">  Name="MyCompany">  
>  
> 
>  
>   Source="..\MyProg\bin\Debug\MyProg.dll" KeyPath="yes"
> Assembly=".net">
>  Source="..\MyProg\bin\Debug\MyProg.tlb">
>  Source="..\$(var.JavascriptNET)\Noesis.Javascript.dll" />  Id="MyProg_Demo" Source="..\MyProg_Demo.xlsm">
> 
> 
> 
> 
> And here's around the error that I'm seeing in the log:
> MSI (s) (CC:68) [10:04:32:829]: Executing op:
> UpgradeCodePublish(UpgradeCode={MyGuid3})
> MSI (s) (CC:68) [10:04:32:829]: Executing op:
> SourceListPublish(NumberOfDisks=1)
> MSI (s) (CC:68) [10:04:32:839]: Note: 1: 1402 2:
> UNKNOWN\Installer\Products\xxx\SourceList 3: 2 MSI (s) (CC:68)
> [10:04:32:859]: Executing op: ProductPublishClient(,,) MSI (s) (CC:68)
> [10:04:32:879]: Executing op:
>
> SourceListRegisterLastUsed(SourceProduct={MyGuid3},LastUsedSource=C:\U
> sers\Clean\Downloads\) MSI (s) (CC:68) [10:04:32:919]: Entering 
> CMsiConfigurationManager::SetLastUsedSource.
> MSI (s) (CC:68) [10:04:32:939]: Setting cached product context: 
> machine assigned for product: xxx MSI (s) (CC:68) [10:04:32:949]: 
> Specifed source is already in a list.
> MSI (s) (CC:68) [10:04:32:979]: User policy value 'SearchOrder' is 'nmu'
> MSI (s) (CC:68) [10:04:32:989]: Adding new sources is allowed.
> MSI (s) (CC:68) [10:04:33:009]: Set LastUsedSource to:
> C:\Users\Clean\Downloads\.
> MSI (s) (CC:68) [10:04:33:029]: Set LastUsedType to: n.
> MSI (s) (CC:68) [10:04:33:039]: Set LastUsedIndex to: 1.
> MSI (s) (CC:68) [10:04:33:059]: Executing op:
> End(Checksum=0,ProgressTotalHDWord=0,ProgressTotalLDWord=4286641)
> MSI (s) (CC:68) [10:04:33:089]: Note: 1: 1935 2: {MyGuid3} 3: 0x80131043 4:
> IAssemblyCacheItem 5: Commit
> 6:
> MyProg,version="1.0.0.0",culture="neutral",publicKeyToken="1BC84BAF13B2B399",processorArchitecture="MSIL"
> MSI (s) (CC:68) [10:04:33:280]: Note: 1: 2205 2: 3: Error MSI (s)
> (CC:68)
> [10:04:33:350]: Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM 
> `Error` WHERE `Error` = 1935 MSI (c) (20:B0) [10:04:34:051]: Font created. 
> Charset:
> Req=0, Ret=0, Font:
> Req=MS Shell Dlg, Ret=MS Shell Dlg
> Error 1935. An error occurred during the installation of assembly 
> 'MyProg,version="1.0.0.0",culture="neutral",publicKeyToken="1BC84BAF13B2B399",processorArchitecture="MSIL"'.
> Please refer to Help and Support for more information. HRESULT: 0x80131043.
> assembly interface: IAssemblyCacheItem, function: Commit, component:
> {MyGuid3}
> MSI (s) (CC:68) [10:04:35:623]: Note: 1: 2205 2: 3: Error MSI (s)
> (CC:68)
> [10:04:35:633]: Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM 
> `Error` WHERE `Error` = 1709 MSI (s) (CC:68) [10:04:35:643]: Product:
> MyProg -- Error 1935. An error occurred during the installation of 
> assembly 
> 'MyProg,version="1.0.0.0",culture="neutral",publicKeyToken="1BC84BAF13B2B399",processorArchitecture="MSIL"'.
> Please refer to Help and Support for more information. HRESULT: 0x80131043.
> assembly interface: IAssemblyCacheItem, function: Commit, component:
> {MyGuid3}
> Action ended 10:04:35: InstallFinalize. Return value 3

Re: [WiX-users] Install Failed, Log Attached

2012-04-26 Thread John Cooper

A TLB files strongly suggests that this is a COM and/or native DLL.  I don't 
think that's a candidate for the GAC either way.

--
John Merryweather Cooper
Build & Install Engineer - ESA
Jack Henry & Associates, Inc.(r)
Shawnee Mission, KS  66227
Office:  913-341-3434 x791011
jocoo...@jackhenry.com
www.jackhenry.com 



-Original Message-
From: Sam Youtsey [mailto:sam.yout...@gmail.com] 
Sent: Thursday, April 26, 2012 2:28 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Install Failed, Log Attached

 Yeah, it's a DLL. There don't seem to be any config files associated, just the 
TLB file. Anything else to look for?

That HRESULT is FUSION_E_UNEXPECTED_MODULE_FOUND.
> http://blogs.msdn.com/b/astebner/archive/2004/11/10/255346.aspx
> Is there a config file associated with the assembly (maybe because 
> it's a policy assembly)?
> Is it actually a Dll?
> Phil W
> -Original Message-
> From: Sam Youtsey [mailto:sam.youtsey@...]
> Sent: Thursday, April 26, 2012 10:35 AM
> To: wix-users@...
> Subject: [WiX-users] Install Failed, Log Attached Hi all, My installer 
> doesn't seem to be installing anything properly. Any chance I could 
> get some help with it?
> Here's the .wxs file:
>   xmlns="http://schemas.microsoft.com/wix/2006/wi";>
>  Name="MyProg"
> Language="1033"
> Version="$(var.ProductVersion)"
> Manufacturer="MyCompany"
> UpgradeCode="MyGuid2">
>  />
>Id="ProductFeature" Title="MyProg" Level="1">  Id="ProductComponents" /> Id="TARGETDIR" Name="SourceDir">  Name="Program Files">  Name="MyCompany">  
>  
> 
>  
>   Source="..\MyProg\bin\Debug\MyProg.dll" KeyPath="yes"
> Assembly=".net">
>  Source="..\MyProg\bin\Debug\MyProg.tlb">
>  Source="..\$(var.JavascriptNET)\Noesis.Javascript.dll" />  Id="MyProg_Demo" Source="..\MyProg_Demo.xlsm">
> 
> 
> 
> 
> And here's around the error that I'm seeing in the log:
> MSI (s) (CC:68) [10:04:32:829]: Executing op:
> UpgradeCodePublish(UpgradeCode={MyGuid3})
> MSI (s) (CC:68) [10:04:32:829]: Executing op:
> SourceListPublish(NumberOfDisks=1)
> MSI (s) (CC:68) [10:04:32:839]: Note: 1: 1402 2:
> UNKNOWN\Installer\Products\xxx\SourceList 3: 2 MSI (s) (CC:68)
> [10:04:32:859]: Executing op: ProductPublishClient(,,) MSI (s) (CC:68)
> [10:04:32:879]: Executing op:
>
> SourceListRegisterLastUsed(SourceProduct={MyGuid3},LastUsedSource=C:\U
> sers\Clean\Downloads\) MSI (s) (CC:68) [10:04:32:919]: Entering 
> CMsiConfigurationManager::SetLastUsedSource.
> MSI (s) (CC:68) [10:04:32:939]: Setting cached product context: 
> machine assigned for product: xxx MSI (s) (CC:68) [10:04:32:949]: 
> Specifed source is already in a list.
> MSI (s) (CC:68) [10:04:32:979]: User policy value 'SearchOrder' is 'nmu'
> MSI (s) (CC:68) [10:04:32:989]: Adding new sources is allowed.
> MSI (s) (CC:68) [10:04:33:009]: Set LastUsedSource to:
> C:\Users\Clean\Downloads\.
> MSI (s) (CC:68) [10:04:33:029]: Set LastUsedType to: n.
> MSI (s) (CC:68) [10:04:33:039]: Set LastUsedIndex to: 1.
> MSI (s) (CC:68) [10:04:33:059]: Executing op:
> End(Checksum=0,ProgressTotalHDWord=0,ProgressTotalLDWord=4286641)
> MSI (s) (CC:68) [10:04:33:089]: Note: 1: 1935 2: {MyGuid3} 3: 0x80131043 4:
> IAssemblyCacheItem 5: Commit
> 6:
> MyProg,version="1.0.0.0",culture="neutral",publicKeyToken="1BC84BAF13B2B399",processorArchitecture="MSIL"
> MSI (s) (CC:68) [10:04:33:280]: Note: 1: 2205 2: 3: Error MSI (s) 
> (CC:68)
> [10:04:33:350]: Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM 
> `Error` WHERE `Error` = 1935 MSI (c) (20:B0) [10:04:34:051]: Font created. 
> Charset:
> Req=0, Ret=0, Font:
> Req=MS Shell Dlg, Ret=MS Shell Dlg
> Error 1935. An error occurred during the installation of assembly 
> 'MyProg,version="1.0.0.0",culture="neutral",publicKeyToken="1BC84BAF13B2B399",processorArchitecture="MSIL"'.
> Please refer to Help and Support for more information. HRESULT: 0x80131043.
> assembly interface: IAssemblyCacheItem, function: Commit, component:
> {MyGuid3}
> MSI (s) (CC:68) [10:04:35:623]: Note: 1: 2205 2: 3: Error MSI (s) 
> (CC:68)
> [10:04:35:633]: Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM 
> `Error` WHERE `Error` = 1709 MSI (s) (CC:68) [10:04:35:643]: Product: 
> MyProg -- Error 1935. An error occurred during the installation of 
> assembly 
> 'MyProg,version="1.0.0.0",culture="neutral",publicKeyToken="1BC84BAF13B2B399",processorArchitecture="MSIL"'.
> Please refer to Help and Support for more information. HRESULT: 0x80131043.
> assembly interface: IAssemblyCacheItem, function: Commit, component:
> {MyGuid3}
> Action ended 10:04:35: InstallFinalize. Return value 3.
>
> --
> 
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and 
> threat landscape has changed and how IT managers can respond. 
> Discussions will include endpoint security, mobile security and the 
> latest in malware threats. 
> http://www.accelacomm.com/jaw/sfrnl042420

Re: [WiX-users] Install Failed, Log Attached

 Yeah, it's a DLL. There don't seem to be any config files associated, just
the TLB file. Anything else to look for?

That HRESULT is FUSION_E_UNEXPECTED_MODULE_FOUND.
> http://blogs.msdn.com/b/astebner/archive/2004/11/10/255346.aspx
> Is there a config file associated with the assembly (maybe because it's a
> policy assembly)?
> Is it actually a Dll?
> Phil W
> -Original Message-
> From: Sam Youtsey [mailto:sam.youtsey@...]
> Sent: Thursday, April 26, 2012 10:35 AM
> To: wix-users@...
> Subject: [WiX-users] Install Failed, Log Attached
> Hi all,
> My installer doesn't seem to be installing anything properly. Any chance I
> could get some help with it?
> Here's the .wxs file:
> 
> http://schemas.microsoft.com/wix/2006/wi";>
>  Name="MyProg"
> Language="1033"
> Version="$(var.ProductVersion)"
> Manufacturer="MyCompany"
> UpgradeCode="MyGuid2">
>  />
>  
>   Id="ProductComponents" />  
> 
>   Id="ProgramFilesFolder" Name="Program Files">  Name="MyCompany"> 
>
> 
> 
> 
>   Source="..\MyProg\bin\Debug\MyProg.dll" KeyPath="yes"
> Assembly=".net">
>  Source="..\MyProg\bin\Debug\MyProg.tlb">
>  Source="..\$(var.JavascriptNET)\Noesis.Javascript.dll" />  Id="MyProg_Demo" Source="..\MyProg_Demo.xlsm">
> 
> 
> 
> 
> And here's around the error that I'm seeing in the log:
> MSI (s) (CC:68) [10:04:32:829]: Executing op:
> UpgradeCodePublish(UpgradeCode={MyGuid3})
> MSI (s) (CC:68) [10:04:32:829]: Executing op:
> SourceListPublish(NumberOfDisks=1)
> MSI (s) (CC:68) [10:04:32:839]: Note: 1: 1402 2:
> UNKNOWN\Installer\Products\xxx\SourceList 3: 2 MSI (s) (CC:68)
> [10:04:32:859]: Executing op: ProductPublishClient(,,) MSI (s) (CC:68)
> [10:04:32:879]: Executing op:
>
> SourceListRegisterLastUsed(SourceProduct={MyGuid3},LastUsedSource=C:\Users\Clean\Downloads\)
> MSI (s) (CC:68) [10:04:32:919]: Entering
> CMsiConfigurationManager::SetLastUsedSource.
> MSI (s) (CC:68) [10:04:32:939]: Setting cached product context: machine
> assigned for product: xxx MSI (s) (CC:68) [10:04:32:949]: Specifed source
> is already in a list.
> MSI (s) (CC:68) [10:04:32:979]: User policy value 'SearchOrder' is 'nmu'
> MSI (s) (CC:68) [10:04:32:989]: Adding new sources is allowed.
> MSI (s) (CC:68) [10:04:33:009]: Set LastUsedSource to:
> C:\Users\Clean\Downloads\.
> MSI (s) (CC:68) [10:04:33:029]: Set LastUsedType to: n.
> MSI (s) (CC:68) [10:04:33:039]: Set LastUsedIndex to: 1.
> MSI (s) (CC:68) [10:04:33:059]: Executing op:
> End(Checksum=0,ProgressTotalHDWord=0,ProgressTotalLDWord=4286641)
> MSI (s) (CC:68) [10:04:33:089]: Note: 1: 1935 2: {MyGuid3} 3: 0x80131043 4:
> IAssemblyCacheItem 5: Commit
> 6:
> MyProg,version="1.0.0.0",culture="neutral",publicKeyToken="1BC84BAF13B2B399",processorArchitecture="MSIL"
> MSI (s) (CC:68) [10:04:33:280]: Note: 1: 2205 2: 3: Error MSI (s) (CC:68)
> [10:04:33:350]: Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM `Error`
> WHERE `Error` = 1935 MSI (c) (20:B0) [10:04:34:051]: Font created. Charset:
> Req=0, Ret=0, Font:
> Req=MS Shell Dlg, Ret=MS Shell Dlg
> Error 1935. An error occurred during the installation of assembly
> 'MyProg,version="1.0.0.0",culture="neutral",publicKeyToken="1BC84BAF13B2B399",processorArchitecture="MSIL"'.
> Please refer to Help and Support for more information. HRESULT: 0x80131043.
> assembly interface: IAssemblyCacheItem, function: Commit, component:
> {MyGuid3}
> MSI (s) (CC:68) [10:04:35:623]: Note: 1: 2205 2: 3: Error MSI (s) (CC:68)
> [10:04:35:633]: Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM `Error`
> WHERE `Error` = 1709 MSI (s) (CC:68) [10:04:35:643]: Product: MyProg --
> Error 1935. An error occurred during the installation of assembly
> 'MyProg,version="1.0.0.0",culture="neutral",publicKeyToken="1BC84BAF13B2B399",processorArchitecture="MSIL"'.
> Please refer to Help and Support for more information. HRESULT: 0x80131043.
> assembly interface: IAssemblyCacheItem, function: Commit, component:
> {MyGuid3}
> Action ended 10:04:35: InstallFinalize. Return value 3.
>
> --
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and threat
> landscape has changed and how IT managers can respond. Discussions will
> include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> ___
> WiX-users mailing list
> WiX-users@...
> https://lists.sourceforge.net/lists/listinfo/wix-users
> *** Confidentiality Notice: This e-mail, including any associated or
> attached files, is intended solely for the individual or entity to which it
> is addressed. This e-mail is confidential and may well also be legally
> privileged. If you have received it in error, you are on notice of its
> status. Please notify the sender immediately by reply e-mail and then
> delete this message from your system. Please do not copy it or use it for
> any pur

[WiX-users] Recommended way to implement installer key (serial number you need to install the msi)

2012-04-26 Thread Helali Bhuiyan

What is the recommended way of writing a msi installer that will ask for a 
serial number before installation? Any pointers, code example is greatly 
appreciated.

Thanks.

-Helali

--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Install Failed, Log Attached

That HRESULT is FUSION_E_UNEXPECTED_MODULE_FOUND. 

http://blogs.msdn.com/b/astebner/archive/2004/11/10/255346.aspx 

Is there a config file associated with the assembly (maybe because it's a 
policy assembly)? 

Is it actually a  Dll? 

Phil W 

-Original Message-
From: Sam Youtsey [mailto:sam.yout...@gmail.com] 
Sent: Thursday, April 26, 2012 10:35 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Install Failed, Log Attached

Hi all,

My installer doesn't seem to be installing anything properly. Any chance I 
could get some help with it?

Here's the .wxs file:


http://schemas.microsoft.com/wix/2006/wi";>



 

   


   
   
 




 
   
 






And here's around the error that I'm seeing in the log:

MSI (s) (CC:68) [10:04:32:829]: Executing op:
UpgradeCodePublish(UpgradeCode={MyGuid3})
MSI (s) (CC:68) [10:04:32:829]: Executing op:
SourceListPublish(NumberOfDisks=1)
MSI (s) (CC:68) [10:04:32:839]: Note: 1: 1402 2:
UNKNOWN\Installer\Products\xxx\SourceList 3: 2 MSI (s) (CC:68) [10:04:32:859]: 
Executing op: ProductPublishClient(,,) MSI (s) (CC:68) [10:04:32:879]: 
Executing op:
SourceListRegisterLastUsed(SourceProduct={MyGuid3},LastUsedSource=C:\Users\Clean\Downloads\)
MSI (s) (CC:68) [10:04:32:919]: Entering 
CMsiConfigurationManager::SetLastUsedSource.
MSI (s) (CC:68) [10:04:32:939]: Setting cached product context: machine 
assigned for product: xxx MSI (s) (CC:68) [10:04:32:949]: Specifed source is 
already in a list.
MSI (s) (CC:68) [10:04:32:979]: User policy value 'SearchOrder' is 'nmu'
MSI (s) (CC:68) [10:04:32:989]: Adding new sources is allowed.
MSI (s) (CC:68) [10:04:33:009]: Set LastUsedSource to:
C:\Users\Clean\Downloads\.
MSI (s) (CC:68) [10:04:33:029]: Set LastUsedType to: n.
MSI (s) (CC:68) [10:04:33:039]: Set LastUsedIndex to: 1.
MSI (s) (CC:68) [10:04:33:059]: Executing op:
End(Checksum=0,ProgressTotalHDWord=0,ProgressTotalLDWord=4286641)
MSI (s) (CC:68) [10:04:33:089]: Note: 1: 1935 2: {MyGuid3} 3: 0x80131043 4:
IAssemblyCacheItem 5: Commit
6: 
MyProg,version="1.0.0.0",culture="neutral",publicKeyToken="1BC84BAF13B2B399",processorArchitecture="MSIL"
MSI (s) (CC:68) [10:04:33:280]: Note: 1: 2205 2:  3: Error MSI (s) (CC:68) 
[10:04:33:350]: Note: 1: 2228 2:  3: Error 4: SELECT `Message` FROM `Error` 
WHERE `Error` = 1935 MSI (c) (20:B0) [10:04:34:051]: Font created.  Charset: 
Req=0, Ret=0, Font:
Req=MS Shell Dlg, Ret=MS Shell Dlg

Error 1935. An error occurred during the installation of assembly 
'MyProg,version="1.0.0.0",culture="neutral",publicKeyToken="1BC84BAF13B2B399",processorArchitecture="MSIL"'.
Please refer to Help and Support for more information. HRESULT: 0x80131043.
assembly interface: IAssemblyCacheItem, function: Commit, component:
{MyGuid3}
MSI (s) (CC:68) [10:04:35:623]: Note: 1: 2205 2:  3: Error MSI (s) (CC:68) 
[10:04:35:633]: Note: 1: 2228 2:  3: Error 4: SELECT `Message` FROM `Error` 
WHERE `Error` = 1709 MSI (s) (CC:68) [10:04:35:643]: Product: MyProg -- Error 
1935. An error occurred during the installation of assembly 
'MyProg,version="1.0.0.0",culture="neutral",publicKeyToken="1BC84BAF13B2B399",processorArchitecture="MSIL"'.
Please refer to Help and Support for more information. HRESULT: 0x80131043.
assembly interface: IAssemblyCacheItem, function: Commit, component:
{MyGuid3}

Action ended 10:04:35: InstallFinalize. Return value 3.
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and threat 
landscape has changed and how IT managers can respond. Discussions will include 
endpoint security, mobile security and the latest in malware threats. 
http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


*** Confidentiality Notice: This e-mail, including any associated or attached 
files, is intended solely for the individual or entity to which it is 
addressed. This e-mail is confidential and may well also be legally privileged. 
If you have received it in error, you are on notice of its status. Please 
notify the sender immediately by reply e-mail and then delete this message from 
your system. Please do not copy it or use it for any purposes, or disclose its 
contents to any other person. This email comes from a division of the Invensys 
Group, owned by Invensys plc, which is a company registered in England and 
Wales with its registered office at 3rd Floor, 40 Grosvenor Place, London, SW1X 
7AW (Registered number 166023). For a list of European legal entities within 
the Invensys Group, please go to http://www.invensys.com/en/legal/default.aspx.

You may contact Invensys plc on +44 (0)20 3155 1200 or e-mail 
recept...@invensys.com. This e-mail and any attachments thereto may be subject 
to the terms of any agreements between Inv

[WiX-users] Install Failed, Log Attached

Hi all,

My installer doesn't seem to be installing anything properly. Any chance I
could get some help with it?

Here's the .wxs file:


http://schemas.microsoft.com/wix/2006/wi";>
























 
 
 
 
 
 






And here's around the error that I'm seeing in the log:

MSI (s) (CC:68) [10:04:32:829]: Executing op:
UpgradeCodePublish(UpgradeCode={MyGuid3})
MSI (s) (CC:68) [10:04:32:829]: Executing op:
SourceListPublish(NumberOfDisks=1)
MSI (s) (CC:68) [10:04:32:839]: Note: 1: 1402 2:
UNKNOWN\Installer\Products\xxx\SourceList 3: 2
MSI (s) (CC:68) [10:04:32:859]: Executing op: ProductPublishClient(,,)
MSI (s) (CC:68) [10:04:32:879]: Executing op:
SourceListRegisterLastUsed(SourceProduct={MyGuid3},LastUsedSource=C:\Users\Clean\Downloads\)
MSI (s) (CC:68) [10:04:32:919]: Entering
CMsiConfigurationManager::SetLastUsedSource.
MSI (s) (CC:68) [10:04:32:939]: Setting cached product context: machine
assigned for product: xxx
MSI (s) (CC:68) [10:04:32:949]: Specifed source is already in a list.
MSI (s) (CC:68) [10:04:32:979]: User policy value 'SearchOrder' is 'nmu'
MSI (s) (CC:68) [10:04:32:989]: Adding new sources is allowed.
MSI (s) (CC:68) [10:04:33:009]: Set LastUsedSource to:
C:\Users\Clean\Downloads\.
MSI (s) (CC:68) [10:04:33:029]: Set LastUsedType to: n.
MSI (s) (CC:68) [10:04:33:039]: Set LastUsedIndex to: 1.
MSI (s) (CC:68) [10:04:33:059]: Executing op:
End(Checksum=0,ProgressTotalHDWord=0,ProgressTotalLDWord=4286641)
MSI (s) (CC:68) [10:04:33:089]: Note: 1: 1935 2: {MyGuid3} 3: 0x80131043 4:
IAssemblyCacheItem 5: Commit
6: 
MyProg,version="1.0.0.0",culture="neutral",publicKeyToken="1BC84BAF13B2B399",processorArchitecture="MSIL"
MSI (s) (CC:68) [10:04:33:280]: Note: 1: 2205 2:  3: Error
MSI (s) (CC:68) [10:04:33:350]: Note: 1: 2228 2:  3: Error 4: SELECT
`Message` FROM `Error` WHERE `Error` = 1935
MSI (c) (20:B0) [10:04:34:051]: Font created.  Charset: Req=0, Ret=0, Font:
Req=MS Shell Dlg, Ret=MS Shell Dlg

Error 1935. An error occurred during the installation of assembly
'MyProg,version="1.0.0.0",culture="neutral",publicKeyToken="1BC84BAF13B2B399",processorArchitecture="MSIL"'.
Please refer to Help and Support for more information. HRESULT: 0x80131043.
assembly interface: IAssemblyCacheItem, function: Commit, component:
{MyGuid3}
MSI (s) (CC:68) [10:04:35:623]: Note: 1: 2205 2:  3: Error
MSI (s) (CC:68) [10:04:35:633]: Note: 1: 2228 2:  3: Error 4: SELECT
`Message` FROM `Error` WHERE `Error` = 1709
MSI (s) (CC:68) [10:04:35:643]: Product: MyProg -- Error 1935. An error
occurred during the installation of assembly
'MyProg,version="1.0.0.0",culture="neutral",publicKeyToken="1BC84BAF13B2B399",processorArchitecture="MSIL"'.
Please refer to Help and Support for more information. HRESULT: 0x80131043.
assembly interface: IAssemblyCacheItem, function: Commit, component:
{MyGuid3}

Action ended 10:04:35: InstallFinalize. Return value 3.
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] WiX3.6 Uninstall Failed / Installing Votive

2012-04-26 Thread Dmuller720

The log is in the OP

--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/WiX3-6-Uninstall-Failed-Installing-Votive-tp7500775p7503666.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] MsiRMFilesInUse example to restart browsers

Are you maybe misunderstanding the FilesInUse dialogs? Windows decides to show 
this or nor based on what files need replacing, whether they are in use, their 
versions etc.  CloseApplication is not the same thing at all - it's a WiX 
feature that closes applications. 

Phil W 

-Original Message-
From: E. Timothy Uy [mailto:t...@loqu8.com] 
Sent: Thursday, April 26, 2012 9:22 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] MsiRMFilesInUse example to restart browsers

With chrome in the mix, nothing at all (not even IE or Firefox) gets terminated.

Action 9:04:37: WixRegisterRestartResources.
Action start 9:04:37: WixRegisterRestartResources.
WixRegisterRestartResources:  Entering WixRegisterRestartResources in 
C:\Windows\Installer\MSI7074.tmp, version 3.6.2809.0
WixRegisterRestartResources:  Registering process name iexplore.exe with the 
Restart Manager.
WixRegisterRestartResources:  Registering process name firefox.exe with the 
Restart Manager.
WixRegisterRestartResources:  Registering process name chrome.exe with the 
Restart Manager.
Action ended 9:04:38: WixRegisterRestartResources. Return value 1.
Action 9:04:38: InstallValidate. Validating install Action start 9:04:38: 
InstallValidate.
Action 9:04:43: ShutdownApplications. Shutting down applications The setup was 
unable to automatically close all requested applications.
Please ensure that the applications holding files in use are closed before 
continuing with the installation.
Action ended 9:04:54: InstallValidate. Return value 1.

On Wed, Apr 25, 2012 at 3:59 PM, E. Timothy Uy  wrote:

> chrome.exe  - does not close
> firefox.exe - closes, but never restarts iexplore.exe - closes and 
> restarts (blank page)
>
>
> On Wed, Apr 25, 2012 at 2:50 PM, E. Timothy Uy  wrote:
>
>> The plot thickens. Removing Chrome from the mix makes it work.
>>
>>  
>> > />
>>
>> Is this solvable? I did notice that chrome.exe uses a lot of processes.
>> Could this be the issue? Is there a limit on the # of processes?
>>
>> On Wed, Apr 25, 2012 at 2:14 PM, E. Timothy Uy  wrote:
>>
>>> I was able to show the FilesInUse (for iexplore, chrome and firefox) 
>>> but just adding
>>>
>>> 
>>> 
>>> >> />
>>>
>>> However, clicking on attempt to close prompted me with
>>>
>>> The setup was unable to automatically close all requested applications.
>>> Please ensure that the applications holding files in use are closed 
>>> before continuing with the installation.
>>>
>>> None of the browser instances are closed.
>>>
>>> Any advice would be much appreciated.
>>>
>>> Respectfully,
>>> Tim
>>>
>>> On Wed, Apr 25, 2012 at 1:56 PM, E. Timothy Uy  wrote:
>>>
 Looks like RM only works with Vista+. What is the fallback for XP?

 On Wed, Apr 25, 2012 at 1:53 PM, E. Timothy Uy  wrote:

> Dear Rob et al.,
>
> Thanks everyone for being so gracious. This time I would like the 
> installer to shutdown any browsers (IE, Chrome, Firefox) prior to 
> installation, and restart them after installation completes. I 
> think I should use MsiRMFilesInUse but have not been able to 
> locate any samples or instructions. Is this used with 
> util:CloseApplication?
>
> I gather that I need  in UI. Can 
> I use WixUI_InstallDir or should I be using Mondo? A completed 
> example would be ideal. The How To Guides are fantastic.
>
> Respectfully,
> Tim
>

>>>
>>
>
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and threat 
landscape has changed and how IT managers can respond. Discussions will include 
endpoint security, mobile security and the latest in malware threats. 
http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

*** Confidentiality Notice: This e-mail, including any associated or attached 
files, is intended solely for the individual or entity to which it is 
addressed. This e-mail is confidential and may well also be legally privileged. 
If you have received it in error, you are on notice of its status. Please 
notify the sender immediately by reply e-mail and then delete this message from 
your system. Please do not copy it or use it for any purposes, or disclose its 
contents to any other person. This email comes from a division of the Invensys 
Group, owned by Invensys plc, which is a company registered in England and 
Wales with its registered office at 3rd Floor, 40 Grosvenor Place, London, SW1X 
7AW (Registered number 166023). For a list of European legal entities within 
the Invensys Group, please go to http://www.invensys.com/en/legal/default.aspx.

You may contact Invensys plc on +44 (0)20 3155 1200 or e-mail 
recept...@invensys.com. This e-mail and

Re: [WiX-users] MsiRMFilesInUse example to restart browsers

With chrome in the mix, nothing at all (not even IE or Firefox) gets
terminated.

Action 9:04:37: WixRegisterRestartResources.
Action start 9:04:37: WixRegisterRestartResources.
WixRegisterRestartResources:  Entering WixRegisterRestartResources in
C:\Windows\Installer\MSI7074.tmp, version 3.6.2809.0
WixRegisterRestartResources:  Registering process name iexplore.exe with
the Restart Manager.
WixRegisterRestartResources:  Registering process name firefox.exe with the
Restart Manager.
WixRegisterRestartResources:  Registering process name chrome.exe with the
Restart Manager.
Action ended 9:04:38: WixRegisterRestartResources. Return value 1.
Action 9:04:38: InstallValidate. Validating install
Action start 9:04:38: InstallValidate.
Action 9:04:43: ShutdownApplications. Shutting down applications
The setup was unable to automatically close all requested applications.
Please ensure that the applications holding files in use are closed before
continuing with the installation.
Action ended 9:04:54: InstallValidate. Return value 1.

On Wed, Apr 25, 2012 at 3:59 PM, E. Timothy Uy  wrote:

> chrome.exe  - does not close
> firefox.exe - closes, but never restarts
> iexplore.exe - closes and restarts (blank page)
>
>
> On Wed, Apr 25, 2012 at 2:50 PM, E. Timothy Uy  wrote:
>
>> The plot thickens. Removing Chrome from the mix makes it work.
>>
>> 
>> 
>>
>> Is this solvable? I did notice that chrome.exe uses a lot of processes.
>> Could this be the issue? Is there a limit on the # of processes?
>>
>> On Wed, Apr 25, 2012 at 2:14 PM, E. Timothy Uy  wrote:
>>
>>> I was able to show the FilesInUse (for iexplore, chrome and firefox) but
>>> just adding
>>>
>>> 
>>> 
>>> >> />
>>>
>>> However, clicking on attempt to close prompted me with
>>>
>>> The setup was unable to automatically close all requested applications.
>>> Please ensure that the applications holding files in use are closed before
>>> continuing with the installation.
>>>
>>> None of the browser instances are closed.
>>>
>>> Any advice would be much appreciated.
>>>
>>> Respectfully,
>>> Tim
>>>
>>> On Wed, Apr 25, 2012 at 1:56 PM, E. Timothy Uy  wrote:
>>>
 Looks like RM only works with Vista+. What is the fallback for XP?

 On Wed, Apr 25, 2012 at 1:53 PM, E. Timothy Uy  wrote:

> Dear Rob et al.,
>
> Thanks everyone for being so gracious. This time I would like the
> installer to shutdown any browsers (IE, Chrome, Firefox) prior to
> installation, and restart them after installation completes. I think I
> should use MsiRMFilesInUse but have not been able to locate any samples or
> instructions. Is this used with util:CloseApplication?
>
> I gather that I need  in UI. Can I
> use WixUI_InstallDir or should I be using Mondo? A completed example would
> be ideal. The How To Guides are fantastic.
>
> Respectfully,
> Tim
>

>>>
>>
>
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] WiX 3.5: error PYRO0306

2012-04-26 Thread Zlatko Lovcevic

I'm trying to build a patch using purely WiX method and I'm getting the 
following error:

pyro.exe
 : error PYRO0306 : An error (E_FAIL) was returned while finalizing a 
CAB file. This most commonly happens when creating a CAB file with more 
than 65535 files in it. Either reduce the number of files in your 
installation package or split your installation package's files into 
more than one CAB file using the Media element.

Total number of 
files in my installation is around 1600 and about 600 of them are 
selected for patching. Does anyone know what might be the problem and 
how to solve it? Can patch package be divided into multiple cabs?
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Burn - MSIPackage InstallCondition evaluates to false, attempts minor upgrade

2012-04-26 Thread Pally Sandher

Not too bothered about 3 so I'll ignore it for now. Just mentioned it as one 
our QA guys noticed it today.

Regarding 4, I do have the same product code & higher version however my 
Upgrade Table code looks like the following:


  
  
  


Burn is trying to be too clever for its own good & changing the expected 
behaviour. I create a patch to upgrade from 2.0 or 2.1 to 2.2 as it's less than 
half the size of the full installer & I don't want to make users download 
something they don't need.
Forcing someone to use a Minor Upgrade when they actually want either Major 
Upgrade or disallow installation seems rather counter-intuitive.

I'll raise bugs in the SourceForge tracker for the other issues.

Palbinder Sandher 
Software Platform Engineer 
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com 

**Design, Simulate + Innovate with the ** 
Integrated Environmental Solutions Limited. Registered in Scotland No. SC151456
Registered Office - Helix Building, West Of Scotland Science Park, Glasgow G20 
0SP
Email Disclaimer 



-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com] 
Sent: 26 April 2012 15:41
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Burn - MSIPackage InstallCondition evaluates to false, 
attempts minor upgrade

1. Agree about the InstallCondition doc. Want to file a bug?
2. DisplayInternalUI on MSP might be broken. Want to file a bug?
3. Burn calculates size of installed packages + their cache size if they
are cached. I'd need more details about the size being wrong to be more
helpful.
4. The log file should explain when an MSI is being minor upgraded.
Basically, if you have same product code but higher version, minor upgrade
kicks in.

On Thu, Apr 26, 2012 at 3:11 AM, Pally Sandher wrote:

> I've removed the InstallCondition for the patch & it's now working as
> intended. Thanks for the input on this however I would point out the
> documentation mentions nothing about "patch applicability" & the
> InstallCondition description says "A condition to evaluate before
> installing the package. The package will only be installed if the condition
> evaluates to true." which it's not unreasonable to assume the converse
> (i.e. if InstallCondition evaluates to false, the package is not installed)
> -> http://wix.sourceforge.net/manual-wix3/wix_xsd_msppackage.htm
>
> Anyone have any input on the previous questions I posted in this thread?
> Why is DisplayInternalUI="yes" being ignored for MspPackage. Also
> InstallSize seems to be ignored in MspPackage & ExePackage (tried setting
> it to 0 and 1, same results with burn size entry in ARP showing the total
> of all packages in the chain which is vastly inflated).
>
> My original question is still unanswered. Even without an InstallCondition
> attribute for the MsiPackage it will still attempt a minor upgrade which is
> contrary to the behaviour it exhibits when the MSI is manually run.
>
> Palbinder Sandher
> Software Platform Engineer
> T:+44 (0) 141 945 8500
> F:+44 (0) 141 945 8501
> http://www.iesve.com
>
> **Design, Simulate + Innovate with the **
> Integrated Environmental Solutions Limited. Registered in Scotland No.
> SC151456
> Registered Office - Helix Building, West Of Scotland Science Park, Glasgow
> G20 0SP
> Email Disclaimer
>
>
> -Original Message-
> From: Rob Mensching [mailto:r...@robmensching.com]
> Sent: 26 April 2012 06:51
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Burn - MSIPackage InstallCondition evaluates to
> false, attempts minor upgrade
>
> Sounds like we should scan patches for those that disallow removal and mark
> them permanent.
>
> The InstallCondition behavior is expected. If the InstallCondition is false
> that means "this Package should not be Installed" (aka: should not exist on
> the box).
>
> On Wed, Apr 25, 2012 at 9:30 AM, Bob Arnson  wrote:
>
> > On 25-Apr-12 10:06, Pally Sandher wrote:
> > > Why is it attempting to uninstall the patch when the condition is
> false&
> >  the patch has AllowRemoval="no"?
> > Because Burn always attempts to uninstall a package that's present when
> > its install condition is false, and Burn doesn't know the patch is
> > permanent. You can file a feature request to change either of those
> > facts or consider using patch applicability instead of install
> > conditions to control the patch installation.
> >
> > --
> > sig://boB
> > http://joyofsetup.com/
> >
> >
> >
> >
> --
> > Live Security Virtual Conference
> > Exclusive live event will cover all the ways today's security and
> > threat landscape has changed and how IT managers can respond. Discussions
> > will include endpoint security, mobile security and the latest in malware
> > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> > ___
> > WiX-use

[WiX-users] Burn - Uninstall from programs & features causes reinstall of WiX built MSI package

2012-04-26 Thread Pally Sandher

  

[06A0:0B6C][2012-04-26T14:56:20]: Burn v3.6.2816.0, Windows v6.1 (Build 7601: 
Service Pack 1), path: C:\ProgramData\Package 
Cache\{c4017423-730a-47fe-b473-eec0fa8071db}\ve2012setup.exe, cmdline: 
'/uninstall -burn.unelevated BurnPipe.{07CEB968-F392-4BE0-A3CF-F00525E5A2C7} 
{50F4EFE9-76A5-45EF-B018-BF523A1D39A7} 1796'
[06A0:0B6C][2012-04-26T14:56:20]: Setting string variable 'WixBundleLog' to 
value 
'C:\Users\zxc\AppData\Local\Temp\IES_Virtual_Environment_2012_20120426145620.log'
[06A0:0B6C][2012-04-26T14:56:21]: Detect 3 packages
[06A0:0B6C][2012-04-26T14:56:21]: Setting string variable 'NET4Installed' to 
value '1'
[06A0:0B6C][2012-04-26T14:56:21]: Calculating patch applicability for target 
product code: {92E2C426-6CDB-44D4-8D48-6414A442231D}, context: Machine
[06A0:0B6C][2012-04-26T14:56:21]: Condition 'NET4Installed = 1' evaluates to 
true.
[06A0:0B6C][2012-04-26T14:56:21]: Detected package: NET4.0, state: Present, 
cached: Complete
[06A0:0B6C][2012-04-26T14:56:21]: Detected package: SharedContentPatch, state: 
Present, cached: Complete
[06A0:0B6C][2012-04-26T14:56:21]: Detected package: SharedContentPatch target: 
{92E2C426-6CDB-44D4-8D48-6414A442231D}, state: Present
[06A0:0B6C][2012-04-26T14:56:21]: Detected package: ve, state: Present, cached: 
Complete
[06A0:0B6C][2012-04-26T14:56:21]: Detect complete, result: 0x0
[06A0:0B6C][2012-04-26T14:56:22]: Plan 3 packages, action: Uninstall
[06A0:0B6C][2012-04-26T14:56:22]: Setting string variable 
'WixBundleRollbackLog_ve' to value 
'C:\Users\zxc\AppData\Local\Temp\IES_Virtual_Environment_2012_20120426145620_0_ve_rollback.log'
[06A0:0B6C][2012-04-26T14:56:22]: Setting string variable 'WixBundleLog_ve' to 
value 
'C:\Users\zxc\AppData\Local\Temp\IES_Virtual_Environment_2012_20120426145620_0_ve.log'
[06A0:0B6C][2012-04-26T14:56:22]: Skipping dependency registration on package 
with no dependency providers: SharedContentPatch
[06A0:0B6C][2012-04-26T14:56:22]: Skipping dependency registration on package 
with no dependency providers: NET4.0
[06A0:0B6C][2012-04-26T14:56:22]: Planned package: ve, state: Present, default 
requested: Absent, ba requested: Absent, execute: Uninstall, rollback: Install, 
cache: No, uncache: Yes, dependency: Unregister
[06A0:0B6C][2012-04-26T14:56:22]: Planned package: SharedContentPatch, state: 
Present, default requested: None, ba requested: None, execute: None, rollback: 
None, cache: No, uncache: No, dependency: None
[06A0:0B6C][2012-04-26T14:56:22]: Planned package: NET4.0, state: Present, 
default requested: None, ba requested: None, execute: None, rollback: None, 
cache: No, uncache: No, dependency: None
[06A0:0B6C][2012-04-26T14:56:22]: Plan complete, result: 0x0
[06A0:0B6C][2012-04-26T14:56:22]: Apply begin
[0704:05D4][2012-04-26T14:56:22]: Creating a system restore point.
[0704:05D4][2012-04-26T14:56:36]: Created a system restore point.
[0704:0B64][2012-04-26T14:56:39]: Verified existing payload: ve at path: 
C:\ProgramData\Package 
Cache\{4C98F99A-3A95-4291-915E-D869C8FD4814}v12.1.0.0\ve2012.msi.
[0704:05D4][2012-04-26T14:56:39]: Removed dependency: 
{c4017423-730a-47fe-b473-eec0fa8071db} on package provider: 
{4C98F99A-3A95-4291-915E-D869C8FD4814}, package ve
[0704:05D4][2012-04-26T14:56:39]: Applying execute package: ve, action: 
Uninstall, path: C:\ProgramData\Package 
Cache\{4C98F99A-3A95-4291-915E-D869C8FD4814}v12.1.0.0\ve2012.msi, arguments: ' 
ALLUSERS="1" ARPSYSTEMCOMPONENT="1" MSIFASTINSTALL="7"'
[0704:05D4][2012-04-26T14:56:55]: Error 0x80070642: Failed to uninstall MSI 
package.
[0704:05D4][2012-04-26T14:56:55]: Error 0x80070642: Failed to execute MSI 
package.
[06A0:0B6C][2012-04-26T14:56:55]: Error 0x80070642: Failed to configure 
per-machine MSI package.
[06A0:0B6C][2012-04-26T14:56:55]: Applied execute package: ve, result: 
0x80070642, restart: None
[06A0:0B6C][2012-04-26T14:56:55]: Error 0x80070642: Failed to execute MSI 
package.
[0704:05D4][2012-04-26T14:56:55]: Skipped rollback of package: ve, action: 
Install, already: Present
[06A0:0B6C][2012-04-26T14:56:55]: Applied rollback package: ve, result: 0x0, 
restart: None
[0704:05D4][2012-04-26T14:56:55]: Registering dependency: 
{c4017423-730a-47fe-b473-eec0fa8071db} on package provider: 
{4C98F99A-3A95-4291-915E-D869C8FD4814}, package: ve
[06A0:0B6C][2012-04-26T14:56:55]: Apply complete, result: 0x80070642, restart: 
None, ba requested restart:  No


The MSI uninstalls perfectly fine if I run it after extraction using /layout. 
Why am I getting a Reinstall when run from Burn?

Really at my wits end with Burn.

Palbinder Sandher 
Software Platform Engineer 
T:+44 (0) 141 945 8500
F:+44 (0) 141 945 8501
http://www.iesve.com 

**Design, Simulate + Innovate with the ** 
Integrated Environmental Solutions Limited. Registered in Scotland No. SC151456
Registered Office - Helix Building, West Of Scotland Science Park, Glasgow G20 
0SP
Email Disclaimer 




--
Live Security Virt

Re: [WiX-users] Burn - MSIPackage InstallCondition evaluates to false, attempts minor upgrade

1. Agree about the InstallCondition doc. Want to file a bug?
2. DisplayInternalUI on MSP might be broken. Want to file a bug?
3. Burn calculates size of installed packages + their cache size if they
are cached. I'd need more details about the size being wrong to be more
helpful.
4. The log file should explain when an MSI is being minor upgraded.
Basically, if you have same product code but higher version, minor upgrade
kicks in.

On Thu, Apr 26, 2012 at 3:11 AM, Pally Sandher wrote:

> I've removed the InstallCondition for the patch & it's now working as
> intended. Thanks for the input on this however I would point out the
> documentation mentions nothing about "patch applicability" & the
> InstallCondition description says "A condition to evaluate before
> installing the package. The package will only be installed if the condition
> evaluates to true." which it's not unreasonable to assume the converse
> (i.e. if InstallCondition evaluates to false, the package is not installed)
> -> http://wix.sourceforge.net/manual-wix3/wix_xsd_msppackage.htm
>
> Anyone have any input on the previous questions I posted in this thread?
> Why is DisplayInternalUI="yes" being ignored for MspPackage. Also
> InstallSize seems to be ignored in MspPackage & ExePackage (tried setting
> it to 0 and 1, same results with burn size entry in ARP showing the total
> of all packages in the chain which is vastly inflated).
>
> My original question is still unanswered. Even without an InstallCondition
> attribute for the MsiPackage it will still attempt a minor upgrade which is
> contrary to the behaviour it exhibits when the MSI is manually run.
>
> Palbinder Sandher
> Software Platform Engineer
> T:+44 (0) 141 945 8500
> F:+44 (0) 141 945 8501
> http://www.iesve.com
>
> **Design, Simulate + Innovate with the **
> Integrated Environmental Solutions Limited. Registered in Scotland No.
> SC151456
> Registered Office - Helix Building, West Of Scotland Science Park, Glasgow
> G20 0SP
> Email Disclaimer
>
>
> -Original Message-
> From: Rob Mensching [mailto:r...@robmensching.com]
> Sent: 26 April 2012 06:51
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Burn - MSIPackage InstallCondition evaluates to
> false, attempts minor upgrade
>
> Sounds like we should scan patches for those that disallow removal and mark
> them permanent.
>
> The InstallCondition behavior is expected. If the InstallCondition is false
> that means "this Package should not be Installed" (aka: should not exist on
> the box).
>
> On Wed, Apr 25, 2012 at 9:30 AM, Bob Arnson  wrote:
>
> > On 25-Apr-12 10:06, Pally Sandher wrote:
> > > Why is it attempting to uninstall the patch when the condition is
> false&
> >  the patch has AllowRemoval="no"?
> > Because Burn always attempts to uninstall a package that's present when
> > its install condition is false, and Burn doesn't know the patch is
> > permanent. You can file a feature request to change either of those
> > facts or consider using patch applicability instead of install
> > conditions to control the patch installation.
> >
> > --
> > sig://boB
> > http://joyofsetup.com/
> >
> >
> >
> >
> --
> > Live Security Virtual Conference
> > Exclusive live event will cover all the ways today's security and
> > threat landscape has changed and how IT managers can respond. Discussions
> > will include endpoint security, mobile security and the latest in malware
> > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> > ___
> > WiX-users mailing list
> > WiX-users@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/wix-users
> >
>
>
>
> --
> virtually, Rob Mensching - http://RobMensching.com LLC
>
> --
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
>
>
>
> --
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>



-

Re: [WiX-users] Wix 3.6 Bootstrapper Issues

Please provide the log file.

On Wed, Apr 25, 2012 at 11:00 PM, Anirban Paul wrote:

> As you said, I downloaded the WiX v3.6 RC0 (Released: Apr 3 2012) and tried
> to uninstall the already installed version ( Wix Toolset V3.6.2221.0 ) of
> Wix. But that version is not getting uninstalled!!!
> Currently Wix Toolset V3.6.2221.0 is installed in my computer. But I failed
> to uninstall the version. Whenever I go to Add Remove Program  and click on
> the Remove button of
> Wix Toolset V3.6.2221.0, It says "Failed to unistall"
> Please help.
>
> On Thu, Apr 26, 2012 at 11:04 AM, Anirban Paul  >wrote:
>
> > Ok I shall try that and get back to you.
> > But let me know the wix variable names that are used to set bootstrapper
> > dialog title and bootstrapper dialog icon.
> >
> >
> > On Thu, Apr 26, 2012 at 10:53 AM, Rob Mensching  >wrote:
> >
> >> Sounds like you are using an old version. Upgrade to latest build for
> all
> >> that to work.
> >>
> >> On Wed, Apr 25, 2012 at 9:15 PM, Anirban Paul <
> ani.banti.24...@gmail.com
> >> >wrote:
> >>
> >> > Hi,
> >> > I have created a bootstrapper (using burn in visual studio 2010) which
> >> > installs .Net framework4 as prerequisite and then installs the actual
> >> > msi. Following are the problem that I am facing and I really need your
> >> help
> >> > to resolve those problems.
> >> >
> >> > 1> I don't want the bootstrapper to have an entry in Add Remove
> >> Program;so
> >> > I am not using "Name" attribute in "Bundle" tag. But as a result of
> >> that,
> >> > my bootstrapper dialog displays only the text "Setup". Please let me
> >> know
> >> > is there any way to set the title text without specifying "Name"
> >> attribute
> >> > in "Bundle" tag.
> >> >
> >> > 2> I am unable to set the icon of bootstrapper dialog. How to do this?
> >> >
> >> > 3> The bootstrapper exe is working fine but whenever I try to cancel
> the
> >> > installation in midway the bootstrapper crashes. Is that a bug in Win
> >> 3.6
> >> > or I am doing something wrong?
> >> >
> >> > Please help me to resolve these problems.
> >> >
> >> >  Thanks in advance.
> >> >
> >> >
> >>
> --
> >> > Live Security Virtual Conference
> >> > Exclusive live event will cover all the ways today's security and
> >> > threat landscape has changed and how IT managers can respond.
> >> Discussions
> >> > will include endpoint security, mobile security and the latest in
> >> malware
> >> > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> >> > ___
> >> > WiX-users mailing list
> >> > WiX-users@lists.sourceforge.net
> >> > https://lists.sourceforge.net/lists/listinfo/wix-users
> >> >
> >>
> >>
> >>
> >> --
> >> virtually, Rob Mensching - http://RobMensching.com LLC
> >>
> >>
> --
> >> Live Security Virtual Conference
> >> Exclusive live event will cover all the ways today's security and
> >> threat landscape has changed and how IT managers can respond.
> Discussions
> >> will include endpoint security, mobile security and the latest in
> malware
> >> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> >> ___
> >> WiX-users mailing list
> >> WiX-users@lists.sourceforge.net
> >> https://lists.sourceforge.net/lists/listinfo/wix-users
> >>
> >
> >
>
> --
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>



-- 
virtually, Rob Mensching - http://RobMensching.com LLC
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] WiX3.6 Uninstall Failed / Installing Votive

Can you provide the log?

On Thu, Apr 26, 2012 at 4:59 AM, Dmuller720  wrote:

> I am sorry to Bump, but can anyone help me?
>
> --
> View this message in context:
> http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/WiX3-6-Uninstall-Failed-Installing-Votive-tp7500775p7502620.html
> Sent from the wix-users mailing list archive at Nabble.com.
>
>
> --
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>



-- 
virtually, Rob Mensching - http://RobMensching.com LLC
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] WiX3.6 Uninstall Failed / Installing Votive

2012-04-26 Thread Dmuller720

I am sorry to Bump, but can anyone help me?

--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/WiX3-6-Uninstall-Failed-Installing-Votive-tp7500775p7502620.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Burn - MSIPackage InstallCondition evaluates to false, attempts minor upgrade

2012-04-26 Thread Pally Sandher

I've removed the InstallCondition for the patch & it's now working as intended. 
Thanks for the input on this however I would point out the documentation 
mentions nothing about "patch applicability" & the InstallCondition description 
says "A condition to evaluate before installing the package. The package will 
only be installed if the condition evaluates to true." which it's not 
unreasonable to assume the converse (i.e. if InstallCondition evaluates to 
false, the package is not installed) -> 
http://wix.sourceforge.net/manual-wix3/wix_xsd_msppackage.htm

Anyone have any input on the previous questions I posted in this thread? Why is 
DisplayInternalUI="yes" being ignored for MspPackage. Also InstallSize seems to 
be ignored in MspPackage & ExePackage (tried setting it to 0 and 1, same 
results with burn size entry in ARP showing the total of all packages in the 
chain which is vastly inflated).

My original question is still unanswered. Even without an InstallCondition 
attribute for the MsiPackage it will still attempt a minor upgrade which is 
contrary to the behaviour it exhibits when the MSI is manually run.

Palbinder Sandher 
Software Platform Engineer 
T:+44 (0) 141 945 8500
F:+44 (0) 141 945 8501
http://www.iesve.com 

**Design, Simulate + Innovate with the ** 
Integrated Environmental Solutions Limited. Registered in Scotland No. SC151456
Registered Office - Helix Building, West Of Scotland Science Park, Glasgow G20 
0SP
Email Disclaimer 

-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com] 
Sent: 26 April 2012 06:51
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Burn - MSIPackage InstallCondition evaluates to false, 
attempts minor upgrade

Sounds like we should scan patches for those that disallow removal and mark
them permanent.

The InstallCondition behavior is expected. If the InstallCondition is false
that means "this Package should not be Installed" (aka: should not exist on
the box).

On Wed, Apr 25, 2012 at 9:30 AM, Bob Arnson  wrote:

> On 25-Apr-12 10:06, Pally Sandher wrote:
> > Why is it attempting to uninstall the patch when the condition is false&
>  the patch has AllowRemoval="no"?
> Because Burn always attempts to uninstall a package that's present when
> its install condition is false, and Burn doesn't know the patch is
> permanent. You can file a feature request to change either of those
> facts or consider using patch applicability instead of install
> conditions to control the patch installation.
>
> --
> sig://boB
> http://joyofsetup.com/
>
>
>
> --
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>

-- 
virtually, Rob Mensching - http://RobMensching.com LLC
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] killing Chrome and Firefox

Here's another possible clue:
http://sourceforge.net/tracker/?func=detail&atid=642717&aid=1989218&group_id=105970
-
"CloseApplication element doesn't cause the FilesInUseDialog".

Indeed, the latest CloseApps.cpp still has:

//
// Do the UI dance now.
//
/*

TODO: Do this eventually

*
*

On Thu, Apr 26, 2012 at 2:06 AM, E. Timothy Uy  wrote:

> Dear Peter,
>
> Thanks for writing back. util:CloseApplication will close the application
> if CloseMessage="yes", but when CloseMessage="no" it seems that this should
> trigger the FilesInUse dialog. At least, that was my expectation.
>
> In Wix tutorials (e.g.,
> http://weblogs.sqlteam.com/mladenp/archive/2010/02/17/WiX-3-Tutorial-Understanding-main-WXS-and-WXI-file.aspx)
> it seems that FilesInUse is specifically for use with CloseApplication:
>
> 
>> 
>>  
>>  
>>  
>>  
>
>
> I know now that I can close the browsers using CloseMessage="yes", but the
> best would be to show them the FilesInUse dialog and let them choose what
> to do.
>
> Puzzled,
> Tim
>
>
> On Thu, Apr 26, 2012 at 1:55 AM, Peter Shirtcliffe 
> wrote:
>
>> FilesInUse automatically detects files in use during InstallValidate and
>> displays the dialog if one of those files are changed.
>>
>> Restart manager is a newer feature of Windows Installer and works with
>> filesinuse. The applications that are shut down because they have files in
>> use must have registered with restart manager when they were installed.
>> That
>> enables them to restart automatically, saving and restoring state.
>>
>> I don't think closeapplication has much to do with filesinuse. I suspect
>> it
>> sends WM_CLOSE messages to applications or possibly kills them. If your
>> installer runs elevated then setting ElevatedCloseMessage="yes" should be
>> more effective.
>>
>> -Original Message-
>> From: E. Timothy Uy [mailto:t...@loqu8.com]
>> Sent: 26 April 2012 00:28
>> To: General discussion for Windows Installer XML toolset.
>> Subject: Re: [WiX-users] killing Chrome and Firefox
>>
>> It seems that CloseMessage="no" should have triggered FilesInUse, but it
>> doesn't at all. The installation just proceeds.
>>
>> On Wed, Apr 25, 2012 at 1:05 PM, E. Timothy Uy  wrote:
>>
>> > Silly me. I was able to get the browsers to close by setting
>> > CloseMessage="yes". Next step, how do I use "FilesInUse"?
>> >
>> >
>> > On Wed, Apr 25, 2012 at 12:18 PM, E. Timothy Uy  wrote:
>> >
>> >> I changed WixCloseApplications to run before InstallInitialize but
>> >> this did not help either. From the .msi log, I see
>> >>
>> >> Action 12:12:49: WixCloseApplications.
>> >>> Action start 12:12:49: WixCloseApplications.
>> >>> Action ended 12:12:50: WixCloseApplications. Return value 1.
>> >>> Action 12:12:50: InstallInitialize.
>> >>> Action start 12:12:50: InstallInitialize.
>> >>> Action ended 12:12:55: InstallInitialize. Return value 1.
>> >>
>> >>
>> >> I expected some kind of dialog saying I had these applications open,
>> >> and for the installer to either shut them down or prompt me to
>> >> shutdown, but no browsers get closed and there is no indication of any
>> changes.
>> >>
>> >>
>> >>> 
>> >>>   
>> >>>   
>> >>>   
>> >>>   
>> >>> 
>> >>> 
>> >>>   > Before="InstallInitialize" />
>> >>>   > >>> After="InstallFiles">Not Installed
>> >>>   > >>> After="QtExecInstallCmdLineSet">Not Installed
>> >>>   
>> >>>   > >>> Before="RemoveFiles">Installed
>> >>>   > >>> After="QtExecUninstallCmdLineSet">Installed
>> >>> 
>> >>>
>> >>> > >>>Description="Internet Explorer is still
>> >>> running."
>> >>>ElevatedCloseMessage="no"
>> >>>RebootPrompt="no"
>> >>>Target="iexplore.exe"/>
>> >>> > >>>Description="Chrome is still running."
>> >>>ElevatedCloseMessage="no"
>> >>>RebootPrompt="no"
>> >>>Target="chrome.exe"/>
>> >>> > >>>Description="Chrome is still running."
>> >>>ElevatedCloseMessage="no"
>> >>>RebootPrompt="no"
>> >>>Target="firefox.exe"/>
>> >>>
>> >>
>> >>
>> >> On Wed, Apr 25, 2012 at 12:04 PM, E. Timothy Uy  wrote:
>> >>
>> >>> By the way, the code below doesn't work at all.
>> >>>
>> >>>
>> >>> On Wed, Apr 25, 2012 at 12:02 PM, E. Timothy Uy 
>> wrote:
>> >>>
>>  Looks like I can only use WixCloseApplications once. How do I close
>>  all browsers both before installation and right before
>>  uninstallation? Trying the following...
>> 
>>   > >Description="Internet Explorer is still
>> > running."
>> >ElevatedCloseMessage="no"
>> >RebootPrompt="no"
>> >T

Re: [WiX-users] killing Chrome and Firefox

Dear Peter,

Thanks for writing back. util:CloseApplication will close the application
if CloseMessage="yes", but when CloseMessage="no" it seems that this should
trigger the FilesInUse dialog. At least, that was my expectation.

In Wix tutorials (e.g.,
http://weblogs.sqlteam.com/mladenp/archive/2010/02/17/WiX-3-Tutorial-Understanding-main-WXS-and-WXI-file.aspx)
it seems that FilesInUse is specifically for use with CloseApplication:


> 
> 
> 
> 
>  


I know now that I can close the browsers using CloseMessage="yes", but the
best would be to show them the FilesInUse dialog and let them choose what
to do.

Puzzled,
Tim


On Thu, Apr 26, 2012 at 1:55 AM, Peter Shirtcliffe wrote:

> FilesInUse automatically detects files in use during InstallValidate and
> displays the dialog if one of those files are changed.
>
> Restart manager is a newer feature of Windows Installer and works with
> filesinuse. The applications that are shut down because they have files in
> use must have registered with restart manager when they were installed.
> That
> enables them to restart automatically, saving and restoring state.
>
> I don't think closeapplication has much to do with filesinuse. I suspect it
> sends WM_CLOSE messages to applications or possibly kills them. If your
> installer runs elevated then setting ElevatedCloseMessage="yes" should be
> more effective.
>
> -Original Message-
> From: E. Timothy Uy [mailto:t...@loqu8.com]
> Sent: 26 April 2012 00:28
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] killing Chrome and Firefox
>
> It seems that CloseMessage="no" should have triggered FilesInUse, but it
> doesn't at all. The installation just proceeds.
>
> On Wed, Apr 25, 2012 at 1:05 PM, E. Timothy Uy  wrote:
>
> > Silly me. I was able to get the browsers to close by setting
> > CloseMessage="yes". Next step, how do I use "FilesInUse"?
> >
> >
> > On Wed, Apr 25, 2012 at 12:18 PM, E. Timothy Uy  wrote:
> >
> >> I changed WixCloseApplications to run before InstallInitialize but
> >> this did not help either. From the .msi log, I see
> >>
> >> Action 12:12:49: WixCloseApplications.
> >>> Action start 12:12:49: WixCloseApplications.
> >>> Action ended 12:12:50: WixCloseApplications. Return value 1.
> >>> Action 12:12:50: InstallInitialize.
> >>> Action start 12:12:50: InstallInitialize.
> >>> Action ended 12:12:55: InstallInitialize. Return value 1.
> >>
> >>
> >> I expected some kind of dialog saying I had these applications open,
> >> and for the installer to either shut them down or prompt me to
> >> shutdown, but no browsers get closed and there is no indication of any
> changes.
> >>
> >>
> >>> 
> >>>   
> >>>   
> >>>   
> >>>   
> >>> 
> >>> 
> >>>/>
> >>>>>> After="InstallFiles">Not Installed
> >>>>>> After="QtExecInstallCmdLineSet">Not Installed
> >>>   
> >>>>>> Before="RemoveFiles">Installed
> >>>>>> After="QtExecUninstallCmdLineSet">Installed
> >>> 
> >>>
> >>>  >>>Description="Internet Explorer is still
> >>> running."
> >>>ElevatedCloseMessage="no"
> >>>RebootPrompt="no"
> >>>Target="iexplore.exe"/>
> >>>  >>>Description="Chrome is still running."
> >>>ElevatedCloseMessage="no"
> >>>RebootPrompt="no"
> >>>Target="chrome.exe"/>
> >>>  >>>Description="Chrome is still running."
> >>>ElevatedCloseMessage="no"
> >>>RebootPrompt="no"
> >>>Target="firefox.exe"/>
> >>>
> >>
> >>
> >> On Wed, Apr 25, 2012 at 12:04 PM, E. Timothy Uy  wrote:
> >>
> >>> By the way, the code below doesn't work at all.
> >>>
> >>>
> >>> On Wed, Apr 25, 2012 at 12:02 PM, E. Timothy Uy  wrote:
> >>>
>  Looks like I can only use WixCloseApplications once. How do I close
>  all browsers both before installation and right before
>  uninstallation? Trying the following...
> 
>    >Description="Internet Explorer is still
> > running."
> >ElevatedCloseMessage="no"
> >RebootPrompt="no"
> >Target="iexplore.exe"/>
> >  >Description="Chrome is still running."
> >ElevatedCloseMessage="no"
> >RebootPrompt="no"
> >Target="chrome.exe"/>
> >  >Description="Chrome is still running."
> >ElevatedCloseMessage="no"
> >RebootPrompt="no"
> >Target="firefox.exe"/>
> > 
>

Re: [WiX-users] killing Chrome and Firefox

2012-04-26 Thread Peter Shirtcliffe

FilesInUse automatically detects files in use during InstallValidate and
displays the dialog if one of those files are changed.

Restart manager is a newer feature of Windows Installer and works with
filesinuse. The applications that are shut down because they have files in
use must have registered with restart manager when they were installed. That
enables them to restart automatically, saving and restoring state.

I don't think closeapplication has much to do with filesinuse. I suspect it
sends WM_CLOSE messages to applications or possibly kills them. If your
installer runs elevated then setting ElevatedCloseMessage="yes" should be
more effective.

-Original Message-
From: E. Timothy Uy [mailto:t...@loqu8.com] 
Sent: 26 April 2012 00:28
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] killing Chrome and Firefox

It seems that CloseMessage="no" should have triggered FilesInUse, but it
doesn't at all. The installation just proceeds.

On Wed, Apr 25, 2012 at 1:05 PM, E. Timothy Uy  wrote:

> Silly me. I was able to get the browsers to close by setting 
> CloseMessage="yes". Next step, how do I use "FilesInUse"?
>
>
> On Wed, Apr 25, 2012 at 12:18 PM, E. Timothy Uy  wrote:
>
>> I changed WixCloseApplications to run before InstallInitialize but 
>> this did not help either. From the .msi log, I see
>>
>> Action 12:12:49: WixCloseApplications.
>>> Action start 12:12:49: WixCloseApplications.
>>> Action ended 12:12:50: WixCloseApplications. Return value 1.
>>> Action 12:12:50: InstallInitialize.
>>> Action start 12:12:50: InstallInitialize.
>>> Action ended 12:12:55: InstallInitialize. Return value 1.
>>
>>
>> I expected some kind of dialog saying I had these applications open, 
>> and for the installer to either shut them down or prompt me to 
>> shutdown, but no browsers get closed and there is no indication of any
changes.
>>
>>
>>> 
>>>   
>>>   
>>>   
>>>   
>>> 
>>> 
>>>   
>>>   >> After="InstallFiles">Not Installed
>>>   >> After="QtExecInstallCmdLineSet">Not Installed
>>>   
>>>   >> Before="RemoveFiles">Installed
>>>   >> After="QtExecUninstallCmdLineSet">Installed
>>> 
>>>
>>> >>Description="Internet Explorer is still 
>>> running."
>>>ElevatedCloseMessage="no"
>>>RebootPrompt="no"
>>>Target="iexplore.exe"/>
>>> >>Description="Chrome is still running."
>>>ElevatedCloseMessage="no"
>>>RebootPrompt="no"
>>>Target="chrome.exe"/>
>>> >>Description="Chrome is still running."
>>>ElevatedCloseMessage="no"
>>>RebootPrompt="no"
>>>Target="firefox.exe"/>
>>>
>>
>>
>> On Wed, Apr 25, 2012 at 12:04 PM, E. Timothy Uy  wrote:
>>
>>> By the way, the code below doesn't work at all.
>>>
>>>
>>> On Wed, Apr 25, 2012 at 12:02 PM, E. Timothy Uy  wrote:
>>>
 Looks like I can only use WixCloseApplications once. How do I close 
 all browsers both before installation and right before 
 uninstallation? Trying the following...

  Description="Internet Explorer is still 
> running."
>ElevatedCloseMessage="no"
>RebootPrompt="no"
>Target="iexplore.exe"/>
> Description="Chrome is still running."
>ElevatedCloseMessage="no"
>RebootPrompt="no"
>Target="chrome.exe"/>
> Description="Chrome is still running."
>ElevatedCloseMessage="no"
>RebootPrompt="no"
>Target="firefox.exe"/>
> 
>    />




 On Wed, Apr 25, 2012 at 2:03 AM, Peter Shirtcliffe < 
 pshirtcli...@sdl.com> wrote:

> See Util:CloseApplication in the wix help.
>
> -Original Message-
> From: E. Timothy Uy [mailto:t...@loqu8.com]
> Sent: 25 April 2012 06:00
> To: General discussion for Windows Installer XML toolset.
> Subject: [WiX-users] killing Chrome and Firefox
>
> Hi, we are a requirement to kill Chrome and Firefox during 
> install, so that we can install or modify a plugin. What is the 
> best way to kill processes (or ask the user to kill processes)?
>
> Thanks,
> Tim
>
> --
> ---
> -
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and 
> threat landsca

[WiX-users] Customising a bootstrapper theme

2012-04-26 Thread Bertrand D

As previously stated in my previous thread (but not clearly as I had actually
two different issues) when I try to use a customized theme for the
bootstrapper some events are not processed at least for the "failure"
dialog. I haven't checked with the other ones.

This is what I used:

Every time I set "ThemeFile" in the "failure" dialog the link
FailureLogFileLink and the "close" button have no effect.

Please note that the ThemeFile file (RtfTheme.xml) was simply copied from
the src\ext\BalExtension\wixstdba\Resources. No customization was made
(yet).

If I modify the content of the ThemeFile file the changes are correctly
taken in account but the issues remain.

Using a variable WixStdbaThemeXml instead of using ThemeFile gives me the
same result. Everyting works fine if I simply use (without WixStdbaThemeXml)
:

I used the WiX Toolset v3.6.2809.0.

What did I miss?

--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Customising-a-bootstrapper-theme-tp7501905p7501905.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] How to use FileInUse dialog