Re: [WiX-users] Disable Files In Use dialog

[Rob Hamflett]

You can suppress the FilesInUse dialog by specifying 
Dialog@Modeless="yes" and Dialog@Hidden="yes".

Rob


On 23/08/2012 01:31, Gustavo Gustavo wrote:
> I’ve been struggling to get rid of the Files In Use dialog. Seems like
> there’s no easy way out.
>
> Ideally, I would like to execute my MSI with the /qb! mode, ie, showing
> only the progress bar with modal dialog boxes enabled (for instance, the
> reboot dialog at the end if needed for some reason).
>
> I don’t care if a reboot is needed at the end because another process had a
> handle open to a file that must be replaced during the upgrade, as long as
> the user has this message shown at the installation end. That’s why I
> cannot use /passive or /qb-!
>
> During the installation, through Custom Actions, my MSI does it best to
> close processes (well known ones in my business domain) that might block a
> file replacement. The problem is that there CAs must execute with elevated
> privileges (hence deferred), and, of course, after the InstallValidate
> action, that shows up the Files In Use dialog. Therefore, these CAs happens
> after the Files In Use dialog is shown. So it’s impossible to execute my
> CAs before the InstallValidate step.
>
> ** **
>
> Will I have to create a bootstrapper what would kill the holding processes
> before executing the MSI, so that the Files In Use won’t detect anything
> (normally, since the user may be editing/blocking something, but that
> should be very rare, and outside control)???
>
> ** **
>
> I’ve tried to play with
>
> ** **
>
> 
>
> 
>
> 
>
> ** **
>
> but it works sometimes and sometimes not (that really got be puzzled), so I
> cannot trust them.
>
> ** **
>
> Kind Regards,
>
> /Gustavo
>
> **
> --
> 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/
>



--
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] MSI Installation to UNC Path

[Osanger, Martin]

Hello,

Are there any restrictions to create a folder which is reachable via UNC Path?

The user can create folders in the Programs directory but the setup can't.

MSI (s) (D4:24) [12:46:14:010]: Executing op: 
FolderCreate(Folder=\\ligov\users\UserData\\AppData\Roaming\Microsoft\Windows\Start
 Menu\Programs\MyFolder\,Foreign=0,,)
CreateFolders: Folder: 
\\ligov\users\UserData\\AppData\Roaming\Microsoft\Windows\Start 
Menu\Programs\MyFolder\
MSI (s) (D4:24) [12:46:14:026]: Note: 1: 1317 2: \\ligov\users\UserData
Error 1317. An error occurred while attempting to create the directory: 
\\ligov\users\UserData
MSI (s) (D4:B4) [12:46:22:576]: I/O on thread 2992 could not be cancelled. 
Error: 1168
MSI (s) (D4:B4) [12:46:22:576]: I/O on thread 5432 could not be cancelled. 
Error: 1168
MSI (s) (D4:B4) [12:46:22:576]: I/O on thread 4476 could not be cancelled. 
Error: 1168
MSI (s) (D4:B4) [12:46:22:576]: I/O on thread 2180 could not be cancelled. 
Error: 1168
MSI (s) (D4:B4) [12:46:22:576]: I/O on thread 5784 could not be cancelled. 
Error: 1168
MSI (s) (D4:B4) [12:46:22:576]: I/O on thread 3136 could not be cancelled. 
Error: 1168
MSI (s) (D4:B4) [12:46:22:576]: I/O on thread 2956 could not be cancelled. 
Error: 1168
MSI (s) (D4:B4) [12:46:22:576]: I/O on thread 2356 could not be cancelled. 
Error: 1168
MSI (s) (D4:B4) [12:46:22:576]: I/O on thread 1060 could not be cancelled. 
Error: 1168
MSI (s) (D4:B4) [12:46:22:576]: I/O on thread 5492 could not be cancelled. 
Error: 1168
MSI (s) (D4:B4) [12:46:22:576]: I/O on thread 2152 could not be cancelled. 
Error: 1168
MSI (s) (D4:24) [12:46:22:576]: Product:  -- Error 1317. An error 
occurred while attempting to create the directory: \\ligov\users\UserData

best regards,
Martin

--
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] UnistallString is not written in Software\Microsoft\Windows\CurrentVersion\Uninstall\ registry key

[Peter Shirtcliffe]

Windows Installer itself writes the value.
http://msdn.microsoft.com/en-us/library/aa372105%28v=VS.85%29.aspx
However, the uninstall string is not used by Windows Installer so does it
matter that it wasn't written ?

-Original Message-
From: Alec Swan [mailto:alecs...@gmail.com] 
Sent: 23 August 2012 00:23
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] UnistallString is not written in
Software\Microsoft\Windows\CurrentVersion\Uninstall\ registry key

Hello,

I am trying to track down why our installer generated using Wix 3.0 stopped
writing the UninstallString value in
Software\Microsoft\Windows\CurrentVersion\Uninstall\ registry key. At some
point we must have changed some code that broke this behavior.

Where should I start troubleshooting this? Which Wix action writes this
registry key?

Thanks,

Alec

-
-
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
SDL PLC confidential, all rights reserved.
If you are not the intended recipient of this mail SDL requests and requires 
that you delete it without acting upon or copying any of its contents, and we 
further request that you advise us.
SDL PLC is a public limited company registered in England and Wales.  
Registered number: 02675207.
Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6 7DY, 
UK.


--
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] How to create a feature tree with burn?

[Daniel Bruce]

I'm trying to accomplish something similar with my own Bootstrapper 
Application, and would like to find this XML file. What is the suggested way of 
locating this file? I'm unsure how to locate my BA DLL at runtime without 
resorting to magic strings.

In addition, is there any documentation at all about this file, and its format? 
Is it a supported way of accessing bundle information, or is it just a magic 
file? I can't seem to locate anything about it apart from scattered mailing 
list posts.

> -Original Message-
> From: Rob Mensching [mailto:r...@robmensching.com]
> Sent: 20. august 2012 23:37
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] How to create a feature tree with burn?
> 
> BootstrapperApplicationData.xml is provided with your BA. It's right next
> to the DLL at runtime.  You won't see it until the BA is running.
> 
> On Mon, Aug 20, 2012 at 10:34 AM, CristianI  wrote:
> 
> > It's good to hear, that these things are possible =) But where do I
> > find the BootstrapperApplicationData.xml? I read that it should be
> > extracted to the temporary folder, but it's not working for me.
> > Do
> > I have to do something special, am I missing something or is it enough
> > compile it the usually way with candle and light?
> >
> > Thanks again very much for the help; I'm trying to get as much info
> > about
> > OnPlanPackageBegin() as I can find in the next hours =)
> >
> >
> >
> > --
> > View this message in context:
> > http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/How-
> to-c
> > reate-a-feature-tree-with-burn-tp7579948p7579957.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
> 
> ___
> ___
> This email has been scanned by the Symantec Email Security.cloud
> service.
> For more information please visit http://www.symanteccloud.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] crc error on wix 3.7 aditional downloads

[rowbot]

Thanks, however if I 'msbuild wix64.proj', I get errors as follows:

LINK : fatal error LNK1104: cannot open file 'wcautil_2010.lib'

and then various errors on
"C:\wix3.7.821.0-sources\build\debug\x86\GenerateWixInclude.exe" which
doesn't exist...

please advise,




--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/crc-error-on-wix-3-7-aditional-downloads-tp7579981p7580020.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] MSI Installation to UNC Path

[Peter Shirtcliffe]

Windows Installer runs as the localsystem account which doesn't have
permissions on the network so you're probably being denied access to create
the directory. Check the permissions on the share and on the directory.

-Original Message-
From: Osanger, Martin [mailto:martin.osan...@fabasoft.com] 
Sent: 23 August 2012 08:51
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] MSI Installation to UNC Path

Hello,

Are there any restrictions to create a folder which is reachable via UNC
Path?

The user can create folders in the Programs directory but the setup can't.

MSI (s) (D4:24) [12:46:14:010]: Executing op:
FolderCreate(Folder=\\ligov\users\UserData\\AppData\Roaming\Microsoft\W
indows\Start Menu\Programs\MyFolder\,Foreign=0,,)
CreateFolders: Folder:
\\ligov\users\UserData\\AppData\Roaming\Microsoft\Windows\Start
Menu\Programs\MyFolder\ MSI (s) (D4:24) [12:46:14:026]: Note: 1: 1317 2:
\\ligov\users\UserData Error 1317. An error occurred while attempting to
create the directory: \\ligov\users\UserData MSI (s) (D4:B4) [12:46:22:576]:
I/O on thread 2992 could not be cancelled. Error: 1168 MSI (s) (D4:B4)
[12:46:22:576]: I/O on thread 5432 could not be cancelled. Error: 1168 MSI
(s) (D4:B4) [12:46:22:576]: I/O on thread 4476 could not be cancelled. Error:
1168 MSI (s) (D4:B4) [12:46:22:576]: I/O on thread 2180 could not be
cancelled. Error: 1168 MSI (s) (D4:B4) [12:46:22:576]: I/O on thread 5784
could not be cancelled. Error: 1168 MSI (s) (D4:B4) [12:46:22:576]: I/O on
thread 3136 could not be cancelled. Error: 1168 MSI (s) (D4:B4)
[12:46:22:576]: I/O on thread 2956 could not be cancelled. Error: 1168 MSI
(s) (D4:B4) [12:46:22:576]: I/O on thread 2356 could not be cancelled. Error:
1168 MSI (s) (D4:B4) [12:46:22:576]: I/O on thread 1060 could not be
cancelled. Error: 1168 MSI (s) (D4:B4) [12:46:22:576]: I/O on thread 5492
could not be cancelled. Error: 1168 MSI (s) (D4:B4) [12:46:22:576]: I/O on
thread 2152 could not be cancelled. Error: 1168 MSI (s) (D4:24)
[12:46:22:576]: Product:  -- Error 1317. An error occurred while
attempting to create the directory: \\ligov\users\UserData

best regards,
Martin

-
-
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
SDL PLC confidential, all rights reserved.
If you are not the intended recipient of this mail SDL requests and requires 
that you delete it without acting upon or copying any of its contents, and we 
further request that you advise us.
SDL PLC is a public limited company registered in England and Wales.  
Registered number: 02675207.
Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6 7DY, 
UK.


--
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 CLIENTUILEVEL

[Christoffel le Roux]

Hi Neil, I'm on the latest 3.7 build. If I place a breakpoint inside my 
IEmbeddedUI implementation the 'Run' method is never hit.

Kind regards,
Christoffel le Roux




-Original Message-
From: Neil Sleightholm [mailto:n...@x2systems.com]
Sent: Wednesday, August 22, 2012 11:09 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Burn CLIENTUILEVEL

Not sure if this is what you want but you can set 
MsiPackage/@DisplayInternalUI="yes" to display your MSI UI.

Neil

-Original Message-
From: Christoffel le Roux [mailto:christoffe...@tech.flowcentric.com]
Sent: 22 August 2012 09:29
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Burn CLIENTUILEVEL

Hi, What I need to achieve is displaying the Embedded UI in my MSI packages. I 
know I could just create a custom BA UI and use that, but all my setup projects 
needs to be able to install and manage the installation of multiple instances. 
Since there's no way to ask burn to apply a transform to an package I had to 
create the embedded UI's to achieve this. Please can anyone advise.

Kind regards,
Christoffel le Roux


--
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

--
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

--
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] Burn custom managed UI not starting

[Adkins, Christopher]

Hi everyone,

I am trying to get a custom burn UI working, but I can't even get it to start. 
I have looked at the WiXUX project as an example, but I am stuck on what I am 
doing wrong. The log tells me:

[0428:0BC8][2012-08-23T12:04:17]: Burn v3.6.2928.0, Windows v6.1 (Build 7600: 
Service Pack 0), path: C:\Users\Administrator\Desktop\WebSetup.exe, cmdline: 
'-burn.unelevated BurnPipe.{6CBBF06B-E4A0-46FA-9AAA-7375658D17A8} 
{E0D4EE1A-96F0-4E5C-B8FF-38EF4623E92D} 2064'
[0428:0BC8][2012-08-23T12:04:17]: Setting string variable 'WixBundleLog' to 
value 'C:\Temp\WebSetup.Bootstrapper_20120823120417.log'
[0428:0BC8][2012-08-23T12:04:17]: Setting string variable 
'WixBundleOriginalSource' to value 'C:\Users\Administrator\Desktop\WebSetup.exe'
[0428:0BC8][2012-08-23T12:04:18]: Setting string variable 'WixBundleName' to 
value 'WebSetup.Bootstrapper'
[0428:0BC8][2012-08-23T12:04:18]: Loading managed bootstrapper application.
[0428:0BC8][2012-08-23T12:04:18]: Error 0x80070002: Failed to create the 
managed bootstrapper application.
[0428:0BC8][2012-08-23T12:04:18]: Error 0x80070002: Failed to create UX.
[0428:0BC8][2012-08-23T12:04:18]: Error 0x80070002: Failed to load UX.
[0428:0BC8][2012-08-23T12:04:18]: Error 0x80070002: Failed while running
[0428:0BC8][2012-08-23T12:04:18]: Variable: WixBundleAction = 4
[0428:0BC8][2012-08-23T12:04:18]: Variable: WixBundleElevated = 1
[0428:0BC8][2012-08-23T12:04:18]: Variable: WixBundleLog = 
C:\Temp\WebSetup.Bootstrapper_20120823120417.log
[0428:0BC8][2012-08-23T12:04:18]: Variable: WixBundleName = 
WebSetup.Bootstrapper
[0428:0BC8][2012-08-23T12:04:18]: Variable: WixBundleOriginalSource = 
C:\Users\Administrator\Desktop\WebSetup.exe
[0428:0BC8][2012-08-23T12:04:18]: Variable: WixBundleProviderKey = 
{a153399e-410b-41a3-aa5c-d6391841f7f7}
[0428:0BC8][2012-08-23T12:04:18]: Variable: WixBundleTag =
[0428:0BC8][2012-08-23T12:04:18]: Variable: WixBundleVersion = 1.0.0.0
[0428:0BC8][2012-08-23T12:04:18]: Error 0x80070002: Failed to run per-user mode.
[0428:0BC8][2012-08-23T12:04:18]: Exit code: 0x80070002, restarting: No

The call to the bootstrapper looks like this:


 
 


And finally the BootstrapperCore.Config looks like this:






 

  

  

 

 

 

 

 

 

 

  

  

 

 



I have also tried changing the children of the wix.bootstrapper element so they 
are all on the same level, but that didn't make a difference. Any help will be 
greatly appreciated.


Mit freundlichen Grüßen | With best regards

Christopher Adkins
Manager Research and Development


--
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 CLIENTUILEVEL

[Neil Sleightholm]

It might be worth dropping back to 3.6, 3.7 is very new.

Neil

-Original Message-
From: Christoffel le Roux [mailto:christoffe...@tech.flowcentric.com] 
Sent: 23 August 2012 10:52 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Burn CLIENTUILEVEL

Hi Neil, I'm on the latest 3.7 build. If I place a breakpoint inside my 
IEmbeddedUI implementation the 'Run' method is never hit.

Kind regards,
Christoffel le Roux




-Original Message-
From: Neil Sleightholm [mailto:n...@x2systems.com]
Sent: Wednesday, August 22, 2012 11:09 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Burn CLIENTUILEVEL

Not sure if this is what you want but you can set 
MsiPackage/@DisplayInternalUI="yes" to display your MSI UI.

Neil

-Original Message-
From: Christoffel le Roux [mailto:christoffe...@tech.flowcentric.com]
Sent: 22 August 2012 09:29
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Burn CLIENTUILEVEL

Hi, What I need to achieve is displaying the Embedded UI in my MSI packages. I 
know I could just create a custom BA UI and use that, but all my setup projects 
needs to be able to install and manage the installation of multiple instances. 
Since there's no way to ask burn to apply a transform to an package I had to 
create the embedded UI's to achieve this. Please can anyone advise.

Kind regards,
Christoffel le Roux


--
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

--
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

--
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] Burn CLIENTUILEVEL

[Christoffel le Roux]

Hi Neil, I upgraded to 3.7 to see if it will make any difference to my problem 
:), thanks for the help I really appreciate.

Kind regards,
Christoffel le Roux

-Original Message-
From: Neil Sleightholm [mailto:n...@x2systems.com] 
Sent: Thursday, August 23, 2012 12:31 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Burn CLIENTUILEVEL

It might be worth dropping back to 3.6, 3.7 is very new.

Neil

-Original Message-
From: Christoffel le Roux [mailto:christoffe...@tech.flowcentric.com]
Sent: 23 August 2012 10:52 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Burn CLIENTUILEVEL

Hi Neil, I'm on the latest 3.7 build. If I place a breakpoint inside my 
IEmbeddedUI implementation the 'Run' method is never hit.

Kind regards,
Christoffel le Roux




-Original Message-
From: Neil Sleightholm [mailto:n...@x2systems.com]
Sent: Wednesday, August 22, 2012 11:09 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Burn CLIENTUILEVEL

Not sure if this is what you want but you can set 
MsiPackage/@DisplayInternalUI="yes" to display your MSI UI.

Neil

-Original Message-
From: Christoffel le Roux [mailto:christoffe...@tech.flowcentric.com]
Sent: 22 August 2012 09:29
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Burn CLIENTUILEVEL

Hi, What I need to achieve is displaying the Embedded UI in my MSI packages. I 
know I could just create a custom BA UI and use that, but all my setup projects 
needs to be able to install and manage the installation of multiple instances. 
Since there's no way to ask burn to apply a transform to an package I had to 
create the embedded UI's to achieve this. Please can anyone advise.

Kind regards,
Christoffel le Roux


--
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

--
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

--
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/11

Re: [WiX-users] Burn custom managed UI not starting

[Christoffel le Roux]

Hi, I think you mabe need the following in your Assembly.cs 

[assembly: BootstrapperApplication(typeof(Bootstrap))]

Kind regards,
Christoffel le Roux
Software Development Engineer



Finalist: 2011 Microsoft Customer Experience Partner of Year
www.flowcentric.com | Email: christoffe...@flowcentric.com| Mobile: +27 23733 
752 | MSN: christoffler...@hotmail.com


FlowCentric UK/Europe
SoanePoint, 6-8 Market Place
Reading, Berkshire, RG1 2EG
Tel: +44(0) 1189 255 890
FlowCentric Africa/Asia
Fountain Square, 78 Kalkoen Street
Monument Park, 0181
Tel: +27 (0)12 347 4488
FlowCentric Australia/Pacific
Level 18, 333 Ann Street
Brisbane, Qld 4000 
Tel: +61(0)7 3232 1277

This information is intended only for the person or entity to which it is 
addressed and may contain private, confidential, proprietary and/or privileged 
material and may be subject to confidentiality agreements. Any review, 
retransmission, dissemination, or any other use of or taking of any action in 
reliance upon this information, by persons or entities other than the intended 
recipient, is prohibited. If you received this in error, please contact the 
sender and delete the material from all storage media. FlowCentric is neither 
liable for proper, complete transmission of the information contained in this 
communication, any delay in its receipt or that the mail is virus-free.





-Original Message-
From: Adkins, Christopher [mailto:christopher.adk...@docuware.com] 
Sent: Thursday, August 23, 2012 12:11 PM
To: General discussion for Windows Installer XML toolset. 
(wix-users@lists.sourceforge.net)
Subject: [WiX-users] Burn custom managed UI not starting

Hi everyone,

I am trying to get a custom burn UI working, but I can't even get it to start. 
I have looked at the WiXUX project as an example, but I am stuck on what I am 
doing wrong. The log tells me:

[0428:0BC8][2012-08-23T12:04:17]: Burn v3.6.2928.0, Windows v6.1 (Build 7600: 
Service Pack 0), path: C:\Users\Administrator\Desktop\WebSetup.exe, cmdline: 
'-burn.unelevated BurnPipe.{6CBBF06B-E4A0-46FA-9AAA-7375658D17A8} 
{E0D4EE1A-96F0-4E5C-B8FF-38EF4623E92D} 2064'
[0428:0BC8][2012-08-23T12:04:17]: Setting string variable 'WixBundleLog' to 
value 'C:\Temp\WebSetup.Bootstrapper_20120823120417.log'
[0428:0BC8][2012-08-23T12:04:17]: Setting string variable 
'WixBundleOriginalSource' to value 'C:\Users\Administrator\Desktop\WebSetup.exe'
[0428:0BC8][2012-08-23T12:04:18]: Setting string variable 'WixBundleName' to 
value 'WebSetup.Bootstrapper'
[0428:0BC8][2012-08-23T12:04:18]: Loading managed bootstrapper application.
[0428:0BC8][2012-08-23T12:04:18]: Error 0x80070002: Failed to create the 
managed bootstrapper application.
[0428:0BC8][2012-08-23T12:04:18]: Error 0x80070002: Failed to create UX.
[0428:0BC8][2012-08-23T12:04:18]: Error 0x80070002: Failed to load UX.
[0428:0BC8][2012-08-23T12:04:18]: Error 0x80070002: Failed while running
[0428:0BC8][2012-08-23T12:04:18]: Variable: WixBundleAction = 4
[0428:0BC8][2012-08-23T12:04:18]: Variable: WixBundleElevated = 1
[0428:0BC8][2012-08-23T12:04:18]: Variable: WixBundleLog = 
C:\Temp\WebSetup.Bootstrapper_20120823120417.log
[0428:0BC8][2012-08-23T12:04:18]: Variable: WixBundleName = 
WebSetup.Bootstrapper
[0428:0BC8][2012-08-23T12:04:18]: Variable: WixBundleOriginalSource = 
C:\Users\Administrator\Desktop\WebSetup.exe
[0428:0BC8][2012-08-23T12:04:18]: Variable: WixBundleProviderKey = 
{a153399e-410b-41a3-aa5c-d6391841f7f7}
[0428:0BC8][2012-08-23T12:04:18]: Variable: WixBundleTag =
[0428:0BC8][2012-08-23T12:04:18]: Variable: WixBundleVersion = 1.0.0.0
[0428:0BC8][2012-08-23T12:04:18]: Error 0x80070002: Failed to run per-user mode.
[0428:0BC8][2012-08-23T12:04:18]: Exit code: 0x80070002, restarting: No

The call to the bootstrapper looks like this:


 
  

And finally the BootstrapperCore.Config looks like this:






 

  

  

 

 

 

 

 

 

 

  

  

 

 



I have also tried changing the children of the wix.bootstrapper element so they 
are all on the same level, but that didn't make a difference. Any help will be 
greatly appreciated.


Mit freundlichen Grüßen | With best regards

Christopher Adkins
Manager Research and Development


--
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 custom managed UI not starting

[Adkins, Christopher]

Sorry, I forgot to mention that I also included that. I am not sure what else I 
can try and sadly I haven't found any information about that error number 
either.

Best regards,
Christopher Adkins
Manager Research and Development

-Original Message-
From: Christoffel le Roux [mailto:christoffe...@tech.flowcentric.com] 
Sent: Donnerstag, 23. August 2012 12:41
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Burn custom managed UI not starting

Hi, I think you mabe need the following in your Assembly.cs 

[assembly: BootstrapperApplication(typeof(Bootstrap))]

Kind regards,
Christoffel le Roux
Software Development Engineer



Finalist: 2011 Microsoft Customer Experience Partner of Year 
www.flowcentric.com | Email: christoffe...@flowcentric.com| Mobile: +27 23733 
752 | MSN: christoffler...@hotmail.com


FlowCentric UK/Europe
SoanePoint, 6-8 Market Place
Reading, Berkshire, RG1 2EG
Tel: +44(0) 1189 255 890
FlowCentric Africa/Asia
Fountain Square, 78 Kalkoen Street
Monument Park, 0181
Tel: +27 (0)12 347 4488
FlowCentric Australia/Pacific
Level 18, 333 Ann Street
Brisbane, Qld 4000
Tel: +61(0)7 3232 1277

This information is intended only for the person or entity to which it is 
addressed and may contain private, confidential, proprietary and/or privileged 
material and may be subject to confidentiality agreements. Any review, 
retransmission, dissemination, or any other use of or taking of any action in 
reliance upon this information, by persons or entities other than the intended 
recipient, is prohibited. If you received this in error, please contact the 
sender and delete the material from all storage media. FlowCentric is neither 
liable for proper, complete transmission of the information contained in this 
communication, any delay in its receipt or that the mail is virus-free.





-Original Message-
From: Adkins, Christopher [mailto:christopher.adk...@docuware.com]
Sent: Thursday, August 23, 2012 12:11 PM
To: General discussion for Windows Installer XML toolset. 
(wix-users@lists.sourceforge.net)
Subject: [WiX-users] Burn custom managed UI not starting

Hi everyone,

I am trying to get a custom burn UI working, but I can't even get it to start. 
I have looked at the WiXUX project as an example, but I am stuck on what I am 
doing wrong. The log tells me:

[0428:0BC8][2012-08-23T12:04:17]: Burn v3.6.2928.0, Windows v6.1 (Build 7600: 
Service Pack 0), path: C:\Users\Administrator\Desktop\WebSetup.exe, cmdline: 
'-burn.unelevated BurnPipe.{6CBBF06B-E4A0-46FA-9AAA-7375658D17A8} 
{E0D4EE1A-96F0-4E5C-B8FF-38EF4623E92D} 2064'
[0428:0BC8][2012-08-23T12:04:17]: Setting string variable 'WixBundleLog' to 
value 'C:\Temp\WebSetup.Bootstrapper_20120823120417.log'
[0428:0BC8][2012-08-23T12:04:17]: Setting string variable 
'WixBundleOriginalSource' to value 'C:\Users\Administrator\Desktop\WebSetup.exe'
[0428:0BC8][2012-08-23T12:04:18]: Setting string variable 'WixBundleName' to 
value 'WebSetup.Bootstrapper'
[0428:0BC8][2012-08-23T12:04:18]: Loading managed bootstrapper application.
[0428:0BC8][2012-08-23T12:04:18]: Error 0x80070002: Failed to create the 
managed bootstrapper application.
[0428:0BC8][2012-08-23T12:04:18]: Error 0x80070002: Failed to create UX.
[0428:0BC8][2012-08-23T12:04:18]: Error 0x80070002: Failed to load UX.
[0428:0BC8][2012-08-23T12:04:18]: Error 0x80070002: Failed while running
[0428:0BC8][2012-08-23T12:04:18]: Variable: WixBundleAction = 4
[0428:0BC8][2012-08-23T12:04:18]: Variable: WixBundleElevated = 1
[0428:0BC8][2012-08-23T12:04:18]: Variable: WixBundleLog = 
C:\Temp\WebSetup.Bootstrapper_20120823120417.log
[0428:0BC8][2012-08-23T12:04:18]: Variable: WixBundleName = 
WebSetup.Bootstrapper
[0428:0BC8][2012-08-23T12:04:18]: Variable: WixBundleOriginalSource = 
C:\Users\Administrator\Desktop\WebSetup.exe
[0428:0BC8][2012-08-23T12:04:18]: Variable: WixBundleProviderKey = 
{a153399e-410b-41a3-aa5c-d6391841f7f7}
[0428:0BC8][2012-08-23T12:04:18]: Variable: WixBundleTag =
[0428:0BC8][2012-08-23T12:04:18]: Variable: WixBundleVersion = 1.0.0.0
[0428:0BC8][2012-08-23T12:04:18]: Error 0x80070002: Failed to run per-user mode.
[0428:0BC8][2012-08-23T12:04:18]: Exit code: 0x80070002, restarting: No

The call to the bootstrapper looks like this:


 
  

And finally the BootstrapperCore.Config looks like this:






 

  

  

 

 

 

 

 

 

 

  

  

 

 



I have also tried changing the children of the wix.bootstrapper element so they 
are all on the same level, but that didn't make a difference. Any help will be 
greatly appreciated.


Mit freundlichen Grüßen | With best regards

Christopher Adkins
Manager Research and Development


--
Live Security Virtual Con

[WiX-users] (no subject)

[Aditya Mohan]

Hello Guys.

We are creating an installer that uses multiple merge modules. Two of
these modules deploy a particular file at the same location, hence
causing a compilation error.
We can alter only one of the modules.

The error is:

light.exe : error LGHT0204 : ICE30: The target file
'pbsgpqfc.res|abc.resources' is installed in
'[ProgramFilesFolder]\xxx\xxx\en\' by two different components on an LFN
system:
'_001359A8D31745CB9362973F9EE3F5BD.7C263653_7A00_4D9C_B52A_39AF1892BC49'
and 'Adapter_Co
nfig_en.BABCE01A_0CB9_4A62_B877_5E520A53D609'. This breaks component
reference counting.

Any inputs? We need to make sure that once merge module 1 writes a file,
merge module 2 overwrites this file.

Thanks,
Aditya

--
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 custom managed UI not starting

[Henning Krause]

Hi,

0x80070002 means file not found. Make sure you have your file references in the 
bundle correct. You can also use Sysinternals ProcMon to see where the bundle 
tries to locate your bootstrapper.

Kind regards,
Henning

> -Original Message-
> From: Adkins, Christopher [mailto:christopher.adk...@docuware.com]
> Sent: Donnerstag, 23. August 2012 13:04
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Burn custom managed UI not starting
>
> Sorry, I forgot to mention that I also included that. I am not sure what else 
> I
> can try and sadly I haven't found any information about that error number
> either.
>
> Best regards,
> Christopher Adkins
> Manager Research and Development
>
> -Original Message-
> From: Christoffel le Roux [mailto:christoffe...@tech.flowcentric.com]
> Sent: Donnerstag, 23. August 2012 12:41
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Burn custom managed UI not starting
>
> Hi, I think you mabe need the following in your Assembly.cs
>
> [assembly: BootstrapperApplication(typeof(Bootstrap))]
>
> Kind regards,
> Christoffel le Roux
> Software Development Engineer
>
>
>
> Finalist: 2011 Microsoft Customer Experience Partner of Year
> www.flowcentric.com | Email: christoffe...@flowcentric.com| Mobile: +27
> 23733 752 | MSN: christoffler...@hotmail.com
>
>
> FlowCentric UK/Europe
> SoanePoint, 6-8 Market Place
> Reading, Berkshire, RG1 2EG
> Tel: +44(0) 1189 255 890
> FlowCentric Africa/Asia
> Fountain Square, 78 Kalkoen Street
> Monument Park, 0181
> Tel: +27 (0)12 347 4488
> FlowCentric Australia/Pacific
> Level 18, 333 Ann Street
> Brisbane, Qld 4000
> Tel: +61(0)7 3232 1277
>
> This information is intended only for the person or entity to which it is
> addressed and may contain private, confidential, proprietary and/or privileged
> material and may be subject to confidentiality agreements. Any review,
> retransmission, dissemination, or any other use of or taking of any action in
> reliance upon this information, by persons or entities other than the intended
> recipient, is prohibited. If you received this in error, please contact the 
> sender
> and delete the material from all storage media. FlowCentric is neither liable 
> for
> proper, complete transmission of the information contained in this
> communication, any delay in its receipt or that the mail is virus-free.
>
>
>
>
>
> -Original Message-
> From: Adkins, Christopher [mailto:christopher.adk...@docuware.com]
> Sent: Thursday, August 23, 2012 12:11 PM
> To: General discussion for Windows Installer XML toolset. (wix-
> us...@lists.sourceforge.net)
> Subject: [WiX-users] Burn custom managed UI not starting
>
> Hi everyone,
>
> I am trying to get a custom burn UI working, but I can't even get it to 
> start. I
> have looked at the WiXUX project as an example, but I am stuck on what I am
> doing wrong. The log tells me:
>
> [0428:0BC8][2012-08-23T12:04:17]: Burn v3.6.2928.0, Windows v6.1
> (Build 7600: Service Pack 0), path:
> C:\Users\Administrator\Desktop\WebSetup.exe, cmdline: '-burn.unelevated
> BurnPipe.{6CBBF06B-E4A0-46FA-9AAA-7375658D17A8} {E0D4EE1A-96F0-
> 4E5C-B8FF-38EF4623E92D} 2064'
> [0428:0BC8][2012-08-23T12:04:17]: Setting string variable 'WixBundleLog'
> to value 'C:\Temp\WebSetup.Bootstrapper_20120823120417.log'
> [0428:0BC8][2012-08-23T12:04:17]: Setting string variable
> 'WixBundleOriginalSource' to value
> 'C:\Users\Administrator\Desktop\WebSetup.exe'
> [0428:0BC8][2012-08-23T12:04:18]: Setting string variable 'WixBundleName'
> to value 'WebSetup.Bootstrapper'
> [0428:0BC8][2012-08-23T12:04:18]: Loading managed bootstrapper
> application.
> [0428:0BC8][2012-08-23T12:04:18]: Error 0x80070002: Failed to create the
> managed bootstrapper application.
> [0428:0BC8][2012-08-23T12:04:18]: Error 0x80070002: Failed to create UX.
> [0428:0BC8][2012-08-23T12:04:18]: Error 0x80070002: Failed to load UX.
> [0428:0BC8][2012-08-23T12:04:18]: Error 0x80070002: Failed while running
> [0428:0BC8][2012-08-23T12:04:18]: Variable: WixBundleAction = 4
> [0428:0BC8][2012-08-23T12:04:18]: Variable: WixBundleElevated = 1
> [0428:0BC8][2012-08-23T12:04:18]: Variable: WixBundleLog =
> C:\Temp\WebSetup.Bootstrapper_20120823120417.log
> [0428:0BC8][2012-08-23T12:04:18]: Variable: WixBundleName =
> WebSetup.Bootstrapper
> [0428:0BC8][2012-08-23T12:04:18]: Variable: WixBundleOriginalSource =
> C:\Users\Administrator\Desktop\WebSetup.exe
> [0428:0BC8][2012-08-23T12:04:18]: Variable: WixBundleProviderKey =
> {a153399e-410b-41a3-aa5c-d6391841f7f7}
> [0428:0BC8][2012-08-23T12:04:18]: Variable: WixBundleTag =
> [0428:0BC8][2012-08-23T12:04:18]: Variable: WixBundleVersion = 1.0.0.0
> [0428:0BC8][2012-08-23T12:04:18]: Error 0x80070002: Failed to run per-
> user mode.
> [0428:0BC8][2012-08-23T12:04:18]: Exit code: 0x80070002, restarting: No
>
> The call to the bootstrapper looks like this:
>
> 
>  
>   />
> 
>
> And finally the B

Re: [WiX-users] error during compilation-two merge modules writing the same file to disc.

[Aditya Mohan]

With a subject this time :)

-Original Message-
From: Aditya Mohan [mailto:amo...@quark.com] 
Sent: Thursday, August 23, 2012 4:38 PM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] (no subject)

Hello Guys.

We are creating an installer that uses multiple merge modules. Two of
these modules deploy a particular file at the same location, hence
causing a compilation error.
We can alter only one of the modules.

The error is:

light.exe : error LGHT0204 : ICE30: The target file
'pbsgpqfc.res|abc.resources' is installed in
'[ProgramFilesFolder]\xxx\xxx\en\' by two different components on an LFN
system:
'_001359A8D31745CB9362973F9EE3F5BD.7C263653_7A00_4D9C_B52A_39AF1892BC49'
and 'Adapter_Co
nfig_en.BABCE01A_0CB9_4A62_B877_5E520A53D609'. This breaks component
reference counting.

Any inputs? We need to make sure that once merge module 1 writes a file,
merge module 2 overwrites this file.

Thanks,
Aditya


--
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] (no subject)

[Peter Shirtcliffe]

2 different components cannot deploy the same file to the same location. 

The best fix depends on how much control you have over the merge module
definitions, whether you've published either of them already, etc. Your
options include:
Remove one of the components entirely.
Remove one of the components and insert an exact copy of the remaining
component in its place.
Change the location of one of the files (if the component had already been
published then make a new component).
Change one of the file names, which may also require you to make a new
component.

Whatever you do to fix it, make sure the solution doesn't break the component
rules.

-Original Message-
From: Aditya Mohan [mailto:amo...@quark.com] 
Sent: 23 August 2012 12:08
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] (no subject)

Hello Guys.

We are creating an installer that uses multiple merge modules. Two of these
modules deploy a particular file at the same location, hence causing a
compilation error.
We can alter only one of the modules.

The error is:

light.exe : error LGHT0204 : ICE30: The target file
'pbsgpqfc.res|abc.resources' is installed in
'[ProgramFilesFolder]\xxx\xxx\en\' by two different components on an LFN
system:
'_001359A8D31745CB9362973F9EE3F5BD.7C263653_7A00_4D9C_B52A_39AF1892BC49'
and 'Adapter_Co
nfig_en.BABCE01A_0CB9_4A62_B877_5E520A53D609'. This breaks component
reference counting.

Any inputs? We need to make sure that once merge module 1 writes a file,
merge module 2 overwrites this file.

Thanks,
Aditya

-
-
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
SDL PLC confidential, all rights reserved.
If you are not the intended recipient of this mail SDL requests and requires 
that you delete it without acting upon or copying any of its contents, and we 
further request that you advise us.
SDL PLC is a public limited company registered in England and Wales.  
Registered number: 02675207.
Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6 7DY, 
UK.


--
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] Burn: .NET 3.5 on Windows 2008 R2

[Neil Sleightholm]

Does anyone know how you could use burn to install .NET 3.5 on Windows 2008 R2 
(and Windows 8)?

I know you need to use powershell like this: "powershell.exe Import-Module 
ServerManager ; Add-WindowsFeature as-net-framework" but can't see how I could 
do that with burn. I did think I could copy the powershell.exe and use 
ExePackage to run it but that didn't feel right.

Neil

Neil Sleightholm
X2 Systems Limited
n...@x2systems.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: .NET 3.5 on Windows 2008 R2

[Peter Shirtcliffe]

DISM has been mentioned on here before
http://technet.microsoft.com/en-us/library/dd744256%28v=ws.10%29.aspx
It might be worth searching back through the mailing list.

-Original Message-
From: Neil Sleightholm [mailto:n...@x2systems.com] 
Sent: 23 August 2012 12:39
To: General toolset. (wix-users@lists.sourceforge.net)
Subject: [WiX-users] Burn: .NET 3.5 on Windows 2008 R2

Does anyone know how you could use burn to install .NET 3.5 on Windows 2008
R2 (and Windows 8)?

I know you need to use powershell like this: "powershell.exe Import-Module
ServerManager ; Add-WindowsFeature as-net-framework" but can't see how I
could do that with burn. I did think I could copy the powershell.exe and use
ExePackage to run it but that didn't feel right.

Neil

Neil Sleightholm
X2 Systems Limited
n...@x2systems.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
SDL PLC confidential, all rights reserved.
If you are not the intended recipient of this mail SDL requests and requires 
that you delete it without acting upon or copying any of its contents, and we 
further request that you advise us.
SDL PLC is a public limited company registered in England and Wales.  
Registered number: 02675207.
Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6 7DY, 
UK.


--
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 custom managed UI not starting

[Adkins, Christopher]

Hi,

I have created the bootstrapper in such a way that all the files should be 
included in the package itself (meaning I have set Compressed="yes" on 
everything). I will try getting some more information through ProcMon, but on 
first glance it isn't telling me much.

Best regards,
Christopher Adkins

-Original Message-
From: Henning Krause [mailto:m...@henningkrause.eu] 
Sent: Donnerstag, 23. August 2012 13:16
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Burn custom managed UI not starting

Hi,

0x80070002 means file not found. Make sure you have your file references in the 
bundle correct. You can also use Sysinternals ProcMon to see where the bundle 
tries to locate your bootstrapper.

Kind regards,
Henning

> -Original Message-
> From: Adkins, Christopher [mailto:christopher.adk...@docuware.com]
> Sent: Donnerstag, 23. August 2012 13:04
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Burn custom managed UI not starting
>
> Sorry, I forgot to mention that I also included that. I am not sure 
> what else I can try and sadly I haven't found any information about 
> that error number either.
>
> Best regards,
> Christopher Adkins
> Manager Research and Development
>
> -Original Message-
> From: Christoffel le Roux [mailto:christoffe...@tech.flowcentric.com]
> Sent: Donnerstag, 23. August 2012 12:41
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Burn custom managed UI not starting
>
> Hi, I think you mabe need the following in your Assembly.cs
>
> [assembly: BootstrapperApplication(typeof(Bootstrap))]
>
> Kind regards,
> Christoffel le Roux
> Software Development Engineer
>
>
>
> Finalist: 2011 Microsoft Customer Experience Partner of Year 
> www.flowcentric.com | Email: christoffe...@flowcentric.com| Mobile: 
> +27
> 23733 752 | MSN: christoffler...@hotmail.com
>
>
> FlowCentric UK/Europe
> SoanePoint, 6-8 Market Place
> Reading, Berkshire, RG1 2EG
> Tel: +44(0) 1189 255 890
> FlowCentric Africa/Asia
> Fountain Square, 78 Kalkoen Street
> Monument Park, 0181
> Tel: +27 (0)12 347 4488
> FlowCentric Australia/Pacific
> Level 18, 333 Ann Street
> Brisbane, Qld 4000
> Tel: +61(0)7 3232 1277
>
> This information is intended only for the person or entity to which it 
> is addressed and may contain private, confidential, proprietary and/or 
> privileged material and may be subject to confidentiality agreements. 
> Any review, retransmission, dissemination, or any other use of or 
> taking of any action in reliance upon this information, by persons or 
> entities other than the intended recipient, is prohibited. If you 
> received this in error, please contact the sender and delete the 
> material from all storage media. FlowCentric is neither liable for 
> proper, complete transmission of the information contained in this 
> communication, any delay in its receipt or that the mail is virus-free.
>
>
>
>
>
> -Original Message-
> From: Adkins, Christopher [mailto:christopher.adk...@docuware.com]
> Sent: Thursday, August 23, 2012 12:11 PM
> To: General discussion for Windows Installer XML toolset. (wix-
> us...@lists.sourceforge.net)
> Subject: [WiX-users] Burn custom managed UI not starting
>
> Hi everyone,
>
> I am trying to get a custom burn UI working, but I can't even get it 
> to start. I have looked at the WiXUX project as an example, but I am 
> stuck on what I am doing wrong. The log tells me:
>
> [0428:0BC8][2012-08-23T12:04:17]: Burn v3.6.2928.0, Windows v6.1 
> (Build 7600: Service Pack 0), path:
> C:\Users\Administrator\Desktop\WebSetup.exe, cmdline: 
> '-burn.unelevated BurnPipe.{6CBBF06B-E4A0-46FA-9AAA-7375658D17A8} 
> {E0D4EE1A-96F0- 4E5C-B8FF-38EF4623E92D} 2064'
> [0428:0BC8][2012-08-23T12:04:17]: Setting string variable 'WixBundleLog'
> to value 'C:\Temp\WebSetup.Bootstrapper_20120823120417.log'
> [0428:0BC8][2012-08-23T12:04:17]: Setting string variable 
> 'WixBundleOriginalSource' to value 
> 'C:\Users\Administrator\Desktop\WebSetup.exe'
> [0428:0BC8][2012-08-23T12:04:18]: Setting string variable 'WixBundleName'
> to value 'WebSetup.Bootstrapper'
> [0428:0BC8][2012-08-23T12:04:18]: Loading managed bootstrapper 
> application.
> [0428:0BC8][2012-08-23T12:04:18]: Error 0x80070002: Failed to create 
> the managed bootstrapper application.
> [0428:0BC8][2012-08-23T12:04:18]: Error 0x80070002: Failed to create UX.
> [0428:0BC8][2012-08-23T12:04:18]: Error 0x80070002: Failed to load UX.
> [0428:0BC8][2012-08-23T12:04:18]: Error 0x80070002: Failed while 
> running
> [0428:0BC8][2012-08-23T12:04:18]: Variable: WixBundleAction = 4
> [0428:0BC8][2012-08-23T12:04:18]: Variable: WixBundleElevated = 1
> [0428:0BC8][2012-08-23T12:04:18]: Variable: WixBundleLog = 
> C:\Temp\WebSetup.Bootstrapper_20120823120417.log
> [0428:0BC8][2012-08-23T12:04:18]: Variable: WixBundleName = 
> WebSetup.Bootstrapper
> [0428:0BC8][2012-08-23T12:04:18]: Variable: WixBundleOriginal

Re: [WiX-users] Burn: .NET 3.5 on Windows 2008 R2

[Christopher Painter]

Also be aware that the feature names for .NET differ between Server and 
Server Core.

(Microsoft never makes it easier for us... always more complicated.)


 From: "Peter Shirtcliffe" 
Sent: Thursday, August 23, 2012 6:59 AM
To: "General discussion for Windows Installer XML toolset." 

Subject: Re: [WiX-users] Burn: .NET 3.5 on Windows 2008 R2

DISM has been mentioned on here before
http://technet.microsoft.com/en-us/library/dd744256%28v=ws.10%29.aspx
It might be worth searching back through the mailing list.

-Original Message-
From: Neil Sleightholm [mailto:n...@x2systems.com] 
Sent: 23 August 2012 12:39
To: General toolset. (wix-users@lists.sourceforge.net)
Subject: [WiX-users] Burn: .NET 3.5 on Windows 2008 R2

Does anyone know how you could use burn to install .NET 3.5 on Windows 
2008
R2 (and Windows 8)?

I know you need to use powershell like this: "powershell.exe Import-Module
ServerManager ; Add-WindowsFeature as-net-framework" but can't see how I
could do that with burn. I did think I could copy the powershell.exe and 
use
ExePackage to run it but that didn't feel right.

Neil

Neil Sleightholm
X2 Systems Limited
n...@x2systems.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
SDL PLC confidential, all rights reserved.
If you are not the intended recipient of this mail SDL requests and 
requires that you delete it without acting upon or copying any of its 
contents, and we further request that you advise us.
SDL PLC is a public limited company registered in England and Wales.  
Registered number: 02675207.
Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6 
7DY, UK.


--
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] Files to install in a location other than INSTALLDIR

[sudriptan]

A big thanks to Rob and Peter. It worked. You saved my day.
 
 
 
Thanks.
Sudripta.
 
 
 
-Original Message-
From: "Rob Mensching" 
Sent: Wednesday, 22 August, 2012 6:00pm
To: "General discussion for Windows Installer XML toolset." 

Subject: Re: [WiX-users] Files to install in a location other than INSTALLDIR



The error is about the Component with only the FileShare elements. Add a
CreateFolder element there.

On Wed, Aug 22, 2012 at 4:42 AM,  wrote:

>
> I will always be installing a file in that location. You can see that the
> two files 'abc.txt' and 'efg.txt' gets installed in that location. I have
> even tried putting it like this:
>
> 
>
> 
>
> 
>
> 
>  
>  
>  
>  
>  
>
>  Guid='AD3F1A3E-393C-4A97-93B8-323A8378F3B0'>
>  
>   GenericRead='yes' Read='yes' />
>  
>  
>
>  
>
> 
>
>
> But, still it doesn't help. No matter what I do I am unable to get rid of
> the link error.
>
>
> Thanks.
>
>
>
> -Original Message-
> From: "Peter Shirtcliffe" 
> Sent: Wednesday, 22 August, 2012 2:44pm
> To: "Sudripta Nandy" , "General discussion
> for Windows Installer XML toolset." 
> Subject: RE: [WiX-users] Files to install in a location other than
> INSTALLDIR
>
>
>
> Normally directories are created automatically when a file is installed
> into
> them. For some reason, the ICE checker thinks you might not install a file
> into that location.I'm not sure how intelligent it is at calculating when
> this can happen. If you are happy that there are valid situations where
> files
> might not be installed there, just add
> 
> into your MyCompShareNewLoc component. That ensures that the directory will
> always be created.
>
> -Original Message-
> From: Sudripta Nandy [mailto:sudrip...@sarangsoft.co.in]
> Sent: 22 August 2012 11:06
> To: WIX
> Subject: [WiX-users] Files to install in a location other than INSTALLDIR
>
> Hi,
>
> In my setup, I want to install 2 files say 'abc.txt' and 'efg.txt' in a
> separate location other than the default install location (INSTALLDIR).
> This
> separate location is also user-specified and I am storing the path in a
> property called 'NEWLOC1'. I also need to do a 'FileShare' of this location
> in read-mode. All other files will be installed in the default install
> location (INSTALLDIR) which also is user-specified. My main problem is
> that I
> don't know how to install these two files in the separate location
> ([NEWLOC1]) other than INSTALLDIR.
>
> I am using the following script to create the separate location and share
> it:
>
> 
>
> 
>   Guid='AD3F1A3E-393C-4A97-93B8-323A8378F3B0'>
>  
>   GenericRead='yes' Read='yes' />
>  
>  
> 
>
> In another fragment file:
>
> 
>  
>  
>  
>  
>  
>  
> 
>
>
> The problem is that I am getting a 'light' link error:
>
> error LGHT0204: ICE18: KeyPath for Component: 'MyCompShareNewLoc' is
> Directory: 'NEWLOC1'. The Directory/Component pair must be listed in the
> CreateFolders table.
>
>
> Please help me in finding a solution to my problem.
>
>
> Thanks.
> With Regards,
> // Sudripta.
>
>
>
>
>
>
>
>
> Thanking You,
> With Regards,
>
> // Sudripta Nandy
> S.D.E (Systems Programming),
>
>  SARANGSoft (India) Pvt. Ltd.
>
> Kolkata, India.
> Phone: +91 33 4008 9813.   Extn: 24
> Visit: http://www.sarangsoft.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
> SDL PLC confidential, all rights reserved.
> If you are not the intended recipient of this mail SDL requests and
> requires that you delete it without acting upon or copying any of its
> contents, and we further request that you advise us.
> SDL PLC is a public limited company registered in England and Wales.
>  Registered number: 02675207.
> Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6
> 7DY, UK.
>
>
> --
> 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 Se

Re: [WiX-users] Burn: .NET 3.5 on Windows 2008 R2

[Neil Sleightholm]

I think that still suffers the same issue, you need to run "ocsetup NetFx3" and 
burn doesn't (and probably shouldn't) allow you to run arbitrary applications. 
I think I'll need to write a powershell or ocsetup wrapper that I launch with 
ExePackage.

Neil

-Original Message-
From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] 
Sent: 23 August 2012 12:56 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Burn: .NET 3.5 on Windows 2008 R2

DISM has been mentioned on here before
http://technet.microsoft.com/en-us/library/dd744256%28v=ws.10%29.aspx
It might be worth searching back through the mailing list.

-Original Message-
From: Neil Sleightholm [mailto:n...@x2systems.com]
Sent: 23 August 2012 12:39
To: General toolset. (wix-users@lists.sourceforge.net)
Subject: [WiX-users] Burn: .NET 3.5 on Windows 2008 R2

Does anyone know how you could use burn to install .NET 3.5 on Windows 2008
R2 (and Windows 8)?

I know you need to use powershell like this: "powershell.exe Import-Module 
ServerManager ; Add-WindowsFeature as-net-framework" but can't see how I could 
do that with burn. I did think I could copy the powershell.exe and use 
ExePackage to run it but that didn't feel right.

Neil

Neil Sleightholm
X2 Systems Limited
n...@x2systems.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
SDL PLC confidential, all rights reserved.
If you are not the intended recipient of this mail SDL requests and requires 
that you delete it without acting upon or copying any of its contents, and we 
further request that you advise us.
SDL PLC is a public limited company registered in England and Wales.  
Registered number: 02675207.
Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6 7DY, 
UK.


--
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] Making my own Dialog set

[Natalie Carr]

Hi, Can anyone help me I'm getting errors and my installation is ending
prematurely.

Here are the log files:

Action start 11:06:04: InstallInitialize.
MSI (s) (00:90) [11:06:04:186]: Note: 1: 2205 2:  3: Component 
Action ended 11:06:04: InstallInitialize. Return value 3.
Action ended 11:06:04: INSTALL. Return value 3.
Then on down the log is:

Action ended 11:06:04: ExecuteAction. Return value 3.
MSI (c) (00:A4) [11:06:04:233]: Doing action: FatalError
MSI (c) (00:A4) [11:06:04:233]: Note: 1: 2205 2:  3: ActionText 
Action 11:06:04: FatalError. 
Action start 11:06:04: FatalError.
Action 11:06:04: FatalError. Dialog created
MSI (c) (00:C8) [11:06:04:250]: Note: 1: 2731 2: 0 
Action ended 11:06:31: FatalError. Return value 2.
Action ended 11:06:31: INSTALL. Return value 3.

Action 12:48:30: LicenseAgreementDlg. Dialog created
MSI (c) (08:6C) [12:48:31:760]: PROPERTY CHANGE: Adding LicenseAccepted
property. Itsvalue is '1'.
MSI (c) (08:6C) [12:48:32:246]: Note: 1: 2205 2:  3: Error 
MSI (c) (08:6C) [12:48:32:246]: Note: 1: 2228 2:  3: Error 4: SELECT
`Message` FROM   `Error` WHERE `Error` = 2898 
Info 2898.For Font_Normal__UL textstyle, the system created a 'Tahoma' font,
in 0 character set, of 13 pixels height.

Thanks

-Original Message-
From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] 
Sent: 22 August 2012 10:20
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Making my own Dialog set

Have you seen Neil's guide ?
http://neilsleightholm.blogspot.co.uk/2008/08/customised-uis-for-wix.html


-Original Message-
From: Natalie Carr [mailto:natalie.c...@measuresoft.com]
Sent: 22 August 2012 10:11
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Making my own Dialog set

Hi,

 

Need some advice. I need to edit all the error dialogs etc. but when I do I
get errors of duplicate symbols, etc. I know this is a very meticulous job
so wondering would I be safer making my own complete set of dialogs starting
from scratch or is this a crazy idea?  

 

Kind Regards,

 

Natalie Carr

 


-
-
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
SDL PLC confidential, all rights reserved.
If you are not the intended recipient of this mail SDL requests and requires
that you delete it without acting upon or copying any of its contents, and
we further request that you advise us.
SDL PLC is a public limited company registered in England and Wales.
Registered number: 02675207.
Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6
7DY, UK.



--
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] UnistallString is not written in Software\Microsoft\Windows\CurrentVersion\Uninstall\ registry key

[Alec Swan]

We use UninstallString to run the uninstaller when the product is
updated in place.

So, when the user runs our installer the installer looks for
UninstallString reg key and if found the installer asks if user wants
to wipe out previous product version's data or try to preserve it and
then runs the uninstaller passing user's answer as a command-line
parameter.

Are we doing this wrong? How else can we find the path to the
uninstaller of the product version installed on user's machine?

Thanks,

Alec

On Thu, Aug 23, 2012 at 3:17 AM, Peter Shirtcliffe  wrote:
> Windows Installer itself writes the value.
> http://msdn.microsoft.com/en-us/library/aa372105%28v=VS.85%29.aspx
> However, the uninstall string is not used by Windows Installer so does it
> matter that it wasn't written ?
>
> -Original Message-
> From: Alec Swan [mailto:alecs...@gmail.com]
> Sent: 23 August 2012 00:23
> To: General discussion for Windows Installer XML toolset.
> Subject: [WiX-users] UnistallString is not written in
> Software\Microsoft\Windows\CurrentVersion\Uninstall\ registry key
>
> Hello,
>
> I am trying to track down why our installer generated using Wix 3.0 stopped
> writing the UninstallString value in
> Software\Microsoft\Windows\CurrentVersion\Uninstall\ registry key. At some
> point we must have changed some code that broke this behavior.
>
> Where should I start troubleshooting this? Which Wix action writes this
> registry key?
>
> Thanks,
>
> Alec
>
> -
> -
> 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
> SDL PLC confidential, all rights reserved.
> If you are not the intended recipient of this mail SDL requests and requires 
> that you delete it without acting upon or copying any of its contents, and we 
> further request that you advise us.
> SDL PLC is a public limited company registered in England and Wales.  
> Registered number: 02675207.
> Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6 
> 7DY, UK.
>
>
> --
> 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

[WiX-users] Burn - InstallAnywhere ExePackage

[jhennessey]

I was wondering if anyone out there has had the unfortunate task of trying to
bootstrap an InstallAnywhere package?

I ask because apparently to uninstall these types of packages you need to
launch an "uninstall.exe" file that gets installed by the setup executable.
That being the case it appears burn won't be able to handle removal of these
natively (because it knows nothing about the "uninstall.exe" and you can't
tell it to launch an arbitrary executable).

I really can't believe there is no way to launch an uninstall from the
original install package (please let me know if I'm wrong here). Does anyone
know a hack to get this to work or have any other advice on how to deal with
InstallAnywhere?



--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-InstallAnywhere-ExePackage-tp7580040.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] crc error on wix 3.7 aditional downloads

[Rob Mensching]

wix64.proj can only be called after some of the previous parts of the build
are built. Take a look at wix.proj in the root of the project. You'll see
the overall order.

Still trying to decide how best to create all the cross dependencies
between all the various projects.

On Thu, Aug 23, 2012 at 2:21 AM, rowbot  wrote:

> Thanks, however if I 'msbuild wix64.proj', I get errors as follows:
>
> LINK : fatal error LNK1104: cannot open file 'wcautil_2010.lib'
>
> and then various errors on
> "C:\wix3.7.821.0-sources\build\debug\x86\GenerateWixInclude.exe" which
> doesn't exist...
>
> please advise,
>
>
>
>
> --
> View this message in context:
> http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/crc-error-on-wix-3-7-aditional-downloads-tp7579981p7580020.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] FW: WiX using with MSBuild can't reference other project: error CNDL0150: Undefined preprocessor variable

[Rob Mensching]

It's probably something unique about the .sqlproj that prevents the
variables from flowing across the project references. I've never crated a
..sqlproj. How do you do that?

On Wed, Aug 22, 2012 at 6:17 PM, Castro, Edwin G. (Hillsboro) <
edwin.cas...@fiserv.com> wrote:

> I'm building the .sln in both cases. It works in Visual Studio but fails
> in the command line.
>
> I tried adding the
> false to my .wixproj
> but the behavior didn't change. :-(
>
> I can build the .sqlproj just fine from the command line (either by itself
> or as part of the .sln).
>
> Edwin G. Castro
> Software Developer - Staff
> Digital Channels
> Fiserv
> Office: 503-746-0643
> Fax: 503-617-0291
> www.fiserv.com
> Please consider the environment before printing this e-mail
>
>
> > -Original Message-
> > From: Rob Mensching [mailto:r...@robmensching.com]
> > Sent: Wednesday, August 22, 2012 4:30 PM
> > To: General discussion for Windows Installer XML toolset.
> > Subject: Re: [WiX-users] FW: WiX using with MSBuild can't reference other
> > project: error CNDL0150: Undefined preprocessor variable
> >
> > What if you add
> >
> >   
> > false
> >   
> > To your .wixproj?  I expect you're hitting an interplay between
> solutions and
> > projects. That MSBuild property disables Visual Studio from creating
> magical
> > properties only available when you build the .sln file. If that is set
> and the
> > build fails then my hypothesis is correct and .sqlproj variables are
> dependent
> > on solutions today the way .vcproj files were in the past.
> >
> >
> > On Wed, Aug 22, 2012 at 1:16 PM, Edwin G. Castro
> > wrote:
> >
> > > Ruslan Albu  kurtosys.com> writes:
> > >
> > > >
> > > > But it doesn't work when I build it using MSBuild task. In my build
> > > > definition I use the following:
> > > >
> > > >  > Condition="'$(CreateSetup)'=='true'"
> > > > Properties
> > > > ="MsiInstallVersion=$(Major).$(Minor).$(Build).$(Revision);AutoBuild
> > > > =Tru
> > > > e"/>
> > > >
> > > > I'm getting this error when using MSBuild:
> > > >
> > > > Product.wxs(361): error CNDL0150: Undefined preprocessor variable
> > > > '$(var.InstallDataBase.TargetDir)'.
> > > >
> > > > I checked the build outputs from both VS and MSBuild and the
> > > > difference is that when building in MSBuild the candle.exe doesn't
> > > > have the properties for the library project (for instance
> > > > -dLibraryProjectName.ProjectDir, etc.).
> > > >
> > >
> > > I'm running into this same problem.
> > >
> > > I have a WiX project with a reference to a .sqlproj. When I build the
> > > solution the WiX project builds as expected but when I build it on the
> > > command line I get error CNDL0150: Undefined preprocessor variable
> > > similar to above.
> > >
> > > Similarly, when I checked the output for Visual Studio and compared it
> > > to the output from MSBuild I noticed that the project preprocessor
> > > variables are not getting defined in MSBuild.
> > >
> > > I see in wix2010.targets that the
> > > CreateProjectReferenceDefineConstants
> > > task is
> > > responsible for setting the ProjectReferenceDefineConstants property.
> > > I can also see that the CreateProjectReferenceDefineConstants task
> > > uses
> > > @(_ResolvedProjectReferencePaths) as ProjectReferencePaths.
> > >
> > > My guess is that the wix2010.targets is failing to resolve my project
> > > dependency on the command line but it succeeds in Visual Studio. I
> > > can't figure out why the difference occurs.
> > >
> > > Has anybody else experienced this? If so, how did you resolve it?
> > >
> > > --
> > > Edwin G. Castro
> > >
> > >
> > >
> > >
> > > --
> > > 
> > > 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] Burn: .NET 3.5 on Windows 2008 R2

[Rob Mensching]

There is a feature request open to support turning on Windows "roles and
features". It's obviously not implemented yet. 

On Thu, Aug 23, 2012 at 5:52 AM, Neil Sleightholm wrote:

> I think that still suffers the same issue, you need to run "ocsetup
> NetFx3" and burn doesn't (and probably shouldn't) allow you to run
> arbitrary applications. I think I'll need to write a powershell or ocsetup
> wrapper that I launch with ExePackage.
>
> Neil
>
> -Original Message-
> From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com]
> Sent: 23 August 2012 12:56 PM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Burn: .NET 3.5 on Windows 2008 R2
>
> DISM has been mentioned on here before
> http://technet.microsoft.com/en-us/library/dd744256%28v=ws.10%29.aspx
> It might be worth searching back through the mailing list.
>
> -Original Message-
> From: Neil Sleightholm [mailto:n...@x2systems.com]
> Sent: 23 August 2012 12:39
> To: General toolset. (wix-users@lists.sourceforge.net)
> Subject: [WiX-users] Burn: .NET 3.5 on Windows 2008 R2
>
> Does anyone know how you could use burn to install .NET 3.5 on Windows 2008
> R2 (and Windows 8)?
>
> I know you need to use powershell like this: "powershell.exe Import-Module
> ServerManager ; Add-WindowsFeature as-net-framework" but can't see how I
> could do that with burn. I did think I could copy the powershell.exe and
> use ExePackage to run it but that didn't feel right.
>
> Neil
>
> Neil Sleightholm
> X2 Systems Limited
> n...@x2systems.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
> SDL PLC confidential, all rights reserved.
> If you are not the intended recipient of this mail SDL requests and
> requires that you delete it without acting upon or copying any of its
> contents, and we further request that you advise us.
> SDL PLC is a public limited company registered in England and Wales.
>  Registered number: 02675207.
> Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6
> 7DY, UK.
>
>
>
> --
> 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] Burn custom managed UI not starting

[Rob Mensching]

Just guessing but the ".dll" below in your BootstrapperCore.config could be
a problem:


 


On Thu, Aug 23, 2012 at 4:59 AM, Adkins, Christopher <
christopher.adk...@docuware.com> wrote:

> Hi,
>
> I have created the bootstrapper in such a way that all the files should be
> included in the package itself (meaning I have set Compressed="yes" on
> everything). I will try getting some more information through ProcMon, but
> on first glance it isn't telling me much.
>
> Best regards,
> Christopher Adkins
>
> -Original Message-
> From: Henning Krause [mailto:m...@henningkrause.eu]
> Sent: Donnerstag, 23. August 2012 13:16
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Burn custom managed UI not starting
>
> Hi,
>
> 0x80070002 means file not found. Make sure you have your file references
> in the bundle correct. You can also use Sysinternals ProcMon to see where
> the bundle tries to locate your bootstrapper.
>
> Kind regards,
> Henning
>
> > -Original Message-
> > From: Adkins, Christopher [mailto:christopher.adk...@docuware.com]
> > Sent: Donnerstag, 23. August 2012 13:04
> > To: General discussion for Windows Installer XML toolset.
> > Subject: Re: [WiX-users] Burn custom managed UI not starting
> >
> > Sorry, I forgot to mention that I also included that. I am not sure
> > what else I can try and sadly I haven't found any information about
> > that error number either.
> >
> > Best regards,
> > Christopher Adkins
> > Manager Research and Development
> >
> > -Original Message-
> > From: Christoffel le Roux [mailto:christoffe...@tech.flowcentric.com]
> > Sent: Donnerstag, 23. August 2012 12:41
> > To: General discussion for Windows Installer XML toolset.
> > Subject: Re: [WiX-users] Burn custom managed UI not starting
> >
> > Hi, I think you mabe need the following in your Assembly.cs
> >
> > [assembly: BootstrapperApplication(typeof(Bootstrap))]
> >
> > Kind regards,
> > Christoffel le Roux
> > Software Development Engineer
> >
> >
> >
> > Finalist: 2011 Microsoft Customer Experience Partner of Year
> > www.flowcentric.com | Email: christoffe...@flowcentric.com| Mobile:
> > +27
> > 23733 752 | MSN: christoffler...@hotmail.com
> >
> >
> > FlowCentric UK/Europe
> > SoanePoint, 6-8 Market Place
> > Reading, Berkshire, RG1 2EG
> > Tel: +44(0) 1189 255 890
> > FlowCentric Africa/Asia
> > Fountain Square, 78 Kalkoen Street
> > Monument Park, 0181
> > Tel: +27 (0)12 347 4488
> > FlowCentric Australia/Pacific
> > Level 18, 333 Ann Street
> > Brisbane, Qld 4000
> > Tel: +61(0)7 3232 1277
> >
> > This information is intended only for the person or entity to which it
> > is addressed and may contain private, confidential, proprietary and/or
> > privileged material and may be subject to confidentiality agreements.
> > Any review, retransmission, dissemination, or any other use of or
> > taking of any action in reliance upon this information, by persons or
> > entities other than the intended recipient, is prohibited. If you
> > received this in error, please contact the sender and delete the
> > material from all storage media. FlowCentric is neither liable for
> > proper, complete transmission of the information contained in this
> communication, any delay in its receipt or that the mail is virus-free.
> >
> >
> >
> >
> >
> > -Original Message-
> > From: Adkins, Christopher [mailto:christopher.adk...@docuware.com]
> > Sent: Thursday, August 23, 2012 12:11 PM
> > To: General discussion for Windows Installer XML toolset. (wix-
> > us...@lists.sourceforge.net)
> > Subject: [WiX-users] Burn custom managed UI not starting
> >
> > Hi everyone,
> >
> > I am trying to get a custom burn UI working, but I can't even get it
> > to start. I have looked at the WiXUX project as an example, but I am
> > stuck on what I am doing wrong. The log tells me:
> >
> > [0428:0BC8][2012-08-23T12:04:17]: Burn v3.6.2928.0, Windows v6.1
> > (Build 7600: Service Pack 0), path:
> > C:\Users\Administrator\Desktop\WebSetup.exe, cmdline:
> > '-burn.unelevated BurnPipe.{6CBBF06B-E4A0-46FA-9AAA-7375658D17A8}
> > {E0D4EE1A-96F0- 4E5C-B8FF-38EF4623E92D} 2064'
> > [0428:0BC8][2012-08-23T12:04:17]: Setting string variable 'WixBundleLog'
> > to value 'C:\Temp\WebSetup.Bootstrapper_20120823120417.log'
> > [0428:0BC8][2012-08-23T12:04:17]: Setting string variable
> > 'WixBundleOriginalSource' to value
> > 'C:\Users\Administrator\Desktop\WebSetup.exe'
> > [0428:0BC8][2012-08-23T12:04:18]: Setting string variable 'WixBundleName'
> > to value 'WebSetup.Bootstrapper'
> > [0428:0BC8][2012-08-23T12:04:18]: Loading managed bootstrapper
> > application.
> > [0428:0BC8][2012-08-23T12:04:18]: Error 0x80070002: Failed to create
> > the managed bootstrapper application.
> > [0428:0BC8][2012-08-23T12:04:18]: Error 0x80070002: Failed to create UX.
> > [0428:0BC8][2012-08-23T12:04:18]: Error 0x80070002: Failed to load UX.
> > [0428:0BC8][2012-08-23T12:04:18]: Error 0x80070002: Failed whil

Re: [WiX-users] Burn - InstallAnywhere ExePackage

[Rob Mensching]

Yeah, sadly we totally missed this pattern of exe installers in the first
version of Burn.

On Thu, Aug 23, 2012 at 7:41 AM, jhennessey wrote:

> I was wondering if anyone out there has had the unfortunate task of trying
> to
> bootstrap an InstallAnywhere package?
>
> I ask because apparently to uninstall these types of packages you need to
> launch an "uninstall.exe" file that gets installed by the setup executable.
> That being the case it appears burn won't be able to handle removal of
> these
> natively (because it knows nothing about the "uninstall.exe" and you can't
> tell it to launch an arbitrary executable).
>
> I really can't believe there is no way to launch an uninstall from the
> original install package (please let me know if I'm wrong here). Does
> anyone
> know a hack to get this to work or have any other advice on how to deal
> with
> InstallAnywhere?
>
>
>
> --
> View this message in context:
> http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-InstallAnywhere-ExePackage-tp7580040.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] How to create a feature tree with burn?

[Rob Mensching]

It is poorly documented but it does exist and exists for this very sort of
reason. 

The file is always right next to your BA.dll. Unfortunately, the WixBA
doesn't need any information from the file so I can't point to it as an
example how to load the file.
Just get the executing path of your BA.dll then load the file named
BootstrapperApplicationData.xml.
On Thu, Aug 23, 2012 at 2:18 AM, Daniel Bruce wrote:

> I'm trying to accomplish something similar with my own Bootstrapper
> Application, and would like to find this XML file. What is the suggested
> way of locating this file? I'm unsure how to locate my BA DLL at runtime
> without resorting to magic strings.
>
> In addition, is there any documentation at all about this file, and its
> format? Is it a supported way of accessing bundle information, or is it
> just a magic file? I can't seem to locate anything about it apart from
> scattered mailing list posts.
>
> > -Original Message-
> > From: Rob Mensching [mailto:r...@robmensching.com]
> > Sent: 20. august 2012 23:37
> > To: General discussion for Windows Installer XML toolset.
> > Subject: Re: [WiX-users] How to create a feature tree with burn?
> >
> > BootstrapperApplicationData.xml is provided with your BA. It's right next
> > to the DLL at runtime.  You won't see it until the BA is running.
> >
> > On Mon, Aug 20, 2012 at 10:34 AM, CristianI  wrote:
> >
> > > It's good to hear, that these things are possible =) But where do I
> > > find the BootstrapperApplicationData.xml? I read that it should be
> > > extracted to the temporary folder, but it's not working for me.
> > > Do
> > > I have to do something special, am I missing something or is it enough
> > > compile it the usually way with candle and light?
> > >
> > > Thanks again very much for the help; I'm trying to get as much info
> > > about
> > > OnPlanPackageBegin() as I can find in the next hours =)
> > >
> > >
> > >
> > > --
> > > View this message in context:
> > > http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/How-
> > to-c
> > > reate-a-feature-tree-with-burn-tp7579948p7579957.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
> >
> > ___
> > ___
> > This email has been scanned by the Symantec Email Security.cloud
> > service.
> > For more information please visit http://www.symanteccloud.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/lis

Re: [WiX-users] Burn - InstallAnywhere ExePackage

[jhennessey]

Yeah I have never even been exposed to this type of installer until very
recently. Should I file a bug for 3.7 to track this?



--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-InstallAnywhere-ExePackage-tp7580040p7580047.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] UnistallString is not written in Software\Microsoft\Windows\CurrentVersion\Uninstall\ registry key

[Peter Shirtcliffe]

Sounds like an strange design. Normally you'd make a major upgrade to remove
the old version automatically and replace it with the new one. Any data that
needs preserving is probably configuration or user data and should be handled
by the application rather than the installer. The normal way to uninstall is
via Add/Remove Programs (Programs And Features) but you can make a shortcut
as shown in
http://robmensching.com/blog/posts/2007/4/27/How-to-create-an-uninstall-short
cut-and-pass-all-the

Have you set ARPNOREMOVE ? That would suppress the uninstall string.

-Original Message-
From: Alec Swan [mailto:alecs...@gmail.com] 
Sent: 23 August 2012 15:22
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] UnistallString is not written in
Software\Microsoft\Windows\CurrentVersion\Uninstall\ registry key

We use UninstallString to run the uninstaller when the product is updated in
place.

So, when the user runs our installer the installer looks for UninstallString
reg key and if found the installer asks if user wants to wipe out previous
product version's data or try to preserve it and then runs the uninstaller
passing user's answer as a command-line parameter.

Are we doing this wrong? How else can we find the path to the uninstaller of
the product version installed on user's machine?

Thanks,

Alec

On Thu, Aug 23, 2012 at 3:17 AM, Peter Shirtcliffe 
wrote:
> Windows Installer itself writes the value.
> http://msdn.microsoft.com/en-us/library/aa372105%28v=VS.85%29.aspx
> However, the uninstall string is not used by Windows Installer so does 
> it matter that it wasn't written ?
>
> -Original Message-
> From: Alec Swan [mailto:alecs...@gmail.com]
> Sent: 23 August 2012 00:23
> To: General discussion for Windows Installer XML toolset.
> Subject: [WiX-users] UnistallString is not written in 
> Software\Microsoft\Windows\CurrentVersion\Uninstall\ registry key
>
> Hello,
>
> I am trying to track down why our installer generated using Wix 3.0 
> stopped writing the UninstallString value in 
> Software\Microsoft\Windows\CurrentVersion\Uninstall\ registry key. At 
> some point we must have changed some code that broke this behavior.
>
> Where should I start troubleshooting this? Which Wix action writes 
> this registry key?
>
> Thanks,
>
> Alec
>
> --
> ---
> -
> 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
> SDL PLC confidential, all rights reserved.
> If you are not the intended recipient of this mail SDL requests and
requires that you delete it without acting upon or copying any of its
contents, and we further request that you advise us.
> SDL PLC is a public limited company registered in England and Wales.
Registered number: 02675207.
> Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6
7DY, UK.
>
>
> --
> 
> 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

--
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/li

Re: [WiX-users] Burn - InstallAnywhere ExePackage

[Hoover, Jacob]

I really don't like this approach, but in theory could you not create a Stub 
EXE that would take an install or uninstall parameter and would have to have 
the knowledge of the InstallAnywhere package? You could then bundle this stub 
with your InstallAnywhere package. 

-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com] 
Sent: Thursday, August 23, 2012 9:53 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Burn - InstallAnywhere ExePackage

Yeah, sadly we totally missed this pattern of exe installers in the first 
version of Burn.

On Thu, Aug 23, 2012 at 7:41 AM, jhennessey wrote:

> I was wondering if anyone out there has had the unfortunate task of 
> trying to bootstrap an InstallAnywhere package?
>
> I ask because apparently to uninstall these types of packages you need 
> to launch an "uninstall.exe" file that gets installed by the setup executable.
> That being the case it appears burn won't be able to handle removal of 
> these natively (because it knows nothing about the "uninstall.exe" and 
> you can't tell it to launch an arbitrary executable).
>
> I really can't believe there is no way to launch an uninstall from the 
> original install package (please let me know if I'm wrong here). Does 
> anyone know a hack to get this to work or have any other advice on how 
> to deal with InstallAnywhere?
>
>
>
> --
> View this message in context:
> http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-Ins
> tallAnywhere-ExePackage-tp7580040.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

--
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 - InstallAnywhere ExePackage

[jhennessey]

Good idea, I'm going to look into this approach and post back if I'm
successful...thanks for the idea!



--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-InstallAnywhere-ExePackage-tp7580040p7580050.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] UnistallString is not written in Software\Microsoft\Windows\CurrentVersion\Uninstall\ registry key

[Alec Swan]

We can still uninstall the product from Add/Remove Programs but there
is no entry for our product under
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Uninstall
reg key. Is it possible UninstallString is written in some other
registry location?

Thanks,

Alec

On Thu, Aug 23, 2012 at 9:06 AM, Peter Shirtcliffe  wrote:
> Sounds like an strange design. Normally you'd make a major upgrade to remove
> the old version automatically and replace it with the new one. Any data that
> needs preserving is probably configuration or user data and should be handled
> by the application rather than the installer. The normal way to uninstall is
> via Add/Remove Programs (Programs And Features) but you can make a shortcut
> as shown in
> http://robmensching.com/blog/posts/2007/4/27/How-to-create-an-uninstall-short
> cut-and-pass-all-the
>
> Have you set ARPNOREMOVE ? That would suppress the uninstall string.
>
> -Original Message-
> From: Alec Swan [mailto:alecs...@gmail.com]
> Sent: 23 August 2012 15:22
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] UnistallString is not written in
> Software\Microsoft\Windows\CurrentVersion\Uninstall\ registry key
>
> We use UninstallString to run the uninstaller when the product is updated in
> place.
>
> So, when the user runs our installer the installer looks for UninstallString
> reg key and if found the installer asks if user wants to wipe out previous
> product version's data or try to preserve it and then runs the uninstaller
> passing user's answer as a command-line parameter.
>
> Are we doing this wrong? How else can we find the path to the uninstaller of
> the product version installed on user's machine?
>
> Thanks,
>
> Alec
>
> On Thu, Aug 23, 2012 at 3:17 AM, Peter Shirtcliffe 
> wrote:
>> Windows Installer itself writes the value.
>> http://msdn.microsoft.com/en-us/library/aa372105%28v=VS.85%29.aspx
>> However, the uninstall string is not used by Windows Installer so does
>> it matter that it wasn't written ?
>>
>> -Original Message-
>> From: Alec Swan [mailto:alecs...@gmail.com]
>> Sent: 23 August 2012 00:23
>> To: General discussion for Windows Installer XML toolset.
>> Subject: [WiX-users] UnistallString is not written in
>> Software\Microsoft\Windows\CurrentVersion\Uninstall\ registry key
>>
>> Hello,
>>
>> I am trying to track down why our installer generated using Wix 3.0
>> stopped writing the UninstallString value in
>> Software\Microsoft\Windows\CurrentVersion\Uninstall\ registry key. At
>> some point we must have changed some code that broke this behavior.
>>
>> Where should I start troubleshooting this? Which Wix action writes
>> this registry key?
>>
>> Thanks,
>>
>> Alec
>>
>> --
>> ---
>> -
>> 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
>> SDL PLC confidential, all rights reserved.
>> If you are not the intended recipient of this mail SDL requests and
> requires that you delete it without acting upon or copying any of its
> contents, and we further request that you advise us.
>> SDL PLC is a public limited company registered in England and Wales.
> Registered number: 02675207.
>> Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6
> 7DY, UK.
>>
>>
>> --
>> 
>> 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] UnistallString is not written in Software\Microsoft\Windows\CurrentVersion\Uninstall\ registry key

[Alec Swan]

Actually, I just found that
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{5D6E0940-C1EB-4C60-8A36-54D6BCCF5C02}
contains an UninstallString for our product. Now I have to track down
how we ended up with a GUID in this reg key because it used to be the
name of our product.

I am new to all this and appreciate any help with this.

Thanks,

Alec

On Thu, Aug 23, 2012 at 9:27 AM, Alec Swan  wrote:
> We can still uninstall the product from Add/Remove Programs but there
> is no entry for our product under
> HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Uninstall
> reg key. Is it possible UninstallString is written in some other
> registry location?
>
> Thanks,
>
> Alec
>
> On Thu, Aug 23, 2012 at 9:06 AM, Peter Shirtcliffe  
> wrote:
>> Sounds like an strange design. Normally you'd make a major upgrade to remove
>> the old version automatically and replace it with the new one. Any data that
>> needs preserving is probably configuration or user data and should be handled
>> by the application rather than the installer. The normal way to uninstall is
>> via Add/Remove Programs (Programs And Features) but you can make a shortcut
>> as shown in
>> http://robmensching.com/blog/posts/2007/4/27/How-to-create-an-uninstall-short
>> cut-and-pass-all-the
>>
>> Have you set ARPNOREMOVE ? That would suppress the uninstall string.
>>
>> -Original Message-
>> From: Alec Swan [mailto:alecs...@gmail.com]
>> Sent: 23 August 2012 15:22
>> To: General discussion for Windows Installer XML toolset.
>> Subject: Re: [WiX-users] UnistallString is not written in
>> Software\Microsoft\Windows\CurrentVersion\Uninstall\ registry key
>>
>> We use UninstallString to run the uninstaller when the product is updated in
>> place.
>>
>> So, when the user runs our installer the installer looks for UninstallString
>> reg key and if found the installer asks if user wants to wipe out previous
>> product version's data or try to preserve it and then runs the uninstaller
>> passing user's answer as a command-line parameter.
>>
>> Are we doing this wrong? How else can we find the path to the uninstaller of
>> the product version installed on user's machine?
>>
>> Thanks,
>>
>> Alec
>>
>> On Thu, Aug 23, 2012 at 3:17 AM, Peter Shirtcliffe 
>> wrote:
>>> Windows Installer itself writes the value.
>>> http://msdn.microsoft.com/en-us/library/aa372105%28v=VS.85%29.aspx
>>> However, the uninstall string is not used by Windows Installer so does
>>> it matter that it wasn't written ?
>>>
>>> -Original Message-
>>> From: Alec Swan [mailto:alecs...@gmail.com]
>>> Sent: 23 August 2012 00:23
>>> To: General discussion for Windows Installer XML toolset.
>>> Subject: [WiX-users] UnistallString is not written in
>>> Software\Microsoft\Windows\CurrentVersion\Uninstall\ registry key
>>>
>>> Hello,
>>>
>>> I am trying to track down why our installer generated using Wix 3.0
>>> stopped writing the UninstallString value in
>>> Software\Microsoft\Windows\CurrentVersion\Uninstall\ registry key. At
>>> some point we must have changed some code that broke this behavior.
>>>
>>> Where should I start troubleshooting this? Which Wix action writes
>>> this registry key?
>>>
>>> Thanks,
>>>
>>> Alec
>>>
>>> --
>>> ---
>>> -
>>> 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
>>> SDL PLC confidential, all rights reserved.
>>> If you are not the intended recipient of this mail SDL requests and
>> requires that you delete it without acting upon or copying any of its
>> contents, and we further request that you advise us.
>>> SDL PLC is a public limited company registered in England and Wales.
>> Registered number: 02675207.
>>> Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6
>> 7DY, UK.
>>>
>>>
>>> --
>>> 
>>> 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 Secu

Re: [WiX-users] UnistallString is not written in Software\Microsoft\Windows\CurrentVersion\Uninstall\ registry key

[Peter Shirtcliffe]

An MSI installer will always have the product code GUID in the key, exactly
as you have there. Were you using InstallShield or something before ?

-Original Message-
From: Alec Swan [mailto:alecs...@gmail.com] 
Sent: 23 August 2012 16:34
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] UnistallString is not written in
Software\Microsoft\Windows\CurrentVersion\Uninstall\ registry key

Actually, I just found that
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{5D6E0
940-C1EB-4C60-8A36-54D6BCCF5C02}
contains an UninstallString for our product. Now I have to track down how we
ended up with a GUID in this reg key because it used to be the name of our
product.

I am new to all this and appreciate any help with this.

Thanks,

Alec

On Thu, Aug 23, 2012 at 9:27 AM, Alec Swan  wrote:
> We can still uninstall the product from Add/Remove Programs but there 
> is no entry for our product under 
> HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Uninstall
> reg key. Is it possible UninstallString is written in some other 
> registry location?
>
> Thanks,
>
> Alec
>
> On Thu, Aug 23, 2012 at 9:06 AM, Peter Shirtcliffe 
wrote:
>> Sounds like an strange design. Normally you'd make a major upgrade to 
>> remove the old version automatically and replace it with the new one. 
>> Any data that needs preserving is probably configuration or user data 
>> and should be handled by the application rather than the installer. 
>> The normal way to uninstall is via Add/Remove Programs (Programs And 
>> Features) but you can make a shortcut as shown in 
>> http://robmensching.com/blog/posts/2007/4/27/How-to-create-an-uninsta
>> ll-short
>> cut-and-pass-all-the
>>
>> Have you set ARPNOREMOVE ? That would suppress the uninstall string.
>>
>> -Original Message-
>> From: Alec Swan [mailto:alecs...@gmail.com]
>> Sent: 23 August 2012 15:22
>> To: General discussion for Windows Installer XML toolset.
>> Subject: Re: [WiX-users] UnistallString is not written in 
>> Software\Microsoft\Windows\CurrentVersion\Uninstall\ registry key
>>
>> We use UninstallString to run the uninstaller when the product is 
>> updated in place.
>>
>> So, when the user runs our installer the installer looks for 
>> UninstallString reg key and if found the installer asks if user wants 
>> to wipe out previous product version's data or try to preserve it and 
>> then runs the uninstaller passing user's answer as a command-line
parameter.
>>
>> Are we doing this wrong? How else can we find the path to the 
>> uninstaller of the product version installed on user's machine?
>>
>> Thanks,
>>
>> Alec
>>
>> On Thu, Aug 23, 2012 at 3:17 AM, Peter Shirtcliffe 
>> 
>> wrote:
>>> Windows Installer itself writes the value.
>>> http://msdn.microsoft.com/en-us/library/aa372105%28v=VS.85%29.aspx
>>> However, the uninstall string is not used by Windows Installer so 
>>> does it matter that it wasn't written ?
>>>
>>> -Original Message-
>>> From: Alec Swan [mailto:alecs...@gmail.com]
>>> Sent: 23 August 2012 00:23
>>> To: General discussion for Windows Installer XML toolset.
>>> Subject: [WiX-users] UnistallString is not written in 
>>> Software\Microsoft\Windows\CurrentVersion\Uninstall\ registry key
>>>
>>> Hello,
>>>
>>> I am trying to track down why our installer generated using Wix 3.0 
>>> stopped writing the UninstallString value in 
>>> Software\Microsoft\Windows\CurrentVersion\Uninstall\ registry key. 
>>> At some point we must have changed some code that broke this behavior.
>>>
>>> Where should I start troubleshooting this? Which Wix action writes 
>>> this registry key?
>>>
>>> Thanks,
>>>
>>> Alec
>>>
>>> 
>>> --
>>> ---
>>> -
>>> 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
>>> SDL PLC confidential, all rights reserved.
>>> If you are not the intended recipient of this mail SDL requests and
>> requires that you delete it without acting upon or copying any of its 
>> contents, and we further request that you advise us.
>>> SDL PLC is a public limited company registered in England and Wales.
>> Registered number: 02675207.
>>> Registered address: Globe House, Clivemont Road, Maidenhead, 
>>> Berkshire SL6
>> 7DY, UK.
>>>
>>>
>>> 
>>> --
>>> 
>>> Live Security Virtual Conference
>>> Exclusive live event will cover all the ways today's security and 
>>> threat landscape has ch

[WiX-users] [CLOSED]: UnistallString is not written in Software\Microsoft\Windows\CurrentVersion\Uninstall\ registry key

[Alec Swan]

After some internal discussions it turned out that we were looking for
UnistallString to support upgrade from our product version that used
to be installed with NullSoft to the version that is currently
installed with MSI.

I am closing this thread, sorry for the confusion.

Thanks,

Alec

On Thu, Aug 23, 2012 at 9:33 AM, Alec Swan  wrote:
> Actually, I just found that
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{5D6E0940-C1EB-4C60-8A36-54D6BCCF5C02}
> contains an UninstallString for our product. Now I have to track down
> how we ended up with a GUID in this reg key because it used to be the
> name of our product.
>
> I am new to all this and appreciate any help with this.
>
> Thanks,
>
> Alec
>
> On Thu, Aug 23, 2012 at 9:27 AM, Alec Swan  wrote:
>> We can still uninstall the product from Add/Remove Programs but there
>> is no entry for our product under
>> HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Uninstall
>> reg key. Is it possible UninstallString is written in some other
>> registry location?
>>
>> Thanks,
>>
>> Alec
>>
>> On Thu, Aug 23, 2012 at 9:06 AM, Peter Shirtcliffe  
>> wrote:
>>> Sounds like an strange design. Normally you'd make a major upgrade to remove
>>> the old version automatically and replace it with the new one. Any data that
>>> needs preserving is probably configuration or user data and should be 
>>> handled
>>> by the application rather than the installer. The normal way to uninstall is
>>> via Add/Remove Programs (Programs And Features) but you can make a shortcut
>>> as shown in
>>> http://robmensching.com/blog/posts/2007/4/27/How-to-create-an-uninstall-short
>>> cut-and-pass-all-the
>>>
>>> Have you set ARPNOREMOVE ? That would suppress the uninstall string.
>>>
>>> -Original Message-
>>> From: Alec Swan [mailto:alecs...@gmail.com]
>>> Sent: 23 August 2012 15:22
>>> To: General discussion for Windows Installer XML toolset.
>>> Subject: Re: [WiX-users] UnistallString is not written in
>>> Software\Microsoft\Windows\CurrentVersion\Uninstall\ registry key
>>>
>>> We use UninstallString to run the uninstaller when the product is updated in
>>> place.
>>>
>>> So, when the user runs our installer the installer looks for UninstallString
>>> reg key and if found the installer asks if user wants to wipe out previous
>>> product version's data or try to preserve it and then runs the uninstaller
>>> passing user's answer as a command-line parameter.
>>>
>>> Are we doing this wrong? How else can we find the path to the uninstaller of
>>> the product version installed on user's machine?
>>>
>>> Thanks,
>>>
>>> Alec
>>>
>>> On Thu, Aug 23, 2012 at 3:17 AM, Peter Shirtcliffe 
>>> wrote:
 Windows Installer itself writes the value.
 http://msdn.microsoft.com/en-us/library/aa372105%28v=VS.85%29.aspx
 However, the uninstall string is not used by Windows Installer so does
 it matter that it wasn't written ?

 -Original Message-
 From: Alec Swan [mailto:alecs...@gmail.com]
 Sent: 23 August 2012 00:23
 To: General discussion for Windows Installer XML toolset.
 Subject: [WiX-users] UnistallString is not written in
 Software\Microsoft\Windows\CurrentVersion\Uninstall\ registry key

 Hello,

 I am trying to track down why our installer generated using Wix 3.0
 stopped writing the UninstallString value in
 Software\Microsoft\Windows\CurrentVersion\Uninstall\ registry key. At
 some point we must have changed some code that broke this behavior.

 Where should I start troubleshooting this? Which Wix action writes
 this registry key?

 Thanks,

 Alec

 --
 ---
 -
 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
 SDL PLC confidential, all rights reserved.
 If you are not the intended recipient of this mail SDL requests and
>>> requires that you delete it without acting upon or copying any of its
>>> contents, and we further request that you advise us.
 SDL PLC is a public limited company registered in England and Wales.
>>> Registered number: 02675207.
 Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6
>>> 7DY, UK.


 --
 
 Live Security Virtual Conference
 Exclusive live event will cover all the ways today's security and
 threat landscape has changed and

Re: [WiX-users] UnistallString is not written in Software\Microsoft\Windows\CurrentVersion\Uninstall\ registry key

[Alec Swan]

You are spot on! We were using NullSoft product. I just closed the thread.

Thanks!

On Thu, Aug 23, 2012 at 9:55 AM, Peter Shirtcliffe  wrote:
> An MSI installer will always have the product code GUID in the key, exactly
> as you have there. Were you using InstallShield or something before ?
>
> -Original Message-
> From: Alec Swan [mailto:alecs...@gmail.com]
> Sent: 23 August 2012 16:34
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] UnistallString is not written in
> Software\Microsoft\Windows\CurrentVersion\Uninstall\ registry key
>
> Actually, I just found that
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{5D6E0
> 940-C1EB-4C60-8A36-54D6BCCF5C02}
> contains an UninstallString for our product. Now I have to track down how we
> ended up with a GUID in this reg key because it used to be the name of our
> product.
>
> I am new to all this and appreciate any help with this.
>
> Thanks,
>
> Alec
>
> On Thu, Aug 23, 2012 at 9:27 AM, Alec Swan  wrote:
>> We can still uninstall the product from Add/Remove Programs but there
>> is no entry for our product under
>> HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Uninstall
>> reg key. Is it possible UninstallString is written in some other
>> registry location?
>>
>> Thanks,
>>
>> Alec
>>
>> On Thu, Aug 23, 2012 at 9:06 AM, Peter Shirtcliffe 
> wrote:
>>> Sounds like an strange design. Normally you'd make a major upgrade to
>>> remove the old version automatically and replace it with the new one.
>>> Any data that needs preserving is probably configuration or user data
>>> and should be handled by the application rather than the installer.
>>> The normal way to uninstall is via Add/Remove Programs (Programs And
>>> Features) but you can make a shortcut as shown in
>>> http://robmensching.com/blog/posts/2007/4/27/How-to-create-an-uninsta
>>> ll-short
>>> cut-and-pass-all-the
>>>
>>> Have you set ARPNOREMOVE ? That would suppress the uninstall string.
>>>
>>> -Original Message-
>>> From: Alec Swan [mailto:alecs...@gmail.com]
>>> Sent: 23 August 2012 15:22
>>> To: General discussion for Windows Installer XML toolset.
>>> Subject: Re: [WiX-users] UnistallString is not written in
>>> Software\Microsoft\Windows\CurrentVersion\Uninstall\ registry key
>>>
>>> We use UninstallString to run the uninstaller when the product is
>>> updated in place.
>>>
>>> So, when the user runs our installer the installer looks for
>>> UninstallString reg key and if found the installer asks if user wants
>>> to wipe out previous product version's data or try to preserve it and
>>> then runs the uninstaller passing user's answer as a command-line
> parameter.
>>>
>>> Are we doing this wrong? How else can we find the path to the
>>> uninstaller of the product version installed on user's machine?
>>>
>>> Thanks,
>>>
>>> Alec
>>>
>>> On Thu, Aug 23, 2012 at 3:17 AM, Peter Shirtcliffe
>>> 
>>> wrote:
 Windows Installer itself writes the value.
 http://msdn.microsoft.com/en-us/library/aa372105%28v=VS.85%29.aspx
 However, the uninstall string is not used by Windows Installer so
 does it matter that it wasn't written ?

 -Original Message-
 From: Alec Swan [mailto:alecs...@gmail.com]
 Sent: 23 August 2012 00:23
 To: General discussion for Windows Installer XML toolset.
 Subject: [WiX-users] UnistallString is not written in
 Software\Microsoft\Windows\CurrentVersion\Uninstall\ registry key

 Hello,

 I am trying to track down why our installer generated using Wix 3.0
 stopped writing the UninstallString value in
 Software\Microsoft\Windows\CurrentVersion\Uninstall\ registry key.
 At some point we must have changed some code that broke this behavior.

 Where should I start troubleshooting this? Which Wix action writes
 this registry key?

 Thanks,

 Alec

 
 --
 ---
 -
 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
 SDL PLC confidential, all rights reserved.
 If you are not the intended recipient of this mail SDL requests and
>>> requires that you delete it without acting upon or copying any of its
>>> contents, and we further request that you advise us.
 SDL PLC is a public limited company registered in England and Wales.
>>> Registered number: 02675207.
 Registered address: Globe House, Clivemont Road, Maidenhead,
 Be

[WiX-users] Burn cancel button does not work when using an MSI

[Jeanne Dixon]

I have tried to follow the examples I have been able to find regarding Burn and 
installing an MSI as part of the chain. I have an MSI that has its 
DisplayInternalUI set to yes.

If the user cancels the MSI install, burn shows that it failed (fine) but the 
cancel button on the window no longer works. The X close button does. How do I 
get the cancel button to actually do something?

--
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] UnistallString is not written in Software\Microsoft\Windows\CurrentVersion\Uninstall\ registry key

[Rob Mensching]

I'd also recommend using the MajorUpgrade element to upgrade your MSIs.
That's the "proper" way to upgrade. 

On Thu, Aug 23, 2012 at 9:02 AM, Alec Swan  wrote:

> You are spot on! We were using NullSoft product. I just closed the thread.
>
> Thanks!
>
> On Thu, Aug 23, 2012 at 9:55 AM, Peter Shirtcliffe 
> wrote:
> > An MSI installer will always have the product code GUID in the key,
> exactly
> > as you have there. Were you using InstallShield or something before ?
> >
> > -Original Message-
> > From: Alec Swan [mailto:alecs...@gmail.com]
> > Sent: 23 August 2012 16:34
> > To: General discussion for Windows Installer XML toolset.
> > Subject: Re: [WiX-users] UnistallString is not written in
> > Software\Microsoft\Windows\CurrentVersion\Uninstall\ registry key
> >
> > Actually, I just found that
> >
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{5D6E0
> > 940-C1EB-4C60-8A36-54D6BCCF5C02}
> > contains an UninstallString for our product. Now I have to track down
> how we
> > ended up with a GUID in this reg key because it used to be the name of
> our
> > product.
> >
> > I am new to all this and appreciate any help with this.
> >
> > Thanks,
> >
> > Alec
> >
> > On Thu, Aug 23, 2012 at 9:27 AM, Alec Swan  wrote:
> >> We can still uninstall the product from Add/Remove Programs but there
> >> is no entry for our product under
> >> HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Uninstall
> >> reg key. Is it possible UninstallString is written in some other
> >> registry location?
> >>
> >> Thanks,
> >>
> >> Alec
> >>
> >> On Thu, Aug 23, 2012 at 9:06 AM, Peter Shirtcliffe <
> pshirtcli...@sdl.com>
> > wrote:
> >>> Sounds like an strange design. Normally you'd make a major upgrade to
> >>> remove the old version automatically and replace it with the new one.
> >>> Any data that needs preserving is probably configuration or user data
> >>> and should be handled by the application rather than the installer.
> >>> The normal way to uninstall is via Add/Remove Programs (Programs And
> >>> Features) but you can make a shortcut as shown in
> >>> http://robmensching.com/blog/posts/2007/4/27/How-to-create-an-uninsta
> >>> ll-short
> >>> cut-and-pass-all-the
> >>>
> >>> Have you set ARPNOREMOVE ? That would suppress the uninstall string.
> >>>
> >>> -Original Message-
> >>> From: Alec Swan [mailto:alecs...@gmail.com]
> >>> Sent: 23 August 2012 15:22
> >>> To: General discussion for Windows Installer XML toolset.
> >>> Subject: Re: [WiX-users] UnistallString is not written in
> >>> Software\Microsoft\Windows\CurrentVersion\Uninstall\ registry key
> >>>
> >>> We use UninstallString to run the uninstaller when the product is
> >>> updated in place.
> >>>
> >>> So, when the user runs our installer the installer looks for
> >>> UninstallString reg key and if found the installer asks if user wants
> >>> to wipe out previous product version's data or try to preserve it and
> >>> then runs the uninstaller passing user's answer as a command-line
> > parameter.
> >>>
> >>> Are we doing this wrong? How else can we find the path to the
> >>> uninstaller of the product version installed on user's machine?
> >>>
> >>> Thanks,
> >>>
> >>> Alec
> >>>
> >>> On Thu, Aug 23, 2012 at 3:17 AM, Peter Shirtcliffe
> >>> 
> >>> wrote:
>  Windows Installer itself writes the value.
>  http://msdn.microsoft.com/en-us/library/aa372105%28v=VS.85%29.aspx
>  However, the uninstall string is not used by Windows Installer so
>  does it matter that it wasn't written ?
> 
>  -Original Message-
>  From: Alec Swan [mailto:alecs...@gmail.com]
>  Sent: 23 August 2012 00:23
>  To: General discussion for Windows Installer XML toolset.
>  Subject: [WiX-users] UnistallString is not written in
>  Software\Microsoft\Windows\CurrentVersion\Uninstall\ registry key
> 
>  Hello,
> 
>  I am trying to track down why our installer generated using Wix 3.0
>  stopped writing the UninstallString value in
>  Software\Microsoft\Windows\CurrentVersion\Uninstall\ registry key.
>  At some point we must have changed some code that broke this behavior.
> 
>  Where should I start troubleshooting this? Which Wix action writes
>  this registry key?
> 
>  Thanks,
> 
>  Alec
> 
>  
>  --
>  ---
>  -
>  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-use

Re: [WiX-users] Burn - InstallAnywhere ExePackage

[Rob Mensching]

That's exactly what you'd have to do in this case. Honestly, it's not much
different than what Burn would have to do in this case as well. I dislike
this design for uninstalls. 

On Thu, Aug 23, 2012 at 8:17 AM, Hoover, Jacob
wrote:

> I really don't like this approach, but in theory could you not create a
> Stub EXE that would take an install or uninstall parameter and would have
> to have the knowledge of the InstallAnywhere package? You could then bundle
> this stub with your InstallAnywhere package.
>
> -Original Message-
> From: Rob Mensching [mailto:r...@robmensching.com]
> Sent: Thursday, August 23, 2012 9:53 AM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Burn - InstallAnywhere ExePackage
>
> Yeah, sadly we totally missed this pattern of exe installers in the first
> version of Burn.
>
> On Thu, Aug 23, 2012 at 7:41 AM, jhennessey  >wrote:
>
> > I was wondering if anyone out there has had the unfortunate task of
> > trying to bootstrap an InstallAnywhere package?
> >
> > I ask because apparently to uninstall these types of packages you need
> > to launch an "uninstall.exe" file that gets installed by the setup
> executable.
> > That being the case it appears burn won't be able to handle removal of
> > these natively (because it knows nothing about the "uninstall.exe" and
> > you can't tell it to launch an arbitrary executable).
> >
> > I really can't believe there is no way to launch an uninstall from the
> > original install package (please let me know if I'm wrong here). Does
> > anyone know a hack to get this to work or have any other advice on how
> > to deal with InstallAnywhere?
> >
> >
> >
> > --
> > View this message in context:
> > http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-Ins
> > tallAnywhere-ExePackage-tp7580040.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
>
>
> --
> 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] Burn cancel button does not work when using an MSI

[Pally Sandher]

Works fine for me. Have you modified the Burn UI? When an MSI is cancelled, the 
"cancel" button becomes a "close" button for me.

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

**Design, Simulate + Innovate with the ** 
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: Jeanne Dixon [mailto:jdi...@cots.com] 
Sent: 23 August 2012 17:12
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Burn cancel button does not work when using an MSI

I have tried to follow the examples I have been able to find regarding Burn and 
installing an MSI as part of the chain. I have an MSI that has its 
DisplayInternalUI set to yes.

If the user cancels the MSI install, burn shows that it failed (fine) but the 
cancel button on the window no longer works. The X close button does. How do I 
get the cancel button to actually do something?

--
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] Burn cancel button does not work when using an MSI

[Jeanne Dixon]

Yes, I am using the .xml and .xwl theme files to modify prompts and background 
colors. The button does become "close" but it does nothing when I click on it. 
I have to use the window X for closing.

-Original Message-
From: Pally Sandher [mailto:pally.sand...@iesve.com] 
Sent: Thursday, August 23, 2012 1:00 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Burn cancel button does not work when using an MSI

Works fine for me. Have you modified the Burn UI? When an MSI is cancelled, the 
"cancel" button becomes a "close" button for me.

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

**Design, Simulate + Innovate with the ** 
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: Jeanne Dixon [mailto:jdi...@cots.com] 
Sent: 23 August 2012 17:12
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Burn cancel button does not work when using an MSI

I have tried to follow the examples I have been able to find regarding Burn and 
installing an MSI as part of the chain. I have an MSI that has its 
DisplayInternalUI set to yes.

If the user cancels the MSI install, burn shows that it failed (fine) but the 
cancel button on the window no longer works. The X close button does. How do I 
get the cancel button to actually do something?

--
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

--
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] Disable Files In Use dialog

[Gustavo Gustavo]

>From what I’ve tested, It’s quite hard to override the FilesInUse and the
MsiRMFilesInUse dialogs.

The problem is that there are already built-in inside Wix, I cannot simply
redefine them in my own .wxi. I kind of gave up after struggling with
errors after errors.

** **

Well, maybe I have a workaround to this problem. If a ran a custom exe for
instance, before the InstallValidate step, and this utility would kill
well-known process that would be show in the FileInUse dialog otherwise,
then I could prevent such window, in the majority of cases.

But, there are two requirements: 1) The utility must run with elevated
privileges before the InstallValidate step and 2) Is should be somehow
embedded but not installed with the msi. Would that be possible?

** **

Another approach would be to have a bootstrapper that would execute the exe
before installing the msi. But that seems like the last option.

BR
/Gustavo

2012/8/23 Rob Hamflett 

> You can suppress the FilesInUse dialog by specifying
> Dialog@Modeless="yes" and Dialog@Hidden="yes".
>
> Rob
>
>
> On 23/08/2012 01:31, Gustavo Gustavo wrote:
> > I’ve been struggling to get rid of the Files In Use dialog. Seems like
> > there’s no easy way out.
> >
> > Ideally, I would like to execute my MSI with the /qb! mode, ie, showing
> > only the progress bar with modal dialog boxes enabled (for instance, the
> > reboot dialog at the end if needed for some reason).
> >
> > I don’t care if a reboot is needed at the end because another process
> had a
> > handle open to a file that must be replaced during the upgrade, as long
> as
> > the user has this message shown at the installation end. That’s why I
> > cannot use /passive or /qb-!
> >
> > During the installation, through Custom Actions, my MSI does it best to
> > close processes (well known ones in my business domain) that might block
> a
> > file replacement. The problem is that there CAs must execute with
> elevated
> > privileges (hence deferred), and, of course, after the InstallValidate
> > action, that shows up the Files In Use dialog. Therefore, these CAs
> happens
> > after the Files In Use dialog is shown. So it’s impossible to execute my
> > CAs before the InstallValidate step.
> >
> > ** **
> >
> > Will I have to create a bootstrapper what would kill the holding
> processes
> > before executing the MSI, so that the Files In Use won’t detect anything
> > (normally, since the user may be editing/blocking something, but that
> > should be very rare, and outside control)???
> >
> > ** **
> >
> > I’ve tried to play with
> >
> > ** **
> >
> > 
> >
> > 
> >
> > 
> >
> > ** **
> >
> > but it works sometimes and sometimes not (that really got be puzzled),
> so I
> > cannot trust them.
> >
> > ** **
> >
> > Kind Regards,
> >
> > /Gustavo
> >
> > **
> >
> --
> > 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/
> >
>
>
>
>
> --
> 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] FW: WiX using with MSBuild can't reference other project: error CNDL0150: Undefined preprocessor variable

[Castro, Edwin G. (Hillsboro)]

A .sqlproj is a new project type that can be created after the SQL Server Data 
Tools are installed. The new project type replaces the .dbproj project type for 
databases. If I understood better how the properties typically flow across the 
project references, then I could help figure out why it doesn't currently work 
for .sqlproj and what might need to change to support the new project type. Any 
hints or clues would be really appreciated.

Edwin G. Castro
Software Developer - Staff
Digital Channels
Fiserv
Office: 503-746-0643
Fax: 503-617-0291
www.fiserv.com
Please consider the environment before printing this e-mail


> -Original Message-
> From: Rob Mensching [mailto:r...@robmensching.com]
> Sent: Thursday, August 23, 2012 7:45 AM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] FW: WiX using with MSBuild can't reference other
> project: error CNDL0150: Undefined preprocessor variable
> 
> It's probably something unique about the .sqlproj that prevents the variables
> from flowing across the project references. I've never crated a ..sqlproj. How
> do you do that?
> 
> On Wed, Aug 22, 2012 at 6:17 PM, Castro, Edwin G. (Hillsboro) <
> edwin.cas...@fiserv.com> wrote:
> 
> > I'm building the .sln in both cases. It works in Visual Studio but
> > fails in the command line.
> >
> > I tried adding the
> > false to my
> > .wixproj but the behavior didn't change. :-(
> >
> > I can build the .sqlproj just fine from the command line (either by
> > itself or as part of the .sln).
> >
> > Edwin G. Castro
> > Software Developer - Staff
> > Digital Channels
> > Fiserv
> > Office: 503-746-0643
> > Fax: 503-617-0291
> > www.fiserv.com
> > P Please consider the environment before printing this e-mail
> >
> >
> > > -Original Message-
> > > From: Rob Mensching [mailto:r...@robmensching.com]
> > > Sent: Wednesday, August 22, 2012 4:30 PM
> > > To: General discussion for Windows Installer XML toolset.
> > > Subject: Re: [WiX-users] FW: WiX using with MSBuild can't reference
> > > other
> > > project: error CNDL0150: Undefined preprocessor variable
> > >
> > > What if you add
> > >
> > >   
> > > false
> > >   
> > > To your .wixproj?  I expect you're hitting an interplay between
> > solutions and
> > > projects. That MSBuild property disables Visual Studio from creating
> > magical
> > > properties only available when you build the .sln file. If that is
> > > set
> > and the
> > > build fails then my hypothesis is correct and .sqlproj variables are
> > dependent
> > > on solutions today the way .vcproj files were in the past.
> > >
> > >
> > > On Wed, Aug 22, 2012 at 1:16 PM, Edwin G. Castro
> > > wrote:
> > >
> > > > Ruslan Albu  kurtosys.com> writes:
> > > >
> > > > >
> > > > > But it doesn't work when I build it using MSBuild task. In my
> > > > > build definition I use the following:
> > > > >
> > > > >  > > Condition="'$(CreateSetup)'=='true'"
> > > > > Properties
> > > > > ="MsiInstallVersion=$(Major).$(Minor).$(Build).$(Revision);AutoB
> > > > > uild
> > > > > =Tru
> > > > > e"/>
> > > > >
> > > > > I'm getting this error when using MSBuild:
> > > > >
> > > > > Product.wxs(361): error CNDL0150: Undefined preprocessor
> > > > > variable '$(var.InstallDataBase.TargetDir)'.
> > > > >
> > > > > I checked the build outputs from both VS and MSBuild and the
> > > > > difference is that when building in MSBuild the candle.exe
> > > > > doesn't have the properties for the library project (for
> > > > > instance -dLibraryProjectName.ProjectDir, etc.).
> > > > >
> > > >
> > > > I'm running into this same problem.
> > > >
> > > > I have a WiX project with a reference to a .sqlproj. When I build
> > > > the solution the WiX project builds as expected but when I build
> > > > it on the command line I get error CNDL0150: Undefined
> > > > preprocessor variable similar to above.
> > > >
> > > > Similarly, when I checked the output for Visual Studio and
> > > > compared it to the output from MSBuild I noticed that the project
> > > > preprocessor variables are not getting defined in MSBuild.
> > > >
> > > > I see in wix2010.targets that the
> > > > CreateProjectReferenceDefineConstants
> > > > task is
> > > > responsible for setting the ProjectReferenceDefineConstants property.
> > > > I can also see that the CreateProjectReferenceDefineConstants task
> > > > uses
> > > > @(_ResolvedProjectReferencePaths) as ProjectReferencePaths.
> > > >
> > > > My guess is that the wix2010.targets is failing to resolve my
> > > > project dependency on the command line but it succeeds in Visual
> > > > Studio. I can't figure out why the difference occurs.
> > > >
> > > > Has anybody else experienced this? If so, how did you resolve it?
> > > >
> > > > --
> > > > Edwin G. Castro
> > > >
> > > >
> > > >
> > > >
> > > > --
> > > > 
> > > > 
> > > > Live Security Virtual Conference
> > > > Exclusive live event will cove

[WiX-users] How do I install to LocalAppData folder?

[Huang, Deqing]

Hi All,
I'd like to install my app to %LocalAppData% folder.
Following directory setting worked perfectly for me:

  

  


However, when I tried changing "ProgramFilesFolder" to "LocalAppDataFolder", I 
got lots of error when using light to link and generate my msi:
D:\runGroup.wxs(53) : error LGHT0204: ICE38: Component 
cmpA5561BE36D80EB58252E69DDA0C2FF8C installs to user profile. It must use a 
registry key under HKCU as its KeyPath, not a file.
...
D:\main.wxs(38) : error LGHT0204 : ICE64: The directory INSTALLDIR is in the 
user profile but is not listed in the Remove File table.

Looks like "LocalAppDataFolder" is not acceptable for WiX, while I believe it 
is one of the system folder properties which defined in 
http://msdn.microsoft.com/en-us/library/aa370905%28VS.85%29.aspx#system_folder_properties
What am I supposed to use for LocalAppData folder?
Regards,
Deqing



--
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