Re: [WiX-users] Bootstrap conditioned on OSbittage

[David Watson]

Hi,
Experience has taught that the best experience for the user and for the 
developer and the support organisation is to follow the way that the burn 
bundle works, it has been very carefully designed.

Fire and forget bootstrappers are an alternative (I used to use this many years 
ago http://dblock.github.io/dotnetinstaller/)  and are still widely used.

A single point of entry in ARP that allows your user to control the contents of 
the bundle is much simpler to support than a whole array of packages.



 [http://cdn.sdl.tridion.sdlproducts.com/static/corporate/SDLlogo2014.png] 

www.sdl.com


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.

-Original Message-
From: Matt O'Connell [mailto:techsupport...@gmail.com]
Sent: 09 July 2015 10:06
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Bootstrap conditioned on OSbittage

Well I only need to install one 3rd party installer based on os bittage.
On x64- install a_64.exe else install a_32.exe I don't require downloader, and 
chainer engine for that.

If I can use the burn chainer to do this AND get an effectively 'invisible' ARP 
for the un-avoidable bundle that would be 'ok'. If this is possible I'd like to 
know how. But am also looking for alternatives to WiX's current offering and 
thought this would be an ok place to ask, since the experience level here is so 
high!.
Thanks for your help on this.

On 09/07/2015 02:16, Hoover, Jacob wrote:
> My first question would be "why".  What do you need to do that you can't at 
> least allow your bundle be in the chain and let burn do its work before 
> deferring to your final exe installer?
>
> -Original Message-
> From: Matt O'Connell [mailto:techsupport...@gmail.com]
> Sent: Wednesday, July 08, 2015 7:41 PM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Bootstrap conditioned on OSbittage
>
> Sorry guys can I get some advise on this one please?
>
> I realise burn can't 'fire and forget' see
> http://www.joyofsetup.com/2013/07/05/burn-zero-one-or-n/
> but what (free) methods are there available to do this? Can anyone reccommend 
> something?
>
> Alternatively is it possible to bundle (and conditionalise) the exes but hide 
> the bundle's ARP entry and expose the third party exes ARP entries? If so 
> could the user could use that to repair/uninstall so it effectively wouldn't 
> appear that the package had been 'bundled'?
>
> Many Thanks
>
> On 17 June 2015 at 12:36, Matt O'Connell  wrote:
>
>> I've got a third party exe with 2 versions to bootstrap based on OS
>> bittage, our current setup code only does this for MSIs. I've found
>> how to do this with burn bundle but don't need the bundleness of it
>> as per this
>> http://stackoverflow.com/questions/30010837/i-dont-want-install-a-boo
>> t strapper-project-itself What would you guys recommend for this use
>> case?
>>
> --
>  Don't Limit Your Business. Reach for the Cloud.
> GigeNET's Cloud Solutions provide you with the tools and support that you 
> need to offload your IT needs and focus on growing your business.
> Configured For All Businesses. Start Your Cloud Today.
> https://www.gigenetcloud.com/
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
> --
>  Don't Limit Your Business. Reach for the Cloud.
> GigeNET's Cloud Solutions provide you with the tools and support that
> you need to offload your IT needs and focus on growing your business.
> Configured For All Businesses. Start Your Cloud Today.
> https://www.gigenetcloud.com/
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users


--
Don't Limit Your Business. Reach for the Cloud.
GigeNET's Cloud Solutions provide you with the tools and support that you need 
to offload your IT needs and focus on growing your business.
Configured For All Businesses. Start Your Cloud Today.
https://www.gigenetcloud.com/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


This message has been scanned for malware by Websense. www.websense.com
--
Don't Limit

Re: [WiX-users] Adding temporary file to the Binary table

[David Watson]

Add the file as a binary resource to your custom action and stream it from 
there?

Or use the api to read it from the binary table. 
http://blogs.msdn.com/b/icumove/archive/2009/06/23/custom-action-using-wix-reading-from-the-binary-table.aspx

It's usually easier to just install the file and then read it, but that depends 
on when the CA is scheduled.

Dave


 [http://cdn.sdl.tridion.sdlproducts.com/static/corporate/SDLlogo2014.png] 

www.sdl.com


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.

-Original Message-
From: Wang, Miaohsi [mailto:miaohsi.w...@schneider-electric.com]
Sent: 02 July 2015 19:43
To: General discussion about the WiX toolset.
Subject: [WiX-users] Adding temporary file to the Binary table

Dear WiX Support,

I've been trying to add a text file to an MSI package to be used by a custom 
action, but without success. I have added two files to the Binary table as 
shown below.

 

At install runtime, I saw only CustomAction1.dll in the WiX temp folder 
(example: C:\Windows\Installer\MSI5F76.tmp-). Is there any way I can add the 
text file to the package without installing it, and access it at install 
runtime?

Thanks a lot,
Miaohsi

Miaohsi Wang   |   Schneider Electric   |   Invensys   |   SimSci & IntelaTrac 
Software   |   Software Engineer
Phone: +1 949-455-8147
Email: 
miaohsi.w...@schneider-electric.com 
 Site: www.simsci.com   |   
Address: 26561 Rancho Parkway South, Lake Forest, CA 92630, USA

*** Please consider the environment before printing this e-mail



*** Confidentiality Notice: This e-mail, including any associated or attached 
files, is intended solely for the individual or entity to which it is 
addressed. This e-mail is confidential and may well also be legally privileged. 
If you have received it in error, you are on notice of its status. Please 
notify the sender immediately by reply e-mail and then delete this message from 
your system. Please do not copy it or use it for any purposes, or disclose its 
contents to any other person.


*** Confidentiality Notice: This e-mail, including any associated or attached 
files, is intended solely for the individual or entity to which it is 
addressed. This e-mail is confidential and may well also be legally privileged. 
If you have received it in error, you are on notice of its status. Please 
notify the sender immediately by reply e-mail and then delete this message from 
your system. Please do not copy it or use it for any purposes, or disclose its 
contents to any other person.
--
Don't Limit Your Business. Reach for the Cloud.
GigeNET's Cloud Solutions provide you with the tools and support that you need 
to offload your IT needs and focus on growing your business.
Configured For All Businesses. Start Your Cloud Today.
https://www.gigenetcloud.com/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


This message has been scanned for malware by Websense. www.websense.com
--
Don't Limit Your Business. Reach for the Cloud.
GigeNET's Cloud Solutions provide you with the tools and support that
you need to offload your IT needs and focus on growing your business.
Configured For All Businesses. Start Your Cloud Today.
https://www.gigenetcloud.com/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Why does a patch build include same versioned dlls?

[David Watson]

If you allow the tools to decide what is in your patch it ultimately does a 
binary comparison to see what has changed between versions and includes them if 
there is any difference.

You would need to dig into the patch building tools to implement an override of 
this behaviour to examine the version resource of versioned files.

I added a feature-request for this a while ago but never managed to find any 
time to submit (or write for that matter) an implementation of it.

For now I author my patch.wxs files with explicit component refs and control 
exactly what goes in each patch.

Dave


 [http://cdn.sdl.tridion.sdlproducts.com/static/corporate/SDLlogo2014.png] 

www.sdl.com


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.

-Original Message-
From: Pally Sandher [mailto:pally.sand...@iesve.com]
Sent: 24 June 2015 17:01
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Why does a patch build include same versioned dlls?

See https://msdn.microsoft.com/en-us/library/aa368599.aspx

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

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: Jakob Ziegler [mailto:subscr...@gmail.com]
Sent: 24 June 2015 15:20
To: wix-users
Subject: [WiX-users] Why does a patch build include same versioned dlls?

Hi

it always bugged me, that creating a patch either with wix or with the msimsp 
patch creation includes dlls which are binary different, but have the same 
version (or where the upgraded installer has a lower version).

When said patch is installed on top of the targeted product, those dlls will 
not end up on the system, if I understand things correctly, because the windows 
installer will actually compare both versions, not the binary hashes.

Is there a reason/rationale behind this patch creation behavior? I failed to 
find one.

Thanks
Jakob
--
Monitor 25 network devices or servers for free with OpManager!
OpManager is web-based network management software that monitors network 
devices and physical & virtual servers, alerts via email & sms for fault. 
Monitor 25 devices for free with no restriction. Download now 
http://ad.doubleclick.net/ddm/clk/292181274;119417398;o
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

--
Monitor 25 network devices or servers for free with OpManager!
OpManager is web-based network management software that monitors network 
devices and physical & virtual servers, alerts via email & sms for fault. 
Monitor 25 devices for free with no restriction. Download now 
http://ad.doubleclick.net/ddm/clk/292181274;119417398;o
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


This message has been scanned for malware by Websense. www.websense.com
--
Monitor 25 network devices or servers for free with OpManager!
OpManager is web-based network management software that monitors 
network devices and physical & virtual servers, alerts via email & sms 
for fault. Monitor 25 devices for free with no restriction. Download now
http://ad.doubleclick.net/ddm/clk/292181274;119417398;o
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Automatic upgrades/provisioning options...

[David Watson]

We use Trueupdate for delivering updates:-

http://www.indigorose.com/products/trueupdate/

We chose it instead of rolling our own as it had solved all the hard things 
already (resuming downloads, firewall and proxy stuff) and it is quite 
customizable.

Downsides are we had to learn lua and we had to fix some localization 
problems(encoding related) which lead to a convoluted build process.

Dave


 [http://cdn.sdl.tridion.sdlproducts.com/static/corporate/SDLlogo2014.png] 

www.sdl.com


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.

-Original Message-
From: Tony [mailto:yellowjacketl...@gmail.com]
Sent: 22 May 2015 14:49
To: WiX Users
Subject: [WiX-users] Automatic upgrades/provisioning options...

This is not directly WiX related (though all of our installers are WiX based), 
but I thought many of you might have some experience in this area.

We need a system/framework for deploying/managing/upgrading software (OS 
management is NOT a requirement) on 100's of remote Kiosks.

Briefly (I don't expect dissertations, just product names, and/or a sentence or 
two), what have you done to solve this scenario?

Thanks.
--
Tony
--
One dashboard for servers and applications across Physical-Virtual-Cloud Widest 
out-of-the-box monitoring support with 50+ applications Performance metrics, 
stats and reports that give you Actionable Insights Deep dive visibility with 
transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


This message has been scanned for malware by Websense. www.websense.com
--
One dashboard for servers and applications across Physical-Virtual-Cloud 
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Overwrite a file with a higher Version

[David Watson]

http://stackoverflow.com/questions/25311969/how-to-downgrade-a-third-party-file-in-a-wix-msi


 [http://cdn.sdl.tridion.sdlproducts.com/static/corporate/SDLlogo2014.png] 

www.sdl.com


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.

-Original Message-
From: RonnyS [mailto:ronnys.cod...@gmail.com]
Sent: 21 May 2015 13:18
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Overwrite a file with a higher Version

Hi I need to overwrite a file with a higher version with a lower Version.

I searching and found the folowing solution but it don`t work fine.
The old fie is not deleted and the new not installed.


 

 
 


I get no Errors in the logs.

Has anyone a Idea for this Problem?
--
One dashboard for servers and applications across Physical-Virtual-Cloud Widest 
out-of-the-box monitoring support with 50+ applications Performance metrics, 
stats and reports that give you Actionable Insights Deep dive visibility with 
transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


This message has been scanned for malware by Websense. www.websense.com
--
One dashboard for servers and applications across Physical-Virtual-Cloud 
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Exclude some files and folders in later version installation and patch

[David Watson]

I suspect you have removed the files from the folder that you run heat on, this 
means that they will have been removed from the upgrade MSI. In this case 
windows installer will remove the files from the target pc as you have removed 
them from the wix.

An msi describes the state of the machine that you want to achieve, if you have 
one with no config files, that is what you will get.

If this is the case, leave the config files present, they will not overwrite 
the current ones unless they wil upgrade them (i.e. are newer) unless the file 
has been changed on the target pc.

Dave

David Watson | Development Operations Engineer
dwat...@sdl.com | +44 114 2535251

The information transmitted, including attachments, is intended only for the 
person(s) or entity to which it is addressed and may contain confidential 
and/or privileged material. Any review, retransmission, dissemination or other 
use of, or taking of any action in reliance upon this information by persons or 
entities other than the intended recipient is prohibited. If you received this 
in error, please contact the sender and destroy any copies of this information.







David Watson | Development Operations Engineer
dwat...@sdl.com | +44 114 2535251

The information transmitted, including attachments, is intended only for the 
person(s) or entity to which it is addressed and may contain confidential 
and/or privileged material. Any review, retransmission, dissemination or other 
use of, or taking of any action in reliance upon this information by persons or 
entities other than the intended recipient is prohibited. If you received this 
in error, please contact the sender and destroy any copies of this information.








This message has been scanned for malware by Websense. www.websense.com
--
BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
Develop your own process in accordance with the BPMN 2 standard
Learn Process modeling best practices with Bonita BPM through live exercises
http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_
source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] [WIX]: Support MSI package on Windows 98/ME

[David Watson]

Windows Installer version 2.00 was included with windows XP RTM and windows 
2000 SP3
http://en.wikipedia.org/wiki/Windows_Installer#Versions

You would only need the redistributable if you were targeting an older 
operating system.



David Watson | Development Operations Engineer
dwat...@sdl.com | +44 (0) 114 2535251

The information transmitted, including attachments, is intended only for the 
person(s) or entity to which it is addressed and may contain confidential 
and/or privileged material. Any review, retransmission, dissemination or other 
use of, or taking of any action in reliance upon this information by persons or 
entities other than the intended recipient is prohibited. If you received this 
in error, please contact the sender and destroy any copies of this information.


David Watson | Development Operations Engineer
dwat...@sdl.com | +44 (0) 114 2535251

The information transmitted, including attachments, is intended only for the 
person(s) or entity to which it is addressed and may contain confidential 
and/or privileged material. Any review, retransmission, dissemination or other 
use of, or taking of any action in reliance upon this information by persons or 
entities other than the intended recipient is prohibited. If you received this 
in error, please contact the sender and destroy any copies of this information.

-Original Message-
From: Phill Hogland [mailto:phogl...@rimage.com]
Sent: 26 February 2015 13:18
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] [WIX]: Support MSI package on Windows 98/ME

What do you have Product/@InstallerVersion set too?

This  link <http://support.microsoft.com/kb/305496>   indicates that you
need to install the Windows Installer 2.0 redistributable to support a
Product/@InstallerVersion='200', but the link to the redistributable is no
longer active.



--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/WIX-Support-MSI-package-on-Windows-98-ME-tp7599352p7599354.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the
conversation now. http://goparallel.sourceforge.net/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users












This message has been scanned for malware by Websense. www.websense.com
--
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] What is this code doing?

[David Watson]

The error says you are using the VS extension in some way. look for a Help 
element or something else from that extension.

http://wixtoolset.org/documentation/manual/v3/xsd/vs/helpfile.html



-Original Message-
From: Pavan Konduru [mailto:pavan.kond...@accelrys.com] 
Sent: 18 December 2014 17:36
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] What is this code doing?


It certainly is being used in the .wxs project . The error you see is somewhere 
in the .wxs file(not Custom action).
Search for " CommonFilesFolder" in the whole solution.

-Original Message-
From: Majcica, Mario [mailto:mario.majc...@bakerhughes.com]
Sent: Thursday, December 18, 2014 7:45 AM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] What is this code doing?

I commented this part of code and I do get the following error:

Error   2   Unresolved reference to symbol 'Directory:CommonFilesFolder' in 
section 'Fragment:'.
E:\delivery\Dev\wix37_public\src\ext\VSExtension\wixlib\HTML_Help_Registration__RTL_X86.wxs

Seems that is used somewhere. Any idea on how to find which custom action is 
depending on this?

Thanks

-Original Message-
From: Majcica, Mario [mailto:mario.majc...@bakerhughes.com]
Sent: Thursday, December 18, 2014 16:27
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] What is this code doing?

Thanks Stephan,

It seems an orphan peace of code. No fragments are using it and no reference to 
that Help folder is anywhere in the project.
Seems to me safe to remove it.

I will try to get rid of it and verify if the installation is still working as 
expected.

I was scared about Bogus_HHRegCA_component, tough may be a reference to 
something internal.

But now it's clear that is just a simple component definition nothing else.

Thanks

-Original Message-
From: Tunney, Stephen [mailto:stephen.tun...@nuance.com]
Sent: Thursday, December 18, 2014 16:14
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] What is this code doing?

It is ensuring that an empty directory named

"Program Files\Common Files\Microsoft Shared\Help"

It seems a bit odd that DirectoryRef elements aren't being used.  We would need 
to see more of the Fragment/file to know EXACTLY where this directory structure 
will land.

is created.



Stephen Tunney

-Original Message-
From: Majcica, Mario [mailto:mario.majc...@bakerhughes.com]
Sent: December-18-14 10:00 AM
To: General discussion about the WiX toolset.
Subject: [WiX-users] What is this code doing?

Hi all,

I inherited in maintenance a WiX project and unfortunately who created can't be 
asked about it.

All of the code is clear except the following:

  

  

  

  

  

  

Can anyone help me understanding what is this code doing?

Thanks

Mario Majcica

--
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! 
Instantly Supercharge Your Business Reports and Dashboards with Interactivity, 
Sharing, Native Excel Exports, App Integration & more Get technology previously 
reserved for billion-dollar corporations, FREE 
http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

--
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! 
Instantly Supercharge Your Business Reports and Dashboards with Interactivity, 
Sharing, Native Excel Exports, App Integration & more Get technology previously 
reserved for billion-dollar corporations, FREE 
http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


--
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! 
Instantly Supercharge Your Business Reports and Dashboards with Interactivity, 
Sharing, Native Excel Exports, App Integration & more Get technology previously 
reserved for billion-dollar corporations, FREE 
http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


--
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! 
Instantly Supercharge Your Business Reports and Dashboards with Interactivity, 

Re: [WiX-users] Issue with deploying MSI through SCCM and GPO

[David Watson]

Do you have a verbose log we can peruse?


-Original Message-
From: Daniel Norman [mailto:daniel.nor...@snowsoftware.com] 
Sent: 04 December 2014 13:09
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Issue with deploying MSI through SCCM and GPO

Thanks for your suggestion Nick, but the problem isn't the actual deployment 
per se; I suspect it's rather with how the msiexec executable is triggered. 

Something happened and I essentially need to nail down whether the issue is 
caused by Microsoft, or the WiX Toolset.

-Original Message-
From: Nick Ramirez [mailto:nickra...@hotmail.com]
Sent: den 3 december 2014 18:10
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Issue with deploying MSI through SCCM and GPO

This probably isn't going to be helpful because I'm not that well-versed with 
using Group Policy. But when I tried it once, the program ended up on a 
different screen that regular programs. I had to go to *Control Panel -> 
Programs and Features -> Install a program from the network*. 

I base this off the following article:
http://support.microsoft.com/kb/816102



--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Issue-with-deploying-MSI-through-SCCM-and-GPO-tp7598319p7598368.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! 
Instantly Supercharge Your Business Reports and Dashboards with Interactivity, 
Sharing, Native Excel Exports, App Integration & more Get technology previously 
reserved for billion-dollar corporations, FREE 
http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

--
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! 
Instantly Supercharge Your Business Reports and Dashboards with Interactivity, 
Sharing, Native Excel Exports, App Integration & more Get technology previously 
reserved for billion-dollar corporations, FREE 
http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk
___
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.



This message has been scanned for malware by Websense. www.websense.com

--
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] effects of not using authenticode digitally signed wix msi build output

[David Watson]

http://msdn.microsoft.com/en-us/library/aa372388%28v=vs.85%29.aspx


-Original Message-
From: Nicolás Alvarez [mailto:nicolas.alva...@gmail.com] 
Sent: 21 November 2014 14:59
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] effects of not using authenticode digitally signed wix 
msi build output

Lua patching?

--
Nicolás

2014-11-21 11:50 GMT-03:00 Hoover, Jacob :

> It's only a few lines in your wixproj, and it gives you Lua patching 
> and the certainty that the payload hasn't been altered.
>
> > On Nov 20, 2014, at 9:14 PM, "zoo ob1"  wrote:
> >
> > Anyone have pointer to good article explaining impacts of not using 
> > authenticode digitally signed wix msi build output?
> >
> >
> >
> > I ask because in my organization we are debating the relevance of 
> > doing
> this
> > on wix authored msi build output that will only ever be used on 
> > internal devices and servers.
> >
> >
> >
> > My thinking is that msi doesn't really do anything to block you from
> running
> > a non-authenticode digitally signed msi installer and so unless the
> internal
> > device or server owner is looking at the file properties and 
> > stopping if they don't see a digital signature then what does it buy 
> > you adding and maintaining extra automated build complexity to do so.
> >
>
--
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! 
Instantly Supercharge Your Business Reports and Dashboards with Interactivity, 
Sharing, Native Excel Exports, App Integration & more Get technology previously 
reserved for billion-dollar corporations, FREE 
http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk
___
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.


This message has been scanned for malware by Websense. www.websense.com
--
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Repost: Wix Burn and KeyPath file hot repair/restore by Windows Installer.

[David Watson]

I thought that had changed at one point and the windows installer cached the 
full msi. Not looked into it for ages.

-Original Message-
From: John Cooper [mailto:jocoo...@jackhenry.com] 
Sent: 20 October 2014 15:04
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Repost: Wix Burn and KeyPath file hot repair/restore 
by Windows Installer.

As I recall, the copy in the Installer folder is dehydrated (stripped of 
content).  For Repair/Patch to work without the dreaded missing source dialog 
appearing, the MSI needs to be either:  1) cached, or 2) in the same location 
it was when the install was performed.

--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications | Continuing 
Development Jack Henry & Associates, Inc.® | Lenexa, KS  66214 | Ext:  431050 
|jocoo...@jackhenry.com



-Original Message-
From: David Watson [mailto:dwat...@sdl.com]
Sent: Monday, October 20, 2014 8:58 AM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Repost: Wix Burn and KeyPath file hot repair/restore 
by Windows Installer.

If the msi is installed it is usually stored in the c:\windows\installer folder 
and that would be used for autoheal repair.

I understand that burn caches packages in case this is not true anymore.


-Original Message-
From: Farrukhw [mailto:farru...@gmail.com]
Sent: 20 October 2014 13:34
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Repost: Wix Burn and KeyPath file hot repair/restore by 
Windows Installer.

Hi,
Reposting with a hope that someone may be able to give some guidance, as last 
time it was left abandoned: 
 
I've developed a Managed Bootstrapper and now near to release the product.
Normally, if a KeyPath file is removed/modified, Windows Installer would try to 
restore/repair that. But in case we used Managed Bootstrapper to deliver the 
product, Windows Installer service would be asking for the source msi installer 
files, which we have packed into the Bootstrapper in this case. 

How to let Windows Installer get the missing files from Boostrapper Package?



--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Repost-Wix-Burn-and-KeyPath-file-hot-repair-restore-by-Windows-Installer-tp7597374.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Comprehensive Server Monitoring with Site24x7.
Monitor 10 servers for $9/Month.
Get alerted through email, SMS, voice calls or mobile push notifications.
Take corrective actions from your mobile device.
http://p.sf.net/sfu/Zoho
___
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.



This message has been scanned for malware by Websense. www.websense.com

--
Comprehensive Server Monitoring with Site24x7.
Monitor 10 servers for $9/Month.
Get alerted through email, SMS, voice calls or mobile push notifications.
Take corrective actions from your mobile device.
http://p.sf.net/sfu/Zoho
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
NOTICE: This electronic mail message and any files transmitted with it are 
intended exclusively for the individual or entity to which it is addressed. The 
message, together with any attachment, may contain confidential and/or 
privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure or 
distribution is strictly prohibited. If you have received this message in 
error, please immediately advise the sender by reply email and delete all 
copies.


--
Comprehensive Server Monitoring with Site24x7.
Monitor 10 servers for $9/Month.
Get alerted through email, SMS, voice calls or mobile push notifications.
Take corrective actions from your mobile device.
http://p.sf.net/sfu/Zoho
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

--
Comprehensive Server Monitoring with Site24x7.
Monitor 10 servers for $9/Month.
Get alerted through email, SMS, voice calls or mobile push notifications.
Take correctiv

Re: [WiX-users] Repost: Wix Burn and KeyPath file hot repair/restore by Windows Installer.

[David Watson]

If the msi is installed it is usually stored in the c:\windows\installer folder 
and that would be used for autoheal repair.

I understand that burn caches packages in case this is not true anymore.


-Original Message-
From: Farrukhw [mailto:farru...@gmail.com] 
Sent: 20 October 2014 13:34
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Repost: Wix Burn and KeyPath file hot repair/restore by 
Windows Installer.

Hi,
Reposting with a hope that someone may be able to give some guidance, as last 
time it was left abandoned: 
 
I've developed a Managed Bootstrapper and now near to release the product.
Normally, if a KeyPath file is removed/modified, Windows Installer would try to 
restore/repair that. But in case we used Managed Bootstrapper to deliver the 
product, Windows Installer service would be asking for the source msi installer 
files, which we have packed into the Bootstrapper in this case. 

How to let Windows Installer get the missing files from Boostrapper Package?



--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Repost-Wix-Burn-and-KeyPath-file-hot-repair-restore-by-Windows-Installer-tp7597374.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Comprehensive Server Monitoring with Site24x7.
Monitor 10 servers for $9/Month.
Get alerted through email, SMS, voice calls or mobile push notifications.
Take corrective actions from your mobile device.
http://p.sf.net/sfu/Zoho
___
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.



This message has been scanned for malware by Websense. www.websense.com

--
Comprehensive Server Monitoring with Site24x7.
Monitor 10 servers for $9/Month.
Get alerted through email, SMS, voice calls or mobile push notifications.
Take corrective actions from your mobile device.
http://p.sf.net/sfu/Zoho
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Wix Upgrade Issue

[David Watson]

You could also split your optional features into separate MSIs and use Burn to 
control their installation behaviour, which may be easier in the long run than 
trying to fight what windows installer is intended to do. You would probably 
need a custom BA though.



-Original Message-
From: Fyodor Koryazhkin [mailto:fyodor...@gmail.com] 
Sent: 17 October 2014 08:03
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Wix Upgrade Issue

HI,
I never implemented this my self but try to do the following:
1. Use Minor upgrade instead of Major upgrade. (by definition Major upgrade is 
completely new installation that installs everything from scratch allowing to 
uninstall old versions and therefore when you choose particular features only 
they get installed) 2. In some place in UI sequence* after feature selection* 
dialog repopulate(write some custom action) ADDLOCAL, REMOVE and REINSTALL 
properties so that:
a. ADDLOCAL and REMOVE will be empty
b. REINSTALL will contain features that user selected in dialog 3. 
Repopulate REINSTALLMODE property so that include "v" (this will run 
installation from the source package and not from cached msi and at the end 
recaches msi to new one).

I hope this should work



>
> -- Forwarded message --
> From: "祁志" 
> To: wix-users@lists.sourceforge.net
> Cc:
> Date: Fri, 17 Oct 2014 10:26:16 +0800
> Subject: [WiX-users] Wix Upgrade Issue Hi All,
>
> Here is a scenario that i want to implement.but i don't have good idea 
> to implement this.
>
> let's say that someone get a installer and install it today. tomorrow 
> someone get a new installer with the higher version number want to 
> install it on the same PC. the installer with the higher version need 
> to do the following things.
>
>1. there should have a dialog to let user choose which modules to
>upgrade.
>2. update those modules base on the user's selection, but don't delete
>other modules that user don't select.
>
> i have tried use Majorupgrade element to implement this. but it always 
> delete the modules that we don't select. see below:
>
> for example .in the previously version we selected *feature A* and 
> *feature
> B* to be installed. and in the new version we only choose *feature A* 
> to update. the *feature a* was updated successfully , but it deleted 
> the feature B at same time.
>
> Is there anyone have a good idea to implement this?
>
> Thanks in advance!
>
>
>
> --
>  Comprehensive Server Monitoring with Site24x7.
> Monitor 10 servers for $9/Month.
> Get alerted through email, SMS, voice calls or mobile push notifications.
> Take corrective actions from your mobile device.
> http://p.sf.net/sfu/Zoho
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
>


--
Regards,
Fyodor Koryazhkin..
--
Comprehensive Server Monitoring with Site24x7.
Monitor 10 servers for $9/Month.
Get alerted through email, SMS, voice calls or mobile push notifications.
Take corrective actions from your mobile device.
http://p.sf.net/sfu/Zoho
___
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.


This message has been scanned for malware by Websense. www.websense.com
--
Comprehensive Server Monitoring with Site24x7.
Monitor 10 servers for $9/Month.
Get alerted through email, SMS, voice calls or mobile push notifications.
Take corrective actions from your mobile device.
http://p.sf.net/sfu/Zoho
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Repair removes application pool user

[David Watson]

Nothing built in at this time, you would need a custom action to encrypt the 
password.

-Original Message-
From: pezmannen [mailto:pezman...@gmail.com] 
Sent: 15 October 2014 11:37
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Repair removes application pool user

Anybody?



--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Repair-removes-application-pool-user-tp7597260p7597313.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Comprehensive Server Monitoring with Site24x7.
Monitor 10 servers for $9/Month.
Get alerted through email, SMS, voice calls or mobile push notifications.
Take corrective actions from your mobile device.
http://p.sf.net/sfu/Zoho
___
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.



This message has been scanned for malware by Websense. www.websense.com

--
Comprehensive Server Monitoring with Site24x7.
Monitor 10 servers for $9/Month.
Get alerted through email, SMS, voice calls or mobile push notifications.
Take corrective actions from your mobile device.
http://p.sf.net/sfu/Zoho
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Documentation Generating Tool

[David Watson]

I would imagine that It would be fairly complex to do this as Project structure 
varies widely with lots of files used to make up a wixproj.
I expect it would be much easier to create a report out of the final MSI as it 
has all the information combined and is in a well known database structure with 
available apis.

Someone has something in vbscript here 
http://www.symantec.com/connect/downloads/msi-report-generator

Or you could heat the final msi to get a combined wix file and use xslt on that 
maybe?

Dave

-Original Message-
From: Kevin Palmer [mailto:k...@orbis-software.com] 
Sent: 19 September 2014 10:09
To: 'wix-users@lists.sourceforge.net'
Subject: [WiX-users] Documentation Generating Tool

Hi Guys,

Have recently started using Wix... very impressed indeed! :)

I was looking to see if there was an Installer documentation generation tool 
available for Wix?

We would like to develop our installer in an Agile way but we also need to 
produce documentation on the Features, Components, and files etc.

Rather than producing both the Wix project and the documentation, we'd like to 
generate documentation from the Wix project.

Since the Wix XML files are well structured files, we could write a Tool to 
create documentation from these files however this got me thinking that maybe 
this already exists.. I did some searching and looked around and couldn't find 
anything.

So, the question is... are there any Wix installer documentation tools around 
that would save us writing something ourselves?

Many Thanks,


Kevin Palmer



This e-mail is confidential and may be privileged and is intended solely for 
the use of the individual or entity to who it is addressed. It may be read, 
disseminated, forwarded, printed, copied and used only by the intended 
recipient. If you have received this email in error, please contact the sender 
immediately by return e-mail or by telephoning +44 (0) 1202 241115. Please then 
delete this email and do not disclose its contents to any person. Internet 
communications are not secure and therefore Orbis Software does not accept 
legal responsibility for the safety or contents of this message and any 
attachment. No liability is accepted for any consequences arising from it. 
Orbis Software does not authorise any contract to be made using the internet. 
Any views or opinions presented are solely those of the author and do not 
necessarily represent those of Orbis Software unless otherwise specifically 
stated.
--
Slashdot TV.  Video for Nerds.  Stuff that Matters.
http://pubads.g.doubleclick.net/gampad/clk?id=160591471&iu=/4140/ostg.clktrk
___
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.



This message has been scanned for malware by Websense. www.websense.com

--
Slashdot TV.  Video for Nerds.  Stuff that Matters.
http://pubads.g.doubleclick.net/gampad/clk?id=160591471&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Intermittent errors setting Windows 8 properties on shortcuts

[David Watson]

My notes indicate that you need to set a System.AppUserModel.ID for these to 
work (I did this research a while ago and don't remember the details and if it 
is still accurate under windows 8.1).
I understand though that if you don't do it explicitly windows will allocate 
you one on the fly, but may be worth a  try.
Check out 
http://msdn.microsoft.com/en-us/library/windows/desktop/dd391569(v=vs.85).aspx 
to see if its relevant to your situation.

My example shortcut


 
 
 
 
 
 

-Original Message-
From: John Hall [mailto:john.h...@cambridgetechgroup.com] 
Sent: 16 September 2014 17:40
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Intermittent errors setting Windows 8 properties on 
shortcuts

Rob,

I am using the GUID - it appears in the error message. I've got a define called 
var.Prop_System_AppUserModel_NoPin that I use.

Regards,
John

-Original Message-
From: Rob Mensching [mailto:r...@firegiant.com] 
Sent: 16 September 2014 16:59
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Intermittent errors setting Windows 8 properties on 
shortcuts

Know Windows Installer issue. Use the GUID of the property instead of the name.

_
 Short replies here. Complete answers over there: http://www.firegiant.com/


-Original Message-
From: John Hall [mailto:john.h...@cambridgetechgroup.com] 
Sent: Tuesday, September 16, 2014 3:11 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Intermittent errors setting Windows 8 properties on 
shortcuts

Hi,

In my installer I have a number of shortcuts installed on the Start Menu that I 
don't want to appear on the Windows 8 start screen. I therefore set both the 
System.AppUserModel.StartPinOption and 
System.AppUserModel.ExcludeFromShowInNewInstall properties for each of these 
shortcuts. My code looks like this:

  

  

  


  


  

Every now and then an installation on Windows 7 will display a dialog saying:

Warning 1946.Property '{9F4C2855-9F79-4B39-A8D0-E1D42DE1D5F3}, 12' for shortcut 
'XJTAG Help' could not be set.

The warning ultimately seems benign, but it is not a good user experience. It 
warning is not consistent or reproducible. Any ideas?

Thanks,
John 

--
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce.
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

--
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce.
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
___
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.



This message has been scanned for malware by Websense. www.websense.com

--
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Certificate of signed file 'C:\Windows\Installer\1fb187a8.msp' differs in size with the certificate authored in the package

[David Watson]

Hi,
Has anyone successfully used a DigitalCertificateRef to add a new embedded .cer 
 in a patch to allow UAC patching to continue?

We have previously done this a few years ago by hacking MSIs and using a blank 
patch family but now I can't seem to get either method to work.

It seems to be applied correctly (in instead) but my new patch signed with the 
new certificate prompts for elevation with an error about the certificate size 
being mismatched (see subject).

I tried recreating the cer from the pfx and it still seems to be an issue, but 
I did have an encoding issue originally when I used base64 not binary DER.

I made a dummy msi and embedded the new cer and signed it and made a patch and 
signed that with the new certificate and that applied correctly with no UAC 
prompt.

I've even tried making a parallel patch with just the certificate in it but get 
the same error.

I am somewhat puzzled, especially as we have done this before.

Any pointers would be appreciated
Dave

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.



This message has been scanned for malware by Websense. www.websense.com

--
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] WIX environment variable missing from Windows 8.1

[David Watson]

It's there on my windows 8.1 and server 2012R2 machines.

-Original Message-
From: Rob Mensching [mailto:r...@firegiant.com] 
Sent: 29 July 2014 07:37
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] WIX environment variable missing from Windows 8.1

Does it work with v3.9? Does it work after restarting the machine?

___
 FireGiant  |  Dedicated support for the WiX toolset  |  
http://www.firegiant.com/

-Original Message-
From: Nick Ramirez [mailto:nickra...@hotmail.com] 
Sent: Monday, July 28, 2014 7:21 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] WIX environment variable missing from Windows 8.1

After installing WiX 3.8 on Windows 8.1, I saw that the system environment 
variable WIX, which is normally installed as part of the install (and still is 
on Windows 7), isn't set. Has anyone noticed this?



--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/WIX-environment-variable-missing-from-Windows-8-1-tp7596093.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Infragistics Professional
Build stunning WinForms apps today!
Reboot your WinForms applications with our WinForms controls. 
Build a bridge from your legacy apps to the future.
http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

--
Infragistics Professional
Build stunning WinForms apps today!
Reboot your WinForms applications with our WinForms controls. 
Build a bridge from your legacy apps to the future.
http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk
___
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.



This message has been scanned for malware by Websense. www.websense.com

--
Infragistics Professional
Build stunning WinForms apps today!
Reboot your WinForms applications with our WinForms controls. 
Build a bridge from your legacy apps to the future.
http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] MajorUpgrade element problems

[David Watson]

If you want to block the installation you can use the upgradeVersion element 
with OnlyDetect='yes' to set a property to use in a launch condition with your 
error message.

If you want to break the new installation away from the previous versions and 
allow for side by side installation you can change the upgrade guid. 

-Original Message-
From: Przemyslaw Galera [mailto:p.gal...@indigovision.com] 
Sent: 04 June 2014 10:02
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] MajorUpgrade element problems

Hello,
Thank you very much for your response.

What hasn't been asked explicitly is: Can I use a MajorUpgrade element and 
prevent the Software from upgrading from particular versions, that are not 
supported?

For example; I don't want to allow upgrades from versions prior to  2.1.0.0? 

Kindest regards,

Przemyslaw Galera
Software Engineer
IndigoVision 
Tel: +44 (0) 131 475 7336 (x336)
Email: p.gal...@indigovision.com
www.indigovision.com
Complete IP Video Security Solutions


-Original Message-
From: Jeremiahf [mailto:jeremi...@gmail.com] 
Sent: 02 June 2014 21:15
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] MajorUpgrade element problems

FYI there is not an attachment.

This is how I used to do it before my requirements changed...

will upgrade 1.1.1.1 to 1.1.2.1 and not allow a downgrade.

keep the Upgradecode static and the product/Package Ids to "*"

I use a config.wxi file that I include into product.wxs then reference the 
values with variables.

Up to you how to implement the values though...

Example:


  
  


NOT 
NEWERVERSIONDETECTED


  
  
   ...


In order to meet version control by the 4th version number you would have to 
use this (It is NOT a good practice.)

There are other threads explaining why in detail. You should also research how 
Microsoft handles version control to get more info in detail.

This allows 1.1.1.1 to upgrade to 1.1.1.2 and not downgrade to 1.1.0.1 or 
1.1.0.2. Pretty much what you are seeing in a sense.




  
  


Thank you,

J



On Mon, Jun 2, 2014 at 10:06 AM, Przemyslaw Galera < p.gal...@indigovision.com> 
wrote:

> Hi there!
> I have a terrible problem with using the MajorUpgrade element in the 
> current installer we have. We tended to use the Upgrade element having 
> different error messages for different versions by using 
> UpgradeVersion property.
> We wanted this behaviour to persist and to force the Major upgrade for 
> all the software upgrades. (Changing the Product.Id by using a 
> wildcard and using old UpgradeVersion is not the solution as it makes 
> the installer downgrading between builds with no errors - from 2.3.4.6 
> to 2.3.4.2 , having two software versions installed side-by-side).
>
>
> MajorUpgrade:
> ---
> It is not possible to specify the Minimum or Maximum upgradable 
> software version for this element, because the UpgradeVersion is not 
> supported by MajorUpgrade element, which prevents from creating the 
> custom actions with different error codes for particular software versions.
> ---
> Trying to work it around:
>
> Using the MajorUpgrade element side by side with Upgrade element is 
> not possible, as the MajorUpgrade's default Id is set to 
> Product.UpgradeCode which clashes with Upgrade.Id being set the same.
> There are error messages attached to the email.
>
> Could you please help? :)
>
> Thanks!
> Przemyslaw Galera
> Software Engineer
> IndigoVision
> Tel: +44 (0) 131 475 7336 (x336)
> Email: p.gal...@indigovision.com
> www.indigovision.com
> Complete IP Video Security Solutions
>
>
>
> --
>  Learn Graph Databases - Download FREE O'Reilly Book "Graph 
> Databases" is the definitive new guide to graph databases and their 
> applications. Written by three acclaimed leaders in the field, this 
> first edition is now available. Download your free book today!
> http://p.sf.net/sfu/NeoTech
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
>


--
"They may forget what you said but they will never forget how you made them 
feel." -- Anonymous
--
Learn Graph Databases - Download FREE O'Reilly Book "Graph Databases" is the 
definitive new guide to graph databases and their applications. Written by 
three acclaimed leaders in the field, this first edition is now available. 
Download your free book today!
http://p.sf.net/sfu/NeoTech
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Using '*' in Component Guids and Patches

[David Watson]

You can add the new file in a new location in a patch, and it is simpler to 
leave the old dll in place.

This may work out for you if the application supports the moved dll and will 
ignore the old dll.

If you really need to you can also try and remove the file during patching see 
http://petermarcu.blogspot.co.uk/2009/05/wix-removing-files-with-patches.html

A major upgrade is much simpler.

Dave

-Original Message-
From: Farrukhw [mailto:farru...@gmail.com] 
Sent: 29 May 2014 05:16
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Using '*' in Component Guids and Patches

It might not be a common practice, but I faced it due to some customer
requirement when we have to move a dll to another location. So ethically,
it should be a Major Upgrade which would handle it with no problem. But I
was asked to build a patch, as it is just one dll,

So we build a new dll with a new incremented version and while sing same
GUID for the component, patch didn't moved the file to new location, but
did updated the dll to the new version.

However, I tried to reproduced this using "*" instead of GUID and it simply
didn't worked.



On Thu, May 29, 2014 at 3:43 AM, Bryan Wolf-2 [via Windows Installer XML
(WiX) toolset]  wrote:

> You should change the component code if the destination of the component
> changes, as documented here:
> http://msdn.microsoft.com/en-us/library/aa367849(v=vs.85).aspx
>
> Changing the component code is incompatible with minor/small updates;
> since
> you're talking about a patch and a major upgrade patch is more or less a
> non-feature, the short answer is that it won't work. Don't change the path
> of a component during the course of a patch - it's just not a compatible
> use case.
>
> Technically speaking, you can make it work through careful and very
> elaborate tailoring of the MSI package and manipulation of the feature
> tree, but you really really don't want to do this :-)
>
>
> On Wed, May 28, 2014 at 5:29 PM, Rob Mensching <[hidden 
> email]>
> wrote:
>
> > IIRC, I don't think that's going to work out well. You can try but I
> think
> > patching across directory moves probably doesn't work out great since
> IIRC
> > moving Component directories during repair doesn't tend to work out real
> > well either. But that's just from memory...
> >
> > ___
> >  FireGiant  |  Dedicated support for the WiX toolset  |
> > http://www.firegiant.com/
> >
> > -Original Message-
> > From: Farrukhw [mailto:[hidden 
> > email]]
>
> > Sent: Sunday, May 25, 2014 10:13 PM
> > To: [hidden email]
> > Subject: [WiX-users] Using '*' in Component Guids and Patches
> >
> > Hi
> > While searching for best practices, I came across  this thread <
> >
> http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Best-Practices-Using-quot-quot-for-GUID-automation-td5234716.html
> > >
> > , which is discussing the use of '*' instead of GUIDs in components.
> >
> > As far I know, while generating GUID dynamically from '*', if the
> > destination of a Component is changes, so its GUID would also be
> changed.
> > There may be some other factors as well.
> >
> > Let's say we released ver 1.0.0.0 and then in 1.0.1.0 we changed the
> > destination of a Component from Dir1 to Dir2.
> >
> > *Question:* If we generate Differential Patch between these two
> versions,
> > would the file get patched who's destination was changed in ver 1.0.1.0?
> > Would using '*' in this case would be good?
> >
> > Regards
> > Farrukh
> >
> >
> >
> >
> >
> > --
> > View this message in context:
> >
> http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Using-in-Component-Guids-and-Patches-tp7594909.html
> > Sent from the wix-users mailing list archive at Nabble.com.
> >
> >
> >
> --
>
> > The best possible search technologies are now affordable for all
> companies.
> > Download your FREE open source Enterprise Search Engine today!
> > Our experts will assist you in its installation for $59/mo, no
> commitment.
> > Test it for FREE on our Cloud platform anytime!
> >
> >
> http://pubads.g.doubleclick.net/gampad/clk?id=145328191&iu=/4140/ostg.clktrk
> > ___
> > WiX-users mailing list
> > [hidden email] 
> > https://lists.sourceforge.net/lists/listinfo/wix-users
> >
> >
> >
> --
>
> > Time is money. Stop wasting it! Get your web API in 5 minutes.
> > www.restlet.com/download
> > http://p.sf.net/sfu/restlet
> > ___
> > WiX-users mailing list
> > [hidden email] 

[WiX-users] EV code signing compatibility

[David Watson]

Hi,
Has anyone used one of the new EV Authenticode certificates to sign MSIs and 
bundles?

If so have you had any issues with it so far?

Also is it possible to export the public key into a cer file from the hardware 
token to allow you to embed it in an MSI to do UAC-less patches?



Cheers
Dave
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.



This message has been scanned for malware by Websense. www.websense.com

--
Time is money. Stop wasting it! Get your web API in 5 minutes.
www.restlet.com/download
http://p.sf.net/sfu/restlet
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] .NET 4.5.2

[David Watson]

http://support.microsoft.com/kb/2901907

has it at

http://go.microsoft.com/fwlink/?LinkId=328856

-Original Message-
From: Neil Sleightholm [mailto:n...@x2systems.com] 
Sent: 20 May 2014 10:57
To: wix-users (wix-users@lists.sourceforge.net)
Subject: [WiX-users] .NET 4.5.2

I am working on a .NET 4.5.2 install and am looking for the direct link to 
download it in my bundle. For 4.5.1 the link is 
http://go.microsoft.com/fwlink/?LinkId=322116 does anyone know what the 
equivalent is for 4.5.2 or where to find it? (I am looking for the "fwlink" 
link id not the location where I can manually download it.)

Thanks

Neil

Neil Sleightholm
X2 Systems Limited
n...@x2systems.com

--
"Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE 
Instantly run your Selenium tests across 300+ browser/OS combos.
Get unparalleled scalability from the best Selenium testing platform available 
Simple to use. Nothing to install. Get started now for free."
http://p.sf.net/sfu/SauceLabs
___
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.



This message has been scanned for malware by Websense. www.websense.com

--
"Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
Instantly run your Selenium tests across 300+ browser/OS combos.
Get unparalleled scalability from the best Selenium testing platform available
Simple to use. Nothing to install. Get started now for free."
http://p.sf.net/sfu/SauceLabs
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Burn setting InstallFolder depending 32/64 bit

[David Watson]

Some large companies use mass deployment methods to distribute software to 
thousands of users automatically and they prefer to use MSI files to do this as 
the reporting they get back from them is better. They would tend to strip the 
msi out of your bundle and use it directly (and silently).

In these scenarios it makes sense for the msi to be as self-contained as 
possible.


-Original Message-
From: Jenny [mailto:kie...@infosim.net] 
Sent: 13 May 2014 10:35
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Burn setting InstallFolder depending 32/64 bit

Phill Hogland wrote
> Consider using ProgramFiles6432Folder to initialize the burn variable.

Ah thank you, it works! I didn't know there is such a variable. On the 
Microsoft page it isn't listed.


Phill Hogland wrote
> You can also use the Persist attribute to have burn persist the value, 
> but you may prefer to implement a remember property pattern in the msi.

I don't get that. Why should I use this property? I will never call my MSI 
outside my Bootstrapper because it's embedded in it. 
(Note: I also read the blogentry of Robmen about it, but I still don't know why 
it would make sense in my project)



--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-setting-InstallFolder-depending-32-64-bit-tp7594661p7594689.html
Sent from the wix-users mailing list archive at Nabble.com.

--
"Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE 
Instantly run your Selenium tests across 300+ browser/OS combos.
Get unparalleled scalability from the best Selenium testing platform available 
Simple to use. Nothing to install. Get started now for free."
http://p.sf.net/sfu/SauceLabs
___
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.



This message has been scanned for malware by Websense. www.websense.com

--
"Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
Instantly run your Selenium tests across 300+ browser/OS combos.
Get unparalleled scalability from the best Selenium testing platform available
Simple to use. Nothing to install. Get started now for free."
http://p.sf.net/sfu/SauceLabs
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] upgrade not working

[David Watson]

If you want to do a major upgrade, ditch the upgrade elements for a 
MajorUpgrade one, change the product Id to *.

Be aware that the MSI only pays attention to the first three parts of the 
product version, but in this example it should upgrade.


-Original Message-
From: kurt.jen...@us.ophiropt.com [mailto:kurt.jen...@us.ophiropt.com] 
Sent: 08 May 2014 16:28
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] upgrade not working

Have a new installation that refuses to upgrade.  On each new release the 
installer complains. That "Another version of this product is already 
installed...  Below is the Product.wxs file.  Build and install this version, 
change BGProductVersion to 1.11.5241.1234, build and install, "Another 
version..." message.  Simply cannot see why this is not working.  Please help.


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




  

  



  







 
  

  
  

  

  
  

  
  

  
  
  
   




--
Is your legacy SCM system holding you back? Join Perforce May 7 to find out:
• 3 signs your SCM is hindering your productivity • Requirements for 
releasing software faster • Expert tips and advice for migrating your SCM 
now http://p.sf.net/sfu/perforce ___
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.



This message has been scanned for malware by Websense. www.websense.com

--
Is your legacy SCM system holding you back? Join Perforce May 7 to find out:
• 3 signs your SCM is hindering your productivity
• Requirements for releasing software faster
• Expert tips and advice for migrating your SCM now
http://p.sf.net/sfu/perforce
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Queries on Upgrade

[David Watson]

Phil not Bob, sorry :)


-Original Message-
From: David Watson [mailto:dwat...@sdl.com] 
Sent: 25 April 2014 13:48
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Queries on Upgrade

Installers are registered by product code.

As Bob said the upgrade code is stored elsewhere in the registry in a different 
format so you can't search for it.

-Original Message-
From: Karkare,Aparna [mailto:akark...@travelers.com]
Sent: 25 April 2014 12:52
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Queries on Upgrade

Hi Gabriel,

Sorry but I don't understand your answer. I am not asking what to search for. 
As you said for Per user install Upgrade code goes into HKUSERS but when I 
checked it wasn't there. It wasn't in HKLM and HKCU as well. So my question is 
how while upgrade it finds related product when Product code keeps changing 
with every build as it is "*" and Upgrade code is not present in any hive of 
registry.

Aparna Karkare
L&T Infotech
OAI-sys, Enterprise Components and Frameworks
Office: 020-6641-6142
Email: akark...@travelers.com


-Original Message-
From: Gabriel Ivanes [mailto:g...@fastmail.net]
Sent: Friday, April 25, 2014 7:27 AM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Queries on Upgrade

Search for the productcode.
--
Sincerely,
Gabriel
--
Start Your Social Network Today - Download eXo Platform Build your Enterprise 
Intranet with eXo Platform Software Java Based Open Source Intranet - Social, 
Extensible, Cloud Ready Get Started Now And Turn Your Intranet Into A 
Collaboration Platform http://p.sf.net/sfu/ExoPlatform 
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

This communication, including attachments, is confidential, may be subject to 
legal privileges, and is intended for the sole use of the addressee. Any use, 
duplication, disclosure or dissemination of this communication, other than by 
the addressee, is prohibited. If you have received this communication in error, 
please notify the sender immediately and delete or destroy this communication 
and all copies.

TRVDiscDefault::1201

--
Start Your Social Network Today - Download eXo Platform Build your Enterprise 
Intranet with eXo Platform Software Java Based Open Source Intranet - Social, 
Extensible, Cloud Ready Get Started Now And Turn Your Intranet Into A 
Collaboration Platform http://p.sf.net/sfu/ExoPlatform 
___
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.



This message has been scanned for malware by Websense. www.websense.com

--
Start Your Social Network Today - Download eXo Platform Build your Enterprise 
Intranet with eXo Platform Software Java Based Open Source Intranet - Social, 
Extensible, Cloud Ready Get Started Now And Turn Your Intranet Into A 
Collaboration Platform http://p.sf.net/sfu/ExoPlatform 
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

--
Start Your Social Network Today - Download eXo Platform
Build your Enterprise Intranet with eXo Platform Software
Java Based Open Source Intranet - Social, Extensible, Cloud Ready
Get Started Now And Turn Your Intranet Into A Collaboration Platform
http://p.sf.net/sfu/ExoPlatform
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Queries on Upgrade

[David Watson]

Installers are registered by product code.

As Bob said the upgrade code is stored elsewhere in the registry in a different 
format so you can't search for it.

-Original Message-
From: Karkare,Aparna [mailto:akark...@travelers.com] 
Sent: 25 April 2014 12:52
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Queries on Upgrade

Hi Gabriel,

Sorry but I don't understand your answer. I am not asking what to search for. 
As you said for Per user install Upgrade code goes into HKUSERS but when I 
checked it wasn't there. It wasn't in HKLM and HKCU as well. So my question is 
how while upgrade it finds related product when Product code keeps changing 
with every build as it is "*" and Upgrade code is not present in any hive of 
registry.

Aparna Karkare
L&T Infotech
OAI-sys, Enterprise Components and Frameworks
Office: 020-6641-6142
Email: akark...@travelers.com


-Original Message-
From: Gabriel Ivanes [mailto:g...@fastmail.net]
Sent: Friday, April 25, 2014 7:27 AM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Queries on Upgrade

Search for the productcode.
--
Sincerely,
Gabriel
--
Start Your Social Network Today - Download eXo Platform Build your Enterprise 
Intranet with eXo Platform Software Java Based Open Source Intranet - Social, 
Extensible, Cloud Ready Get Started Now And Turn Your Intranet Into A 
Collaboration Platform http://p.sf.net/sfu/ExoPlatform 
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

This communication, including attachments, is confidential, may be subject to 
legal privileges, and is intended for the sole use of the addressee. Any use, 
duplication, disclosure or dissemination of this communication, other than by 
the addressee, is prohibited. If you have received this communication in error, 
please notify the sender immediately and delete or destroy this communication 
and all copies.

TRVDiscDefault::1201

--
Start Your Social Network Today - Download eXo Platform Build your Enterprise 
Intranet with eXo Platform Software Java Based Open Source Intranet - Social, 
Extensible, Cloud Ready Get Started Now And Turn Your Intranet Into A 
Collaboration Platform http://p.sf.net/sfu/ExoPlatform 
___
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.



This message has been scanned for malware by Websense. www.websense.com

--
Start Your Social Network Today - Download eXo Platform
Build your Enterprise Intranet with eXo Platform Software
Java Based Open Source Intranet - Social, Extensible, Cloud Ready
Get Started Now And Turn Your Intranet Into A Collaboration Platform
http://p.sf.net/sfu/ExoPlatform
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Burn: doing an Administrative Installation

[David Watson]

You can do a /layout to get the contents of the bundle, then you would need to 
do an admin install with the msi.

Don't know if there is a /admin on the bundle, you could make one if not that 
calls each msi in turn with admin parameters.

-Original Message-
From: Bruce Cran [mailto:br...@cran.org.uk] 
Sent: 09 April 2014 19:00
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Burn: doing an Administrative Installation

We package our MSI using Burn, and have had a request to allow users to dump 
the files in one of the MSIs to a directory instead of installing them - i.e. 
doing an Administrative installation 
(http://msdn.microsoft.com/en-us/library/aa367541%28v=vs.85%29.aspx). 
Does the functionality exist in Burn to do this?

--
Bruce

--
Put Bad Developers to Shame
Dominate Development with Jenkins Continuous Integration Continuously Automate 
Build, Test & Deployment Start a new project now. Try Jenkins in the cloud.
http://p.sf.net/sfu/13600_Cloudbees
___
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.



This message has been scanned for malware by Websense. www.websense.com

--
Put Bad Developers to Shame
Dominate Development with Jenkins Continuous Integration
Continuously Automate Build, Test & Deployment 
Start a new project now. Try Jenkins in the cloud.
http://p.sf.net/sfu/13600_Cloudbees
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Resigning MSI package

[David Watson]

Hi,
You can just use signtool to sign them like an .exe. There are some issues 
around this though, you will probably not have access to the 3rd party 
certificate which means you will have to use your own and explain to your users 
that you resigned them should they care or notice. If any of these packages has 
an embedded certificate to allow them to do UAC-less patching you will need to 
address this by explaining that this will no longer work or you will need to 
embed your own certificate into the MSI.

Dave

-Original Message-
From: fom Forstner Michael [mailto:f...@keba.com] 
Sent: 03 April 2014 08:29
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Resigning MSI package

Hi,

I have a question about resigning MSI packages.

My scenario:
I built a .NET application to handle a whole bunch of MSI packages as a 
complete product suite (platform). Those MSI packages hold some custom 
properties that are used for install/update logic and visual appearance of the 
product tree (child/parent).
It is the case now, that we will eventually get MSI packages from some of our 
external suppliers. My thought was now to edit those MSI packages databases to 
include our custom properties to make them compatible to my application. As I 
understand it, this would invalidate the MSI signature. Someone in my earlier 
discussions mentioned that resigning of MSI packages is possible though.

Can you provide me with some information of how to resign MSI packages?

kind regards,
Michael


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



This message has been scanned for malware by Websense. www.websense.com

--
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Creating Isolated Storage for main assembly during it's install.

[David Watson]

Ideally configuration like this should be done at first run by your application.
Your installer should deploy the config file in a safe place under your 
installation folder somewhere where it is not in use then it should be copied 
to the live location during configuration by the application.
This way you can patch or update the config file without having the headache of 
working out if it has changed by the user. All the complex logic can go in your 
application.

Doesn't answer your question though.

How are you accessing the public methods of the .exe from your custom action, 
it may this binding that's going a bit weird?


-Original Message-
From: paul.chor...@stfc.ac.uk [mailto:paul.chor...@stfc.ac.uk] 
Sent: 31 March 2014 16:06
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Creating Isolated Storage for main assembly during 
it's install.

Hello Carter,

Thanks for your quick reply, unfortunately this does not work as the problem is 
not with the preconfigured XML file, but with which executable owns the ISO 
area after its created by the installer. (C# Custom Action or ISOTest.exe). 
This can be observed from the "store.AssemblyIdentity" property. 

The if (File.Exists("RemotingConfig.xml")) test was merely to test that the 
file was included in the project build. 

In a DEBUG build (where "store.AssemblyIdentity" = ISOTest) the C# Custom 
Action (separate project in the solution) creates an ISO area by calling the 
target assembly's "ISOTest.ExposeIsolatedStorage.GetIsolatedStorage()" method 
and produces an ISO which IS accessible to the  ISOTest.exe application after 
installation.  The Custom Action also copies the pre-configured 
"RemotingConfig.xml" file to that area. So everything is OK for this build.

In a RELEASE build (where "store.AssemblyIdentity" = CustomAction) the C# 
Custom Action (separate project in the solution) creates an ISO area by calling 
the target assemblies "ISOTest.ExposeIsolatedStorage.GetIsolatedStorage()" 
method and produces its own ISO which is NOT accessible to the  ISOTest.exe 
application after installation.  The Custom Action also copies the 
pre-configured "RemotingConfig.xml" file to its own area, but obviously 
ISOTest.exe cannot access area.

There is some difference between the DEBUG & RELEASE builds in VS that affects 
this which I cannot find or understand. 

Cheers,
Paul

-Original Message-
From: Carter Young [mailto:ecyo...@grandecom.net] 
Sent: 31 March 2014 14:48
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Creating Isolated Storage for main assembly during 
it's install.

Change:
try
...
isoFileStream = new
IsolatedStorageFileStream("RemotingConfig.xml", FileMode.Create, store);

to:
try
...
isoFileStream = new
IsolatedStorageFileStream(String.Concat(Application.StartupPath,"RemotingConfig.xml",
 FileMode.Create, store));

Or add:
if not File.exists(String.Concat(Application.StartupPath,"RemotingConfig.xml")
{
 file.create(String.Concat(Application.StartupPath,"RemotingConfig.xml")
 isoFileStream = new
IsolatedStorageFileStream("RemotingConfig.xml",FileMode.Create, store); } else {
  isoFileStream = new
IsolatedStorageFileStream("RemotingConfig.xml",FileMode.Create, store); }

Carter



--
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
-- 
Scanned by iCritical.

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



This message has been scanned for malware by Websense. www.websense.com

--
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Uninstall removing the default Virtual directory and not the one user created

[David Watson]

You need to persist the VIRTUAL_DIR_VAL (store it in the registry) so the 
uninstaller knows it has changed otherwise it will use the default values.

http://robmensching.com/blog/posts/2010/5/2/the-wix-toolsets-remember-property-pattern


-Original Message-
From: Suvrajyoti Panda [mailto:suvrajyo...@contata.co.in] 
Sent: 21 March 2014 12:53
To: General discussion about the WiX toolset.
Subject: [WiX-users] Uninstall removing the default Virtual directory and not 
the one user created

Hi All,

I am creating virtual directory through WIX installer. The installer 
allows user to change the name of the virtual directory through a custom 
UI dialogue. The default virtual directory is PFWServiceApplication. If 
the user changes this to say PFWServiceApplication_Test then the correct 
virtual directory is created and installation works fine. But the 
uninstall removes the default virtual directory. For instance i had 
created the default virtual directory PFWServiceApplication manually for 
testing and then used the installer to create the 
PFWServiceApplication_Test virtual directory. On uninstalling the 
PFWServiceApplication gets fully removed and the for 
PFWServiceApplication_Test only the node is left under the default 
website.  What i want is that on uninstall only that virtual directory 
that i installed through the installer should be removed. Below is my code.


 

 
 
 
 

 
 
 
 
 

 
 
 
 
 
 
 
 

 
 
 
 

 

The include file ConfigurationInitialize.wxi has below code:
   

 
 

Please provide some help on this.

Regards,
Suvra Jyoti

--
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/13534_NeoTech
___
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.



This message has been scanned for malware by Websense. www.websense.com

--
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/13534_NeoTech
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Making 64 bit installer from 32bit wix file

[David Watson]

You can trouble shoot your target machine for dependency issues by using either 
dependency walker for native code (http://www.dependencywalker.com/) or use 
fusion logging for .net to see if something is missing at runtime.

-Original Message-
From: Hoover, Jacob [mailto:jacob.hoo...@greenheck.com] 
Sent: 19 March 2014 19:45
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Making 64 bit installer from 32bit wix file

Which is why I asked you to compare file by file to see what one is different. 
I'm guessing either you missed a file (so it exists in your release folder but 
not in the install), or you are grabbing the "wrong file" from a different 
location. Compare file size, versions, and names. Something has to be 
different.  Identify the difference, and then look to your install where you 
should be getting those files from.

-Original Message-
From: karthikrangaraj [mailto:kranga...@dnpphoto.eu] 
Sent: Wednesday, March 19, 2014 2:17 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Making 64 bit installer from 32bit wix file

Hi,
eveything is working perfectly on Win 32 and there is no other dependencies fro 
64bit. As i said if i launch a release folder files in Win 8.1 64 
bit..everything is working.

Thank you



-
Wix 3.8 users
--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Making-64-bit-installer-from-32bit-wix-file-tp7593557p7593577.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Learn Graph Databases - Download FREE O'Reilly Book "Graph Databases" is the 
definitive new guide to graph databases and their applications. Written by 
three acclaimed leaders in the field, this first edition is now available. 
Download your free book today!
http://p.sf.net/sfu/13534_NeoTech
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

--
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/13534_NeoTech
___
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.



This message has been scanned for malware by Websense. www.websense.com

--
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/13534_NeoTech
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] How WiX created its own setup package?

[David Watson]

http://wix.codeplex.com/SourceControl/latest#src/Setup/


-Original Message-
From: Bo Zhang [fabbricadigitale] [mailto:b.zh...@fabbricadigitale.it] 
Sent: 04 March 2014 11:31
To: General discussion about the WiX toolset.
Subject: [WiX-users] How WiX created its own setup package?

Hi folks, so, as written,  I am very curious about this:

Is the WiX installer writtn in WiX? Is the sourcecode available? Could you 
provide a link if you know it?

Great thanks.
Bo
--
Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce.
With Perforce, you get hassle-free workflows. Merge that actually works. 
Faster operations. Version large binaries.  Built-in WAN optimization and the 
freedom to use Git, Perforce or both. Make the move to Perforce.
http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk
___
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.



This message has been scanned for malware by Websense. www.websense.com

--
Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce.
With Perforce, you get hassle-free workflows. Merge that actually works. 
Faster operations. Version large binaries.  Built-in WAN optimization and the
freedom to use Git, Perforce or both. Make the move to Perforce.
http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] how to pass values from command line to wix installer

[David Watson]

It looks like @AnonymousAccess is not a formatted type so it does not accept 
the property.

You would need to author two mutually exclusive components that differ only by 
AnonymousAccess and use the passed in condition as a component condition.

Dave

-Original Message-
From: Kiran Somisetty [mailto:mr.svski...@gmail.com] 
Sent: 11 February 2014 14:42
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] how to pass values from command line to wix installer

I have declared the property like below

yes

using it like below



but when I compile the project I am getting below error

Error 3 The iis:WebDirProperties/@AnonymousAccess attribute's value, 
'[VALUEPASSED]', is not a legal yes/no value.  The only legal values are 'no' 
and 'yes'. C:\Infodev\TRFAudit\WixInstaller\trfaudit.wxs 26 1 Installer

Pls correct me.


On Tue, Feb 11, 2014 at 7:56 PM, Ilir Bekteshi  wrote:

> You should use Property for example:
> 
>
> Then run msiexec /i abc.msi VALUEPASSED=yourvalue
>
> On 2/11/14, Walter Dexter  wrote:
> > If you mean when you install the resulting MSI, that would be in the 
> > Windows installer documentation. Or you can do msiexec /? and I 
> > think that's in there.
> > On Feb 11, 2014 7:42 AM, "Kiran Somisetty" 
> wrote:
> >
> >>   I have a requirement to pass values from the command line while 
> >> installing the wix.
> >>
> >>   I want to assign this to AnynymousAccess attribute.
> >>
> >>
> >>
> >> 
> >>
> >>
> >>
> >> Can you pls help me on this, I searched the documentation, but 
> >> haven't got any clues.
> >>
> >>
> >>
> >> Kiran
> >>
> >>
> --
> 
> >> Android apps run on BlackBerry 10
> >> Introducing the new BlackBerry 10.2.1 Runtime for Android apps.
> >> Now with support for Jelly Bean, Bluetooth, Mapview and more.
> >> Get your Android app in front of a whole new audience.  Start now.
> >>
> >>
> http://pubads.g.doubleclick.net/gampad/clk?id=124407151&iu=/4140/ostg.
> clktrk
> >> ___
> >> WiX-users mailing list
> >> WiX-users@lists.sourceforge.net
> >> https://lists.sourceforge.net/lists/listinfo/wix-users
> >>
> >
> --
> 
> > Android apps run on BlackBerry 10
> > Introducing the new BlackBerry 10.2.1 Runtime for Android apps.
> > Now with support for Jelly Bean, Bluetooth, Mapview and more.
> > Get your Android app in front of a whole new audience.  Start now.
> >
> http://pubads.g.doubleclick.net/gampad/clk?id=124407151&iu=/4140/ostg.
> clktrk
> > ___
> > WiX-users mailing list
> > WiX-users@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/wix-users
> >
>
>
> --
> 
> Android apps run on BlackBerry 10
> Introducing the new BlackBerry 10.2.1 Runtime for Android apps.
> Now with support for Jelly Bean, Bluetooth, Mapview and more.
> Get your Android app in front of a whole new audience.  Start now.
>
> http://pubads.g.doubleclick.net/gampad/clk?id=124407151&iu=/4140/ostg.
> clktrk ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
--
Android apps run on BlackBerry 10
Introducing the new BlackBerry 10.2.1 Runtime for Android apps.
Now with support for Jelly Bean, Bluetooth, Mapview and more.
Get your Android app in front of a whole new audience.  Start now.
http://pubads.g.doubleclick.net/gampad/clk?id=124407151&iu=/4140/ostg.clktrk
___
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.



This message has been scanned for malware by Websense. www.websense.com

--
Android apps run on BlackBerry 10
Introducing the new BlackBerry 10.2.1 Runtime for Android apps.
Now with support for Jelly Bean, Bluetooth, Mapview and more.
Get your Android app in front of a whole new audience.  Start now.
http://pubads.g.doubleclick.net/gampad/clk?id=124407151&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] how to pass values from command line to wix installer

[David Watson]

If you need to pass information into an MSI at runtime you need to author a 
public property.

http://msdn.microsoft.com/en-us/library/aa370912(v=vs.85).aspx

You should also remember what was passed in from the command line or it will 
revert to default on a repair or patch, see:-

http://robmensching.com/blog/posts/2010/5/2/the-wix-toolsets-remember-property-pattern


-Original Message-
From: Ilir Bekteshi [mailto:ilir...@gmail.com] 
Sent: 11 February 2014 14:27
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] how to pass values from command line to wix installer

You should use Property for example:


Then run msiexec /i abc.msi VALUEPASSED=yourvalue

On 2/11/14, Walter Dexter  wrote:
> If you mean when you install the resulting MSI, that would be in the 
> Windows installer documentation. Or you can do msiexec /? and I think 
> that's in there.
> On Feb 11, 2014 7:42 AM, "Kiran Somisetty"  wrote:
>
>>   I have a requirement to pass values from the command line while 
>> installing the wix.
>>
>>   I want to assign this to AnynymousAccess attribute.
>>
>>
>>
>> 
>>
>>
>>
>> Can you pls help me on this, I searched the documentation, but 
>> haven't got any clues.
>>
>>
>>
>> Kiran
>>
>> -
>> -
>> Android apps run on BlackBerry 10
>> Introducing the new BlackBerry 10.2.1 Runtime for Android apps.
>> Now with support for Jelly Bean, Bluetooth, Mapview and more.
>> Get your Android app in front of a whole new audience.  Start now.
>>
>> http://pubads.g.doubleclick.net/gampad/clk?id=124407151&iu=/4140/ostg
>> .clktrk ___
>> WiX-users mailing list
>> WiX-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/wix-users
>>
> --
> 
> Android apps run on BlackBerry 10
> Introducing the new BlackBerry 10.2.1 Runtime for Android apps.
> Now with support for Jelly Bean, Bluetooth, Mapview and more.
> Get your Android app in front of a whole new audience.  Start now.
> http://pubads.g.doubleclick.net/gampad/clk?id=124407151&iu=/4140/ostg.
> clktrk ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>

--
Android apps run on BlackBerry 10
Introducing the new BlackBerry 10.2.1 Runtime for Android apps.
Now with support for Jelly Bean, Bluetooth, Mapview and more.
Get your Android app in front of a whole new audience.  Start now.
http://pubads.g.doubleclick.net/gampad/clk?id=124407151&iu=/4140/ostg.clktrk
___
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.



This message has been scanned for malware by Websense. www.websense.com

--
Android apps run on BlackBerry 10
Introducing the new BlackBerry 10.2.1 Runtime for Android apps.
Now with support for Jelly Bean, Bluetooth, Mapview and more.
Get your Android app in front of a whole new audience.  Start now.
http://pubads.g.doubleclick.net/gampad/clk?id=124407151&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Problem with service install on non English OS

[David Watson]

I'm not sure there is an issue with the way wix looks the account name up as 
you seem to use this in several other places and they are working and the 
values returned seem to be right.

The actual error seems to be about the dependency services, which seems to be 
msmq according to your install log. Is msmq running correctly when the service 
fails to start?
I notice that you use dism to install msmq, as this is not something I would do 
from an msi I'm not sure if this would be initialized properly and the service 
be running before you try to start your installed services.

Is there anything in the event log?

You seem to be using a custom action to start the services and not the built in 
service control elements, and some of the queue permissions are set after the 
services are attempted to be started, do you think that may be related?

Sorry probably not much help.
Dave


-Original Message-
From: Stephen I. Woolhead [mailto:s...@gtl.biz] 
Sent: 17 January 2014 13:57
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Problem with service install on non English OS

Opps, wrong link in message below.

Correct one is:
https://gtl.sharefile.com/d/s9ec51dd7d1a4dd09

Stephen.

-Original Message-
From: Stephen I. Woolhead [mailto:s...@gtl.biz]
Sent: 17 January 2014 13:18
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Problem with service install on non English OS

OK, here are the log files, also a couple of screen shots.  

https://gtl.sharefile.com/d/sbf6c4368f35490e9

ServiceManager.png - Service manager after install StartError.png - Error we 
get when attempting to start service ResetViaUI.png - Service manager after we 
reset the logon account via the UI and successfully start service

In the log file, you can see a bunch of errors starting around line 9319 as our 
custom actions attempts to start the services.

Cheers,

Stephen.


-Original Message-----
From: David Watson [mailto:dwat...@sdl.com]
Sent: 17 January 2014 09:29
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Problem with service install on non English OS

Can you post a full install log somewhere - attachments tend to get deleted by 
the mailing system ?

Also the exact error you get when you try and start the service.

You may need to enter a bug.

-Original Message-
From: Stephen I. Woolhead [mailto:s...@gtl.biz]
Sent: 16 January 2014 23:07
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Problem with service install on non English OS



Just tried this on a Turkish and Russian OS and it installs and runs fine, so 
it does look like there is something strange with the Polish OS.



Not sure where to go next with this



Stephen.



-Original Message-
From: Stephen I. Woolhead [mailto:s...@gtl.biz]
Sent: 16 January 2014 17:05
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Problem with service install on non English OS



I'll go give it a try in some other languages and see if they work.



Cheers,



Stephen.



-Original Message-----

From: David Watson [mailto:dwat...@sdl.com]

Sent: 16 January 2014 16:42

To: General discussion about the WiX toolset.

Subject: Re: [WiX-users] Problem with service install on non English OS



The wix properties are populated by an api call at runtime, so it should be 
working fine and they are the correct option in this case.



There may be a specific issue in this language.



Is there anything interesting in the install log?











-Original Message-

From: Stephen I. Woolhead [mailto:s...@gtl.biz]

Sent: 16 January 2014 15:23

To: General discussion about the WiX toolset.

Subject: Re: [WiX-users] Problem with service install on non English OS



Ah, yes get what you mean, that was if I was to hard code the names into the 
wxs, I was hoping I would be able to use the translations WiX supplies at 
install time.



-Original Message-

From: Phill Hogland [mailto:phogl...@rimage.com]

Sent: 16 January 2014 15:04

To: wix-users@lists.sourceforge.net<mailto:wix-users@lists.sourceforge.net>

Subject: Re: [WiX-users] Problem with service install on non English OS



I am not sure if what I suggested would solve your problem, but what I noticed 
from your earlier message, when you use that polish string, you had an error 
which indicated that the characters were not in the code table.

The polish wxl file would specify the correct code table.







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.



This message has been scanned fo

Re: [WiX-users] Problem with service install on non English OS

[David Watson]

Can you post a full install log somewhere - attachments tend to get deleted by 
the mailing system ?

Also the exact error you get when you try and start the service.

You may need to enter a bug.

-Original Message-
From: Stephen I. Woolhead [mailto:s...@gtl.biz] 
Sent: 16 January 2014 23:07
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Problem with service install on non English OS



Just tried this on a Turkish and Russian OS and it installs and runs fine, so 
it does look like there is something strange with the Polish OS.



Not sure where to go next with this



Stephen.



-Original Message-
From: Stephen I. Woolhead [mailto:s...@gtl.biz]
Sent: 16 January 2014 17:05
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Problem with service install on non English OS



I'll go give it a try in some other languages and see if they work.



Cheers,



Stephen.



-Original Message-

From: David Watson [mailto:dwat...@sdl.com]

Sent: 16 January 2014 16:42

To: General discussion about the WiX toolset.

Subject: Re: [WiX-users] Problem with service install on non English OS



The wix properties are populated by an api call at runtime, so it should be 
working fine and they are the correct option in this case.



There may be a specific issue in this language.



Is there anything interesting in the install log?











-Original Message-

From: Stephen I. Woolhead [mailto:s...@gtl.biz]

Sent: 16 January 2014 15:23

To: General discussion about the WiX toolset.

Subject: Re: [WiX-users] Problem with service install on non English OS



Ah, yes get what you mean, that was if I was to hard code the names into the 
wxs, I was hoping I would be able to use the translations WiX supplies at 
install time.



-Original Message-

From: Phill Hogland [mailto:phogl...@rimage.com]

Sent: 16 January 2014 15:04

To: wix-users@lists.sourceforge.net<mailto:wix-users@lists.sourceforge.net>

Subject: Re: [WiX-users] Problem with service install on non English OS



I am not sure if what I suggested would solve your problem, but what I noticed 
from your earlier message, when you use that polish string, you had an error 
which indicated that the characters were not in the code table.

The polish wxl file would specify the correct code table.







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.



This message has been scanned for malware by Websense. www.websense.com

--
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For
Critical Workloads, Development Environments & Everything In Between.
Get a Quote or Start a Free Trial Today. 
http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Problem with service install on non English OS

[David Watson]

The wix properties are populated by an api call at runtime, so it should be 
working fine and they are the correct option in this case.

There may be a specific issue in this language.

Is there anything interesting in the install log?





-Original Message-
From: Stephen I. Woolhead [mailto:s...@gtl.biz] 
Sent: 16 January 2014 15:23
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Problem with service install on non English OS

Ah, yes get what you mean, that was if I was to hard code the names into the 
wxs, I was hoping I would be able to use the translations WiX supplies at 
install time.

-Original Message-
From: Phill Hogland [mailto:phogl...@rimage.com]
Sent: 16 January 2014 15:04
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Problem with service install on non English OS

I am not sure if what I suggested would solve your problem, but what I noticed 
from your earlier message, when you use that polish string, you had an error 
which indicated that the characters were not in the code table. 
The polish wxl file would specify the correct code table.



--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Problem-with-service-install-on-non-English-OS-tp7591820p7591829.html
Sent from the wix-users mailing list archive at Nabble.com.

--
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical 
Workloads, Development Environments & Everything In Between.
Get a Quote or Start a Free Trial Today. 
http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

--
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical 
Workloads, Development Environments & Everything In Between.
Get a Quote or Start a Free Trial Today. 
http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
___
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.



This message has been scanned for malware by Websense. www.websense.com

--
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For
Critical Workloads, Development Environments & Everything In Between.
Get a Quote or Start a Free Trial Today. 
http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Fwd: Creating registry for an application installed outside the current directory structure in WIX file

[David Watson]

If you are not shipping the simulator and it is already on the target machine 
you can use a directory/file search to search the hard disk for it then use the 
resulting property to set the registry value.

See 
http://wixtoolset.org/documentation/manual/v3/howtos/files_and_registry/parentdirectorysearch.html


-Original Message-
From: Suvrajyoti Panda [mailto:suvrajyo...@contata.co.in] 
Sent: 15 January 2014 11:51
To: General discussion about the WiX toolset.
Subject: [WiX-users] Fwd: Creating registry for an application installed 
outside the current directory structure in WIX file

Hi All,

To add to the below issue, i understand that i could use a property that 
includes the registry search. But issue here is that the application 
"StandaloneSimulator.exe" is not something that has been installed on my 
machine(i cannot find it under control panel). The 
D:\Project\ESI\PFW\trunk\StandaloneSimulator\bin exists as it has been checked 
out from SVN.Please let me know in case there are any workarounds.


 Original Message 
Subject:Creating registry for an application installed outside the 
current directory structure in WIX file
Date:   Wed, 15 Jan 2014 12:44:55 +0530
From:   Suvrajyoti Panda 
To: General discussion about the WiX toolset. 




Hi All,

I am creating an wix installer. I want to create a registry entry whose path is 
not under the directory structure created in the WIX file. Below is what i 
intend to do:


   


 
  


  


   
 

The *Value *in the above keys is the path where an application 
"standalonesimulator.exe" is installed.Please suggest if there is anyway that i 
do not have to hardcode this path. I know i can use an include file and fetch 
this path, but again that path will be harcoded in the include file anyways.

Regards,
SuvraJyoti


--
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical 
Workloads, Development Environments & Everything In Between.
Get a Quote or Start a Free Trial Today. 
http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
___
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.



This message has been scanned for malware by Websense. www.websense.com

--
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For
Critical Workloads, Development Environments & Everything In Between.
Get a Quote or Start a Free Trial Today. 
http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Preventing 'v1.0.0.1' install when v1.0.0.0 is present...

[David Watson]

The easiest and cleanest way is to make the daily builds update the build 
number (third part of the msi product version) each build and implement major 
upgrade with a * product code (if you don't already)? Then dev builds always 
install and remove any previous build.

You alter the product code and version already each build by the looks of it...

-Original Message-
From: Tony [mailto:yellowjacketl...@gmail.com] 
Sent: 08 January 2014 16:41
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Preventing 'v1.0.0.1' install when v1.0.0.0 is 
present...

I was aware of the Windows Installer limitation, unfortunately, our daily 
builds do not touch the first three parts of the version, so in our dev labs we 
have to "remember" to uninstall first.  Most folks know this, but with several 
new folks coming onboard and contractors helping here and there, we have been 
burned a few times.  So, I was looking for something to prevent and/or "gently" 
remind the installer that they shouldn't be doing the install.


Thanks for the idea Carter.  I was thinking about something similar, maybe 
using RegLocator/CompLocator against a well-known regvalue/binary.
If found and **BOTH** WIX_UPGRADE_DETECTED and WIX_DOWNGRADE_DETECTED are
**NOT** set, I can assume a re-install is taking place and abort the install.

Thoughts?


On Wed, Jan 8, 2014 at 10:54 AM, Rob Mensching  wrote:

> The Windows Installer chooses not to recognize the revision (the 
> fourth build version) in major upgrades.
>
> -Original Message-
> From: Tony [mailto:yellowjacketl...@gmail.com]
> Sent: Wednesday, January 8, 2014 7:36 AM
> To: WiX Users
> Subject: [WiX-users] Preventing 'v1.0.0.1' install when v1.0.0.0 is 
> present...
>
> NOTE: This is primarily an issue with our daily dev/interim builds.  
> This isn't an issue with QA and/or released builds as they have unique 
> Major.Minor.Build numbers.
>
> I'd like some means to block the install, treat it as an upgrade or 
> even just a simple pop-up "Do you really want to install another 
> version of this package?".
>
> Here's the scenario...
>
> Currently installed application:
> UpgradeCode = 123,
> ProductCode = AAA,
> PackageCode = BBB,
> ProductVersion = 1.0.0.0
>
> I'd like to prevent this package from being installed (or show a 
> pop-up, etc.)...
> UpgradeCode = 123,
> ProductCode = DDD,
> PackageCode = FFF,
> ProductVersion = 1.0.0.1
>
> Is there some way prevent this with FindExistingProducts? AppSearch?
> FileSearch? RegSearch?
>
> If not can I get the ProductVersion of any installed application that 
> has the matching UpgradeCode assign it to a Property and compare 
> versions in a custom action?
>
> Thanks,
> --
> Tony
>
> --
>  Rapidly troubleshoot problems before they affect your 
> business. Most IT organizations don't have a clear picture of how 
> application performance affects their revenue. With AppDynamics, you 
> get 100% visibility into your Java,.NET, & PHP application. Start your 
> 15-day FREE TRIAL of AppDynamics Pro!
> http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.c
> lktrk ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
>
>
> --
>  Rapidly troubleshoot problems before they affect your 
> business. Most IT organizations don't have a clear picture of how 
> application performance affects their revenue. With AppDynamics, you 
> get 100% visibility into your Java,.NET, & PHP application. Start your 
> 15-day FREE TRIAL of AppDynamics Pro!
> http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.c
> lktrk ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>



--
Tony
--
Rapidly troubleshoot problems before they affect your business. Most IT 
organizations don't have a clear picture of how application performance affects 
their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, & 
PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk
___
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 Ho

Re: [WiX-users] Deferred vs. elevation

[David Watson]

Its 0x0800 in CustomAction.Type

-Original Message-
From: Tony [mailto:yellowjacketl...@gmail.com] 
Sent: 03 December 2013 12:43
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Deferred  vs. 
elevation

Thanks.

What flag/option get set in Windows Installer tables when @Impersonate is set 
to 'no'?


On Mon, Dec 2, 2013 at 11:35 PM, Blair Murri  wrote:

> @Impersonate='yes' is the default, so you do need to "turn off 
> impersonation" by explicitly saying "no".
>
> -Blair
>
> > Date: Mon, 2 Dec 2013 15:32:58 -0500
> > From: yellowjacketl...@gmail.com
> > To: wix-users@lists.sourceforge.net
> > Subject: [WiX-users] Deferred  vs.
>  elevation
> >
> > I have a deferred custom action that is failing **UNLESS** I launch 
> > the install "Run as Administrator".  Any ideas why this is happening?
> >
> > 
> >
> >  > DllEntry="Install"  BinaryKey="MyCustomActions" />
> >
> > 
> >   ...
> >   NOT 
> > Installed
> >   ...
> > 
> >
> >
> > Do I need to add the 'Impersonate="no"' attribute to make this work 
> > (is _assume_ "yes" is the default)?
> >
> > >From the logs...
> >
> > ...
> > MSI (c) (D4:60) [19:24:20:051]: Machine policy value 'DisableMsi' is 
> > 1 MSI (c) (D4:60) [19:24:20:051]: Machine policy value 
> > 'AlwaysInstallElevated' is 0 MSI (c) (D4:60) [19:24:20:051]: User 
> > policy value 'AlwaysInstallElevated'
> > is 0
> > MSI (c) (D4:60) [19:24:20:051]: Running product 
> > '{BACFF966-3CEF-4CD7-BE12-D8F6D89D2BE3}' with user privileges. 
> > DisableMsi policy is set to or defaulted to 1. This is the client 
> > and the user does not have full admin token. Evaulation is delayed 
> > until after credentials provided. This install could still be 
> > blocked ...
> > MSI (c) (D4:60) [19:24:20:067]: Note: 1: 2262 2: AdminProperties 3:
> > -2147287038
> > MSI (c) (D4:60) [19:24:20:067]: Machine policy value 
> > 'AlwaysInstallElevated' is 0 MSI (c) (D4:60) [19:24:20:067]: User 
> > policy value 'AlwaysInstallElevated'
> > is 0
> > MSI (c) (D4:60) [19:24:20:067]: Running product 
> > '{BACFF966-3CEF-4CD7-BE12-D8F6D89D2BE3}' with user privileges. 
> > DisableMsi policy is set to or defaulted to 1. This is the client 
> > and the user does not have full admin token. Evaulation is delayed 
> > until after credentials provided. This install could still be 
> > blocked ...
> > MSI (s) (D8:88) [19:24:24:247]: MSI_LUA: Credential Request return = 
> > 0x0 MSI (s) (D8:88) [19:24:24:247]: MSI_LUA: Elevated credential 
> > consent provided. Install will run elevated ...
> > MSI (s) (D8:88) [19:24:24:247]: Note: 1: 2262 2: AdminProperties 3:
> > -2147287038
> > MSI (s) (D8:88) [19:24:24:247]: Machine policy value 
> > 'AlwaysInstallElevated' is 0 MSI (s) (D8:88) [19:24:24:247]: User 
> > policy value 'AlwaysInstallElevated'
> > is 0
> > MSI (s) (D8:88) [19:24:24:247]: Product installation will be 
> > elevated because user provided elevated credentials and product is 
> > being installed per-machine.
> > MSI (s) (D8:88) [19:24:24:247]: Running product 
> > '{BACFF966-3CEF-4CD7-BE12-D8F6D89D2BE3}' with elevated privileges:
> Product
> > is assigned.
> > ...
> > MSI (s) (D8:88) [19:24:24:310]: MSI_LUA: Setting AdminUser property 
> > to 1 because this is the client or the user has already permitted 
> > elevation MSI (s) (D8:88) [19:24:24:310]: PROPERTY CHANGE: Adding 
> > AdminUser
> property.
> > Its value is '1'.
> > MSI (s) (D8:88) [19:24:24:310]: MSI_LUA: Setting MsiRunningElevated 
> > property to 1 because the install is already running elevated.
> > MSI (s) (D8:88) [19:24:24:310]: PROPERTY CHANGE: Adding
> MsiRunningElevated
> > property. Its value is '1'.
> > MSI (s) (D8:88) [19:24:24:310]: PROPERTY CHANGE: Adding Privileged 
> > property. Its value is '1'.
> > ...
> > Action 19:24:25: CustomInstall.
> > MSI (s) (D8:88) [19:24:25:261]: Executing op:
> >
> CustomActionSchedule(Action=CustomInstall,ActionType=1025,Source=BinaryData,Target=Install,CustomActionData=CERTPROPERTY=*.
> > mydomain.net;)
> > MSI (s) (D8:88) [19:24:25:261]: Creating MSIHANDLE (51) of type 
> > 790536
> for
> > thread 4488
> > MSI (s) (D8:E8) [19:24:25:261]: Invoking remote custom action. DLL:
> > C:\Windows\Installer\MSIBD8F.tmp, Entrypoint: Install MSI (s) 
> > (D8!F4) [19:24:25:277]: Creating MSIHANDLE (52) of type 790531
> for
> > thread 1268
> > SFXCA: Extracting custom action to temporary directory:
> > C:\Users\SomeUser\AppData\Local\Temp\MSIBD8F.tmp-\
> > MSI (s) (D8!F4) [19:24:25:277]: Closing MSIHANDLE (52) of type 
> > 790531 for thread 1268 MSI (s) (D8!F4) [19:24:25:308]: Creating 
> > MSIHANDLE (53) of type 790531
> for
> > thread 1268
> > SFXCA: Binding to CLR version v4.0.30319 ...
> > 19:24:25.464--MSI.Install -- Exception
> System.ComponentModel.Win32Exception
> > (0x80004005): Binding failed, see log file for details ...
> >
> >
> >
> > --
> > Tony
> >
> --
> > Rapidly troubleshoot problems before they affect your busi

Re: [WiX-users] Placing XXXSequences in a fragment

[David Watson]

We have several products that share code. These are organised into final .exe 
packages that run a custom bootstrapper/chainer (we started this long before 
burn and have yet to move to burn) that install one or more MSIs.

Each msi has a main wix file that has all the basic settings i.e. product, 
media, features and the directory tree.

Installable files are split into themed areas and are included directly as .wxs 
if they are built in the same branch as the product msi or linked in via a 
binary wixlib if they are built elsewhere (this is used for shared components).

For really small MSIs we sometimes just have everything in one wxs file.

We also have a limited usage of wxi files to share defines between wxs files in 
the same branch.

-Original Message-
From: Tony [mailto:yellowjacketl...@gmail.com] 
Sent: 22 November 2013 13:51
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Placing XXXSequences in a fragment

On Thu, Nov 21, 2013 at 7:26 PM, Rob Mensching  wrote:

> Honestly, when I hear about lots of defines and lots of includes I 
> become suspicious that the code is not leveraging Fragments effectively.
>
That's a good point and just the sort of thing that I'm surprised isn't 
discussed (or blogged) more.  I find project layout one of the most annoying 
aspects (in WiX and/or C#) and find that I'm constantly moving stuff around as 
the project grows.  In WiX, I've tended to group like elements together as 
that's how I know where to locate an issue and extend the behavior (Ex. look 
for feature definitions in the Feature.wxs file, etc.).  I'll take a look at 
the wix source.

>
>
> PS: last I checked, C/C++ and C# are linked together by "case 
> sensitive strings" as well. Not sure why that is such an issue in the WiX 
> toolset.
> 
>
I'm not blaming WiX, but Windows Installer.  Though, I think, an IntelliSense 
type integration would probably resolve many of the issues.  Guess we've become 
spoiled by the tools and take them for granted.  I recently had some C++/CLR 
code in VS2010 to deal with.  VS2010 didn't have IntelliSense and/or syntax 
highlighting for C++/CLR, it was very tedious to work on (thankfully vs2012 
fixed the issue).  I grew-up pre-IntelliSense, but that's one aspect of the 
"good ole' days" I'd rather not see again.  Heck who likes working on C# 
without R#?

>
> -Original Message-
> From: Tony [mailto:yellowjacketl...@gmail.com]
> Sent: Thursday, November 21, 2013 9:59 PM
> To: General discussion about the WiX toolset.
> Subject: Re: [WiX-users] Placing XXXSequences in a fragment
>
> Ideally, I should have my custom actions and feature definitions in my 
> wixlibs, but due to the way our custom action dll is built (and must 
> continue to work with our legacy installers) that isn't very partical.
>
> That said, project layout and build issues is something that I'm 
> surprised isn't discussed more as from past experience it is something 
> that can get out-of-hand quickly.  Espeicaly given that so many items 
> in Windows Installer (and thus WiX) are linked together by "case senstivie 
> strings"
> (ugh!).  Sometimes, I think my .wxi file is larger than my wxs files 
> given all of the  that are needed.
>
> I'd love to hear from others on how they organize small, medium, large 
> and very large installers.
>
>
>
>
> On Wed, Nov 20, 2013 at 8:09 PM, Rob Mensching 
> wrote:
>
> > I group things by functionality not type. Thus my .wxs files are 
> > named for what they are "Toolset.wxs" "MSBuild.wxs" and sometimes 
> > centralize the Folders.wxs (group by type).  I wouldn't do
> CustomActionsAndSequences.wxs.
> >
> > -Original Message-
> > From: Tony [mailto:yellowjacketl...@gmail.com]
> > Sent: Wednesday, November 20, 2013 11:51 PM
> > To: General discussion about the WiX toolset.
> > Subject: Re: [WiX-users] Placing XXXSequences in a fragment
> >
> > Thanks, that's what I thought.  I come up with something, I just 
> > wanted to make sure I wasn't missing some sort of FragmentRef type
> thing...
> >
> > Right now I have...
> >
> > Product.wxs  -- Product, Package, Media, Conditions, UIRef, 
> > FeaturesRef, Windows Installer Properties (ARPXXX, MSIXXX, etc.) 
> > Directories.wxs Features.wxs -- ComponentRefs (all defined in 
> > several
> > wixlibs) CustomActionsAndSequences.wxs -- Binary, CustomAction, 
> > InstallExecuteSequence, InstallUISequence
> > 2-3 lUI.wxs (based off of a slightly modified WixUI_FeatureTree
> > pattern)
> >
> > Haven't decided where I'll define my properties.  Maybe a 
> &g

Re: [WiX-users] Question re WIX other MSI installer tools...

[David Watson]

They are right, burn is a tool to allow you to collect data and chain some MSIs 
silently, but you will need to make a custom BA to get the most from it.

The visual studio installer is a custom burn BA that does just that.

-Original Message-
From: StevenOgilvie [mailto:sogil...@msn.com] 
Sent: 15 November 2013 17:49
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Question re WIX other MSI installer tools...

Hi,

I work for a small company and we are using WIX for our Enterprise software.
We have a Server application with Services and use a SQL Server database.
Our Client Software connects to the Server/Database to get client configuration 
info via the Services that is also installed with the Client software.

So we use SQL Server/.NET 4.0/IIS 7.x+/NServiceBus + In house services

It is partly my fault that I didn’t communicate what WIX can/cannot do what 
Burn can/cannot do.

Product Management had a “vision” of a software install of our Server compared 
to the MS SQL Server install (yuck)… an executable asks questions and then the 
MSI’s run silently using the info passed as MSI properties… And to look “sexy” 
like the MS Visual Studio 2012 install.

We have pre requisites that we install… and Burn is an awesome tool, but the UI 
is how to say politely “bland”. I have been using Neil’s Extended BA DLL and 
making modifications to suit our needs which has helped…

I have tried to convey that burn is not meant as a “tool to gather information 
and then kick off MSI” but rather a tool to install pre requisites and install 
our software product.

There has been talk that maybe WIX isn’t the tool we should use but a COTS 
application like InstallShield etc… I have tried to convey that, that will not 
solve the issue of what they want.

As well InstallShield and other tools are expensive, support is expensive, 
upgrades are expensive…

I try to tell them that yes you can have an information gathering tool, but a 
COTS application will not do that… that would have to be a in house developed 
tool that will take some time and effort…

Have I missed anything else?

Thanks,

Steve
Btw I really enjoy using WIX, I was an InstallShield/Wise/InstallAnywhere
user and I have been converted J




--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Question-re-WIX-other-MSI-installer-tools-tp7590687.html
Sent from the wix-users mailing list archive at Nabble.com.

--
DreamFactory - Open Source REST & JSON Services for HTML5 & Native Apps OAuth, 
Users, Roles, SQL, NoSQL, BLOB Storage and External API Access Free app 
hosting. Or install the open source package on any LAMP server.
Sign up and see examples for AngularJS, jQuery, Sencha Touch and Native!
http://pubads.g.doubleclick.net/gampad/clk?id=63469471&iu=/4140/ostg.clktrk
___
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.


This message has been scanned for malware by Websense. www.websense.com
--
DreamFactory - Open Source REST & JSON Services for HTML5 & Native Apps
OAuth, Users, Roles, SQL, NoSQL, BLOB Storage and External API Access
Free app hosting. Or install the open source package on any LAMP server.
Sign up and see examples for AngularJS, jQuery, Sencha Touch and Native!
http://pubads.g.doubleclick.net/gampad/clk?id=63469471&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Help Retrieve full File Path for a File from a CustomAction

[David Watson]

Anything that is customizable is regarded as user data and should be installed 
to a safe non-live location and then copied to the live location during your 
programs first run configuration step (or post install custom action).

Your confg tool/CA then knows where the template source is (which is up to date 
as it has not been modified by the user) and can decide whether to overwrite 
the current templates or not.



-Original Message-
From: Carter Young [mailto:ecyo...@grandecom.net] 
Sent: 15 November 2013 16:12
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Help Retrieve full File Path for a File from a 
CustomAction

Provide 1 base theme for every new version of your product.  In your SetupUI 
advise customer that there are more themes available at your website.  Package 
all the unversioned ones on said server to create a revenue stream...Quoting 
tyler.w.r...@accenture.com:

> Hello,
>
> We have an installer that installs a website and all of its 
> content including several themes. Now during our system testing they 
> have discovered that since the themes aren't versioned they don't 
> always get upgraded and some of these files are editable by the 
> customer. So what I was told to do is to grab all the unversioned 
> files and back them up so that the customer can merge their changes 
> back in after the install. I do know a lot of our customers keep their 
> themes in version control and just merge them after the install, but 
> some don't.
>
> So my thoughts were to query the file table and grab anything that 
> doesn't have a version and back it up, but how do I resolve the full 
> install path for the current running install? Belive me if there is a 
> better way to go about this I would love to hear it because I just 
> feel wrong doing this.
>
> Tyler Reid | Operations and Infrastructure | Accenture Software | P&C 
> Insurance
> 1807 Jones Street | Bolivar, MO 65613| USA
> Office: +cc.xxx.xxx. | Fax: 417.777.3792
> E-Mail:  
> tyler.w.r...@accenture.com | 
> www.accenture.com/pcsoftware
>
>
>
> 
> This message is for the designated recipient only and may contain  
> privileged, proprietary, or otherwise confidential information. If  
> you have received it in error, please notify the sender immediately  
> and delete the original. Any other use of the e-mail by you is  
> prohibited.
>
> Where allowed by local law, electronic communications with Accenture  
> and its affiliates, including e-mail and instant messaging  
> (including content), may be scanned by our systems for the purposes  
> of information security and assessment of internal compliance with  
> Accenture policy.
>
> __
>
> www.accenture.com
> --
> DreamFactory - Open Source REST & JSON Services for HTML5 & Native Apps
> OAuth, Users, Roles, SQL, NoSQL, BLOB Storage and External API Access
> Free app hosting. Or install the open source package on any LAMP server.
> Sign up and see examples for AngularJS, jQuery, Sencha Touch and Native!
> http://pubads.g.doubleclick.net/gampad/clk?id=63469471&iu=/4140/ostg.clktrk
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
>




--
DreamFactory - Open Source REST & JSON Services for HTML5 & Native Apps
OAuth, Users, Roles, SQL, NoSQL, BLOB Storage and External API Access
Free app hosting. Or install the open source package on any LAMP server.
Sign up and see examples for AngularJS, jQuery, Sencha Touch and Native!
http://pubads.g.doubleclick.net/gampad/clk?id=63469471&iu=/4140/ostg.clktrk
___
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.



This message has been scanned for malware by Websense. www.websense.com

--
DreamFactory - Open Source REST & JSON Services for HTML5 & Native Apps
OAuth, Users, Roles, SQL, NoSQL, BLOB Storage and External API Access
Free app hosting. Or install the open source package on any LAMP server.
Sign up and see examples for AngularJS, jQuery, Sencha Touch and Native!
http://puba

Re: [WiX-users] uninstalling files

[David Watson]

If you mean to share files between two different product MSIs then you need to 
author them carefully to make sure that they share the same component guids.

-Original Message-
From: Daniyyel [mailto:daniel.bed...@freenet.de] 
Sent: 15 November 2013 12:09
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] uninstalling files

As far as I know there is no downgrade option. It would only go if you create
a patch (MSP), install it and then you can remove the patch over a command
line. That would be a downgrade.



--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/uninstalling-files-tp7590670p7590671.html
Sent from the wix-users mailing list archive at Nabble.com.

--
DreamFactory - Open Source REST & JSON Services for HTML5 & Native Apps
OAuth, Users, Roles, SQL, NoSQL, BLOB Storage and External API Access
Free app hosting. Or install the open source package on any LAMP server.
Sign up and see examples for AngularJS, jQuery, Sencha Touch and Native!
http://pubads.g.doubleclick.net/gampad/clk?id=63469471&iu=/4140/ostg.clktrk
___
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.



This message has been scanned for malware by Websense. www.websense.com

--
DreamFactory - Open Source REST & JSON Services for HTML5 & Native Apps
OAuth, Users, Roles, SQL, NoSQL, BLOB Storage and External API Access
Free app hosting. Or install the open source package on any LAMP server.
Sign up and see examples for AngularJS, jQuery, Sencha Touch and Native!
http://pubads.g.doubleclick.net/gampad/clk?id=63469471&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Create a Empty Folders through Wix

[David Watson]

Oops never noticed that :)

-Original Message-
From: Chaitanya [mailto:chaita...@pointcross.com] 
Sent: 25 October 2013 12:13
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Create a Empty Folders through Wix

In heat Command i added the tag like -ke after that it is working fine.it is 
creating empty folders.


On 25-10-2013 16:22, David Watson wrote:
> Create a 0kb placeholder files in your empty directories, if you want them to 
> be included automatically.
>
> Would be an interesting addition to heat to allow empty folder harvesting.
>
> -Original Message-
> From: Chaitanya [mailto:chaita...@pointcross.com]
> Sent: 25 October 2013 10:43
> To: General discussion about the WiX toolset.
> Subject: Re: [WiX-users] Create a Empty Folders through Wix
>
> we can create.but i dont want any manual actions in .wxs file..
>
>
> On 25-10-2013 13:30, Dirk Raeder wrote:
>> Hi Chaitanya,
>>
>> we have to create several empty folders, too. We simply create the
>> directory structure in our .wxs files and add a Component inside each
>> empty folder. The Component has the attributes KeyPath=no,
>> NeverOverwrite=no, Permanent=no, Win64=yes (we have a 64bit-only
>> installer) and Location=local.
>>
>> In the Component, we define the CreateFolder element.
>> Additionally, we define some permissions for certain users with the
>> util:PermissionEx element.
>>
>> 
>>   > Guid="DEADBEEF-BEEF-BEEF-BEEF-C0FFEEBABE00" KeyPath="no"
>> NeverOverwrite="no" Permanent="no" Win64="yes" Location="local">
>> 
>>   > Delete="yes" Read="yes" ReadAttributes="yes"
>> ReadExtendedAttributes="yes" ReadPermission="yes" Traverse="yes"
>> GenericRead="yes" GenericWrite="yes" User="[USERNAME]" />
>> 
>>   
>> 
>>
>>
>> Kind regards,
>>
>> Dirk Räder
>>
>>
>>
>> On 2013-10-25 13:12, Chaitanya wrote:
>>> Hi,
>>> In my Source file I am having a lot of empty folders.But,it is not
>>> creating the empty folders through "Heat or WixEdit".How to create an
>>> empty folders through wix.
>>>
>>> --
>>> Thanks & Regards,
>>> Chaitanya.
>>>
>>>
>>> -
>>> - October Webinars: Code for Performance Free Intel webinars
>>> can help you accelerate application performance.
>>> Explore tips for MPI, OpenMP, advanced profiling, and more. Get the
>>> most from the latest Intel processors and coprocessors. See abstracts
>>> and register >
>>> http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.
>>> clktrk ___
>>> WiX-users mailing list
>>> WiX-users@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/wix-users
>
> --
> Thanks & Regards,
> Chaitanya.
>
>
> --
> October Webinars: Code for Performance
> Free Intel webinars can help you accelerate application performance.
> Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
> the latest Intel processors and coprocessors. See abstracts and register >
> http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.clktrk
> ___
> 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.
>
>
> --
> October Webinars: Code for Performance
> Free Intel webinars can help you accelerate application performance.
> Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
> the latest Intel processors and coprocessors. See abstracts and register >
> http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/o

Re: [WiX-users] Create a Empty Folders through Wix

[David Watson]

Create a 0kb placeholder files in your empty directories, if you want them to 
be included automatically.

Would be an interesting addition to heat to allow empty folder harvesting.

-Original Message-
From: Chaitanya [mailto:chaita...@pointcross.com] 
Sent: 25 October 2013 10:43
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Create a Empty Folders through Wix

we can create.but i dont want any manual actions in .wxs file..


On 25-10-2013 13:30, Dirk Raeder wrote:
> Hi Chaitanya,
>
> we have to create several empty folders, too. We simply create the 
> directory structure in our .wxs files and add a Component inside each 
> empty folder. The Component has the attributes KeyPath=no, 
> NeverOverwrite=no, Permanent=no, Win64=yes (we have a 64bit-only
> installer) and Location=local.
>
> In the Component, we define the CreateFolder element.
> Additionally, we define some permissions for certain users with the 
> util:PermissionEx element.
>
> 
>   Guid="DEADBEEF-BEEF-BEEF-BEEF-C0FFEEBABE00" KeyPath="no"
> NeverOverwrite="no" Permanent="no" Win64="yes" Location="local">
>
>   Delete="yes" Read="yes" ReadAttributes="yes"
> ReadExtendedAttributes="yes" ReadPermission="yes" Traverse="yes"
> GenericRead="yes" GenericWrite="yes" User="[USERNAME]" />
>
>  
>
>
>
> Kind regards,
>
> Dirk Räder
>
>
>
> On 2013-10-25 13:12, Chaitanya wrote:
>> Hi,
>> In my Source file I am having a lot of empty folders.But,it is not 
>> creating the empty folders through "Heat or WixEdit".How to create an 
>> empty folders through wix.
>>
>> --
>> Thanks & Regards,
>> Chaitanya.
>>
>>
>> -
>> - October Webinars: Code for Performance Free Intel webinars 
>> can help you accelerate application performance.
>> Explore tips for MPI, OpenMP, advanced profiling, and more. Get the 
>> most from the latest Intel processors and coprocessors. See abstracts 
>> and register > 
>> http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.
>> clktrk ___
>> WiX-users mailing list
>> WiX-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/wix-users


--
Thanks & Regards,
Chaitanya.


--
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from 
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.clktrk
___
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.


--
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from 
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] returned actual error code 1154 from custom action

[David Watson]

Check out this 
http://stackoverflow.com/questions/3560370/custom-action-in-c-sharp-used-via-wix-fails-with-error-1154

Why are you not using the service control element to ensure the service is 
stopped?
http://wixtoolset.org/documentation/manual/v3/xsd%5Cwix%5Cservicecontrol.html


-Original Message-
From: Steven Ogilvie [mailto:steven.ogil...@titus.com] 
Sent: 18 October 2013 13:37
To: General discussion about the WiX toolset.
Subject: [WiX-users] returned actual error code 1154 from custom action

Hi,

I am calling a custom action on uninstall just to ensure that our 5 services 
are actually stopped before we try to remove them...

However I am getting an error that confuses me since everything looks kosher...

Anyone see any issues with what I am doing?

Here is the error from the log file:
MSI (s) (6C:D4) [23:30:16:875]: Executing op: 
ActionStart(Name=CA_STOPESSERVICE.A54690A6_C7B5_477D_ADAF_916A4A173FDF,Description=CA:
 Stopping TITUS Enterprise Settings Service...,)
MSI (s) (6C:D4) [23:30:16:875]: Executing op: 
CustomActionSchedule(Action=CA_STOPESSERVICE.A54690A6_C7B5_477D_ADAF_916A4A173FDF,ActionType=3137,Source=BinaryData,Target=StopServiceForUninstall,CustomActionData=TITUS.Enterprise.Settings.Host|)
MSI (s) (6C:28) [23:30:16:937]: Invoking remote custom action. DLL: 
C:\Windows\Installer\MSIF6FB.tmp, Entrypoint: StopServiceForUninstall
CustomAction CA_STOPESSERVICE.A54690A6_C7B5_477D_ADAF_916A4A173FDF returned 
actual error code 1154 but will be translated to success due to continue marking


Custom Action:




Installed
Installed

DTF Custom Action DLL C#

public static ActionResult StopServiceForUninstall(Session session)
{
var serviceName = string.Empty;
try
{
if (session == null)
{
throw new ArgumentNullException("session");
}

var tempString = GetSessionProperty(session, 
"CustomActionData", false);
var parts = tempString.Split(new[] { '|' });
serviceName = parts[0];

var sc = new ServiceController { ServiceName = serviceName };

if (sc.Status == ServiceControllerStatus.Running)
{
// Stop the service
try
{
// Stop the service.
sc.Stop();
sc.WaitForStatus(ServiceControllerStatus.StopPending, 
TimeSpan.FromSeconds(30));
}
catch (TimeoutException exception)
{
WriteErrorLogInstall(session, "TimeoutException: could 
not stop the " + serviceName + " service.", exception, true);
}
}
}
catch (Exception ex)
{
WriteErrorLogInstall(session, "Could not stop service: " + 
serviceName + " .", ex, true);
}
return ActionResult.Success;
}

Thanks,

Steve


--
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from 
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60135031&iu=/4140/ostg.clktrk
___
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.


--
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from 
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60135031&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Id for programdata folder

[David Watson]

The windows installer property reference is a good resource to know.

http://msdn.microsoft.com/en-us/library/windows/desktop/aa370905(v=vs.85).aspx


-Original Message-
From: Wesley Manning [mailto:wmann...@dynagen.ca] 
Sent: 11 October 2013 17:10
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Id for programdata folder

No, there is a standard Id:

  

Note: on windows xp this folder is located somewhere else which you probably 
know.

-Original Message-
From: Sander Obdeijn [mailto:i...@sanderobdeijn.nl] 
Sent: October-11-13 12:33 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Id for programdata folder

Hi guys and gals

I have just started using wix. And i'm impressed, at first it seemed quite 
daunting but i'm getting the hang of it. One thing i'm stuck on atm I have to 
copy a file into the c:/programdata/ folder. Is there a standard id for this 
folder? Or do I have to treat it as a custom folder. I'm using wix 3.7. I have 
seached on internet and found the same question but no answer.

Thanks upfront for any help you can offer.

Kind regards,

Sander Obdeijn
--
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from 
the latest Intel processors and coprocessors. See abstracts and register > 
http://pubads.g.doubleclick.net/gampad/clk?id=60134071&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

--
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from 
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60134071&iu=/4140/ostg.clktrk
___
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.


--
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from 
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60134071&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] How to compare strings from a Registrykey

[David Watson]

The evaluation order of  launch conditions cannot be guaranteed.

Also they are conditions on which to launch the msi so if the condition is true 
the message is NOT displayed.
I can't see your conditions to see if that is an issue for you.
If any launch conditions fail  the rest of the conditions are not evaluated.

See 
http://msdn.microsoft.com/en-us/library/windows/desktop/aa369752(v=vs.85).aspx


-Original Message-
From: sonhja [mailto:smol...@facephi.com] 
Sent: 13 September 2013 13:04
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] How to compare strings from a Registrykey

I'm trying to build a simple installer with *Wix* that does some staff due to a 
*RegistryValue* that I insert. I have a registry value called *Number* with a 
value of 10.

![enter image description here][1]

I used a *string value* with *REG_SZ* type. With that, as far as I understand, 
my variable will have the value *10* and not *#10*, like other types seem to do.

So with my `WiX` installer I try to find that registry value like this:

 
 
   
 

 
   
 
 
   
 

So I guess this will do a basic comparison from the registry value like
this:

if ( > myNumber)
 ShowEmergentWindow saying: "Lower number"
else
 ShowEmergentWindow saying: "Higher number"

But this check doesn't work well. Even if I put the same value on the registry 
and inside my *myNumber*, it always launches *the first written condition*. I 
mean, if I change the order of the conditions, the first one is *ALWAYS* 
launched.

I'm sure I'm misunderstanding something related with registry values comparison 
using *WiX installer*, but I don't know why this doesn't work as expected. Any 
idea?




--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/How-to-compare-strings-from-a-Registrykey-tp7588946.html
Sent from the wix-users mailing list archive at Nabble.com.

--
How ServiceNow helps IT people transform IT departments:
1. Consolidate legacy IT systems to a single system of record for IT 2. 
Standardize and globalize service processes across IT 3. Implement zero-touch 
automation to replace manual, redundant tasks 
http://pubads.g.doubleclick.net/gampad/clk?id=5127&iu=/4140/ostg.clktrk
___
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.


--
How ServiceNow helps IT people transform IT departments:
1. Consolidate legacy IT systems to a single system of record for IT
2. Standardize and globalize service processes across IT
3. Implement zero-touch automation to replace manual, redundant tasks
http://pubads.g.doubleclick.net/gampad/clk?id=5127&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] [WIX] How to installing same MSI file twice

[David Watson]

You don't.

You have to change the maintenance mode UI to be what you want.

-Original Message-
From: dileep s [mailto:dileep.sanamp...@gmail.com] 
Sent: 10 September 2013 12:44
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] [WIX] How to installing same MSI file twice

Hi All,

I have created MSI using WIX for installing printer driver.

When I installed MSI first time, it was installed the printer driver correctly.

When I want to install the other printer driver using same MSI file, it shows 
Maintenance mode UI.

How to show the Installation UI dialogs instead of Maintenance mode UI, when 
second time MSI is clicked?


Thanks in advance...

Regards,
Dileep
--
How ServiceNow helps IT people transform IT departments:
1. Consolidate legacy IT systems to a single system of record for IT 2. 
Standardize and globalize service processes across IT 3. Implement zero-touch 
automation to replace manual, redundant tasks 
http://pubads.g.doubleclick.net/gampad/clk?id=5127&iu=/4140/ostg.clktrk
___
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.


--
How ServiceNow helps IT people transform IT departments:
1. Consolidate legacy IT systems to a single system of record for IT
2. Standardize and globalize service processes across IT
3. Implement zero-touch automation to replace manual, redundant tasks
http://pubads.g.doubleclick.net/gampad/clk?id=5127&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Bootstrapper step conditional execution

[David Watson]

You can host your ui in the bootstrapper ask all the questions, then install 
sqlexpress if needed then run your msi with relevant properties to install the 
services/populate the database.

Dave

-Original Message-
From: Tunney, Stephen [mailto:stephen.tun...@nuance.com] 
Sent: 09 September 2013 15:55
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Bootstrapper step conditional execution

I'm all ears if you know of anything off the top of your head.  The requirement 
from up on high is to ask questions to determine if the user wants/needs 
SQLExpress installed locally and afterwards install our database via canned 
scripts and start our services.


-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: Monday, September 09, 2013 10:34 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Bootstrapper step conditional execution

You'd probably need a custom BA to do all that. There are probably easier ways 
to accomplish what you are trying to do as well.


On Mon, Sep 9, 2013 at 7:26 AM, Tunney, Stephen
wrote:

> Hello oh great and powerful Rob :)  It is a pleasure to get an email 
> from you.
>
> I've been working with a bootstrapper project but I'm curious as to 
> how I can have the chained EXE project inspect the registry AFTER the 
> initial call to my product MSI has completed.
>
> I think that my bootstrapper will work like this:
>
> 1) Call product MSI with a property that asks all of the questions and 
> copies all files/registry items to disk
> 2) Conditionally call SQLExpress based on a stored property or 
> registry entry
> 3) Call repair on my original MSI to have the services started and the 
> db scripts executed
>
> -Original Message-
> From: Rob Mensching [mailto:r...@robmensching.com]
> Sent: Friday, September 06, 2013 12:00 PM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Bootstrapper step conditional execution
>
> Burn can handle that very easily.
>
>
> On Fri, Sep 6, 2013 at 5:41 AM, Tunney, Stephen
> wrote:
>
> > Hello everyone,
> >
> > I think it has been quite a few years since I've posted a question 
> > to this forum.  I have moved to a new company and I am getting them 
> > out of InstallShield hell :)
> >
> > My boss has come to me with a unique requirement for our installer.
> > We would like to wrap a "demo" mode into our core installer.  This 
> > demo mode will be chosen from the main UI and with it an instance of 
> > SQLEXPRESS will be installed AFTER UI interactions have completed if 
> > it does not already exist.
> >
> > So basically I want the execution of an exe package to be driven by 
> > the value of a property or registry value modified by the msi 
> > package executed successfully before it.
> >
> > Does anyone have any thoughts of how to do this?  Basically it is a 
> > conditional prerequisite :)
> >
> > Cheers,
> > Stephen
> >
> >
> > 
> > --
> >  Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 
> > 2012, more!
> > Discover the easy way to master current and previous Microsoft 
> > technologies and advance your career. Get an incredible 1,500+ hours 
> > of step-by-step tutorial videos with LearnDevNow. Subscribe today 
> > and
> save!
> > http://pubads.g.doubleclick.net/gampad/clk?id=58041391&iu=/4140/ostg
> > .c lktrk ___
> > WiX-users mailing list
> > WiX-users@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/wix-users
> >
> >
>
> --
>  Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 
> 2012, more!
> Discover the easy way to master current and previous Microsoft 
> technologies and advance your career. Get an incredible 1,500+ hours 
> of step-by-step tutorial videos with LearnDevNow. Subscribe today and save!
> http://pubads.g.doubleclick.net/gampad/clk?id=58041391&iu=/4140/ostg.c
> lktrk ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
>
> --
>  Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 
> 2012, more!
> Discover the easy way to master current and previous Microsoft 
> technologies and advance your career. Get an incredible 1,500+ hours 
> of step-by-step tutorial videos with LearnDevNow. Subscribe today and save!
> http://pubads.g.doubleclick.net/gampad/clk?id=58041391&iu=/4140/ostg.c
> lktrk ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
>
--
Learn the latest--Visual St

Re: [WiX-users] Wix tool deployment

[David Watson]

I don't think there are issues with re-distributing the wix toolset as I have
seen third party tools do that.
Double check the license.
I would personally just link to the site with instructions or if needed
distribute the entire toolset.

Dave

-Original Message-
From: biswajitbiee [mailto:biswajitb...@gmail.com] 
Sent: 30 August 2013 06:59
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Wix tool deployment

Can anybody update me with the information requested ?



--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Wix-tool-deploy
ment-tp7588421p7588627.html
Sent from the wix-users mailing list archive at Nabble.com.

-
-
Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more!
Discover the easy way to master current and previous Microsoft technologies
and advance your career. Get an incredible 1,500+ hours of step-by-step
tutorial videos with LearnDevNow. Subscribe today and save!
http://pubads.g.doubleclick.net/gampad/clk?id=58040911&iu=/4140/ostg.clktrk
___
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.


--
Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more!
Discover the easy way to master current and previous Microsoft technologies
and advance your career. Get an incredible 1,500+ hours of step-by-step
tutorial videos with LearnDevNow. Subscribe today and save!
http://pubads.g.doubleclick.net/gampad/clk?id=58040911&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] How to remove custom application with malformed uninstall package

[David Watson]

Make a minor update msi that fixes the issue and get your users (or write a
stub that) runs it from the command line with the repair and recache msi
options.

msiexec /fv your.msi /l*v log.txt



-Original Message-
From: John Ludlow [mailto:john.ludlow...@gmail.com] 
Sent: 28 August 2013 10:34
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] How to remove custom application with malformed
uninstall package

You have a couple of options:

Firstly, there's the MSI Cleanup Utility

http://gallery.technet.microsoft.com/MSI-cleanup-utility-3889c8db

This is an old tool which I thought had been retired, but it's come in very
handy. Note that this will not perform any uninstall operations or any MSI
logic at all. It basically hunts round the MSI registry for evidence of your
install and removes it. Any of your own registry entries or files will not be
removed.

But it's good for cleaning up a broken install.

Secondly, there's it's younger sibling, in the form of a FixIt
troubleshooter:

http://support.microsoft.com/mats/Program_Install_and_Uninstall

This will scan for installs it thinks have problems, ask you a few questions,
then do pretty much the same as the cleanup utility above, though it's
supposed to do a more intelligent job.

Thirdly, you can find the appropriate MSI in the c:\windows\installer cache,
remove the offending action from the sequence using orca.exe and then try to
uninstall it again.

Lastly, I know some people who swear by CCleaner for this kind of thing:
http://www.piriform.com/ccleaner

Hope one of those suggestions helps.

John


On 28 August 2013 10:13, Simon Gerhold  wrote:

> I created a setup project with Wix Toolset, which does something like this:
>
>   *   install (into ProgramFiles/MyApp, Desktop shortcut, StartMenu,...)
>   *   create a folder ProgramFiles/MyApp/InstallFolder
>   *   create some files in the folder ProgramFiles/MyApp/InstallFolder
>   *   run a powershell script, which installs some COM+ components
> In the ProgramFiles/MyApp/InstallFolder is also a powershell script, 
> which removes my COM+ applications (regsvcs /u). This script is 
> executed as a custom action on uninstall. But here I made a mistake - 
> the custom action had the attribute After="RemoveFiles" (it should of 
> course be Before="RemoveFiles"). Now when I try to uninstall on my 
> application, the uninstall process terminates with the exception 
> "There is a problem with this Windows installer package. A program run 
> as part of the setup did not finish as expected. Contact your support 
> personnel or package vendor.". The same exception occurs if I try to
install/repair/change my application...
> Is there any possibility to uninstall my application without the last
> (faulty) custom action? Or to 'overinstall' it somehow?
> Simon
>
>
> Simon Gerhold, razvojni inženir / Development Engineer Cetis d.d., 
> Čopova 24, 3000 Celje, Slovenia - EU, T: +386 3 4278 785, F: +386
> 3 4278 651, www.cetis.si
>
>
> --
>  Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 
> 2012, more!
> Discover the easy way to master current and previous Microsoft 
> technologies and advance your career. Get an incredible 1,500+ hours 
> of step-by-step tutorial videos with LearnDevNow. Subscribe today and save!
> http://pubads.g.doubleclick.net/gampad/clk?id=58040911&iu=/4140/ostg.c
> lktrk ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
-
-
Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more!
Discover the easy way to master current and previous Microsoft technologies
and advance your career. Get an incredible 1,500+ hours of step-by-step
tutorial videos with LearnDevNow. Subscribe today and save!
http://pubads.g.doubleclick.net/gampad/clk?id=58040911&iu=/4140/ostg.clktrk
___
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.
--
Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more!
Discover the easy way to master current and previous Microsoft technologies
and advance your career. Get an incredible 1,500+ hours of step-by-step
tutorial videos with LearnDevN

Re: [WiX-users] how to reference an element in heat generated file?

[David Watson]

I think -suid manages clashing ids if you only have one pass but not if you
run heat multitple times to generate fragments.

Dave

-Original Message-
From: jo...@msli.com [mailto:jo...@msli.com] 
Sent: 16 August 2013 09:29
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] how to reference an element in heat generated file?

OK.  I'll construct a transform, but this seems like a daunting task.

I always have to run heat after every check out.  The developers can change
anything over time, branches, and releases, and the build isn't supposed to
break, so the smoothest policy for me is to limit assumptions by always
running heat against what ever is present.

I couldn't figure out how to modify the Component in the heat generated file,
so my transform chops it out, and I manually create the Component in another
file, with file associations.  This seems to be the easiest way to solve the
problem and I don't have to be an xslt wizard.

First, my Product element contains:

  
   


  

  
  

  


Second, another .wxs file contains the Component for my exe and file
associations:

  

  
  
  

  

  

  


My xslt transformation file cuts out the exe Component from the  http://www.w3.org/1999/XSL/Transform";
xmlns:wix="http://schemas.microsoft.com/wix/2006/wi";>
  
  

  

  
  
  
  
  



Commands:

heat.exe dir dist -dr INSTALLDIR -cg group_ProductFiles -gg -g1 -sf -srd -var
env.dist -t .\wix_project\MyProgram.filter2.xsl -out
.\wix_project\MyProgram.resource_list.wxs 

candle.exe -dwxi_variables=MyProgram.variables.wxi -i MyProgram.variables.wxi
-v -arch x86 -trace -out wixobj/ .\wix_project\MyProgram.wxs
.\wix_project\MyProgram.resource_list.wxs
.\wix_project\MyProgram.shortcuts.wxs 

light.exe -out foo.msi -b dist -ext WixUIExtension wixobj/MyProgram.wixobj
wixobj/MyProgram.resource_list.wixobj wixobj/MyProgram.shortcuts.wixobj 

And it all worked.

I think the documentation could really benefit from a practical example
like this, so people don't have to search though the mailing list
threads.

On Thu, 2013-08-15 at 16:27 -0700, Blair Murri wrote:
> That's why I use a transform to insert the file association code under the
file element and I don't harvest my icons.
> 
> To ne fair, harvesting was originally intended to be performed just once,
not each build. Most projects don't need to be harvested each time, but there
are systems that do require it.
> 
> 
> "jo...@msli.com"  wrote:
> 
> If heat generates a file with unique identifiers for each element, is it
> true that the Id of a particular element can't be referenced elsewhere,
> as there is no way to determine the correct name?
> 
> I am facing this situation by trying to create a file association, where
> my exe has an Id that changes every time I run heat, yet creating a file
> association requires a TargetFile and Icon that refer to an Id, and not
> the name of the file it self.
> 
> The following is a file association, but the '?' are the areas of
> interest:
> 
>   
> 
>   
> 
> 
> A hack is calling heat.exe with argument -suid, which sets the Id = file
> name, and I simply use the file name in TargetFile="file_name.exe", but
> it has issues if two files have the same name in different areas (i
> think).
> 
> Since heat is part of wix it seems like in the design of how all the
> parts fit together there must be a better way.
> 
> 
> NOTICE: This email may contain confidential information.  Please see
http://www.meyersound.com/confidential/ for our complete policy.
> 
>
-
-
> Get 100% visibility into Java/.NET code with AppDynamics Lite!
> It's a free troubleshooting tool designed for production.
> Get down to code-level detail for bottlenecks, with <2% overhead.
> Download for free and get started troubleshooting in minutes.
> http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
> 
>
-
-
> Get 100% visibility into Java/.NET code with AppDynamics Lite!
> It's a free troubleshooting tool designed for production.
> Get down to code-level detail for bottlenecks, with <2% overhead. 
> Download for free and get started troubleshooting in minutes. 
> http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users



-
-
Get 100% visibility into Java/.NET code with AppDynamics Lite!
It's a free troubleshooting tool designed for prod

Re: [WiX-users] Custom installation in Wix Patch

[David Watson]

The latter behaviour is automatic, only installed features are patched.

-Original Message-
From: Swaroop Kare [mailto:swaroop.k...@ifdspercana.com] 
Sent: 14 August 2013 10:12
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Custom installation in Wix Patch

In the wix major upgrade, I have a set of features and the end user has the
option to install either typical, custom or complete features.

 

In case of wix patch release, is it possible to give the user the same option
of typical, custom or complete installation type.

 

Else during the deployment can wix patch detect which features to be deployed
based on the installation done in a system. i.e if a system is installed with
typical installation then the wix patch update only those components that
belong to typical installation. and if a system has a custom installation
with only feature X then the patch update should update only those components
that belong to feature X.

 

Thanks

Wix Developer


This email and any files transmitted with it are confidential and intended
solely for the use of the individual or entity to which it is addressed and
may contain information which is privileged, confidential or prohibited from
disclosure or unauthorised use. You are hereby notified that any use, any
form of reproduction, dissemination, copying, disclosure, modification,
distribution and/or publication of this e-mail message or its attachments
other than by it's intended recipient is strictly prohibited by the sender.
If you have received this email in error, please notify the system manager by
email at ad...@ifdspercana.com Please note that any views or opinions
presented in this email are solely those of the author and do not necessarily
represent those of the company. Finally, this email has been scanned for the
presence of viruses. The recipient should also check this email and any
attachments for the presence of viruses. The company accepts no liability for
any damage caused by any virus transmitted by this email
_
_

IFDS Percana Group Limited, no. 307152, is registered in Ireland at 16 Joyce
Way, Park West Business Park, Dublin 12, Ireland.
Directors: Eugene Larmon, Patrick Concannon, William Slattery, Paul O'Neil
(UK), Simon Hudson-Lund (UK) and Stephen Parkinson (UK) IFDS Percana
International Managed Services Limited, no. 368022, is regulated by the
Central Bank of Ireland. Registered in Ireland at 16 Joyce Way, Park West
Business Park, Dublin 12, Ireland.
IFDS Percana International Managed Services Limited is a wholly owned
subsidiary of IFDS Percana Group Limited and provides support services to the
life and pensions industry.
Directors: Eugene Larmon, Patrick Concannon, Stephen Parkinson (UK) and Paul
O'Neil (UK).
www.ifdspercana.com

__
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
__
-
-
Get 100% visibility into Java/.NET code with AppDynamics Lite!
It's a free troubleshooting tool designed for production.
Get down to code-level detail for bottlenecks, with <2% overhead. 
Download for free and get started troubleshooting in minutes. 
http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk
___
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.


--
Get 100% visibility into Java/.NET code with AppDynamics Lite!
It's a free troubleshooting tool designed for production.
Get down to code-level detail for bottlenecks, with <2% overhead. 
Download for free and get started troubleshooting in minutes. 
http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Adding a new dependent file to shared component without breaking component rules

[David Watson]

When we release side by side versions of products we have to
reversion/relocate(re-guid if com) all our shared components. 

e.g.
All file major versions are increased and we install into different
locations.
All com components have version dependent naming and are reworked to not
clash with previous versions.
This may not be an option if it is a third party com component though, but
there is the potential to use registry free com but this does have
limitations.

%commonfiles%\my company\product1shared
%commonfiles%\my company\product2shared

%programfiles%\my company\product\product1
% programfiles %\my company\product\product2

If you are not dealing with com you can load your dependencies dynamically
from the new common folder in the later version of the software.

Beyond that you are getting into bad practices.

Could you install the dependent dll (or shared components) in a separate msi
that doesn't get uninstalled automatically on product2 removal.

Or some horrendous custom action that puts the dependent dll back if you are
removing it and will break product1.

Dave

-Original Message-
From: Michael Partridge [mailto:michael.partri...@petrosys.com.au] 
Sent: 14 August 2013 03:39
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Adding a new dependent file to shared component
without breaking component rules

Thanks to all for the feedback.

I do agree with the consensus that Product1 is broken and should be fixed
with an upgrade or patch. However, in the real world, that isn't going to
happen in this case. As I said, Product1 and Product2 are side-by-side
installs of the same application, where there is separate Product for each
major version shipped. So, in my example Product1 is really a placeholder
representing 12 different Products (which then all have their own minor
version history). I know I'll never get the resources to make the fix for all
these versions, unfortunate situation where money wins over perfection. At
least I understand (correctly!) the compromise we're making.

(And yeah, we do have a service plan for all our earlier versions for, say,
security issues, but this issue won't be high enough up the list to trigger
one of those. I will keep a record and put in the fix if we do create a new
version of one of the existing "Product1"'s.)

Thanks again for the useful input.

Cheers,
Michael
Ps. I have pushed back to the developer to see if we can remove this
additional dependency, but unsure if that will be possible.


-Original Message-
From: Phil Wilson [mailto:phil.wil...@mvps.org]
Sent: Wednesday, 14 August 2013 8:08 AM
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] Adding a new dependent file to shared component
without breaking component rules

I agree. A common shared component has been updated and it needs fixing in
all the products because it can no longer be shared properly. 

Phil 

-Original Message-
From: David Watson [mailto:dwat...@sdl.com]
Sent: Tuesday, August 13, 2013 10:14 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Adding a new dependent fileger to shared component
without breaking component rules

This is now a bug in product1. It needs fixing at a priority that your
product owner decides. You must have an update strategy for that product,
what if it has a critical security issue/flaw?

You could release product2 as a burn bundle and include a fix in it for
product1 by adding a major upgrade msi or msp to it along with your product2
msi.

Dave


-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: 13 August 2013 15:16
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Adding a new dependent file to shared component
without breaking component rules

No, don't force features to not be uninstalled when uninstalling. Crazy
things will happen. In general, don't mess with feature selection lightly.

Michael, I misread the word "dependency". I think you have analyzed the math
on this correctly. This is one of the scenarios where the Component Rules are
fundamentally broken. Windows Installer expected you to not add dependencies
like this... but devs will be devs and it'd be nice if they actually handled
it correctly.




On Tue, Aug 13, 2013 at 2:55 AM, Blair Murri  wrote:

> You could put D2.dll into its own feature, and force that feature to 
> not be removed on product removal if product 1 is still installed. You 
> get the same "effect" of D2.dll getting orphaned but at least you 
> don't perpetrate the problems of sharing binaries in the same 
> component in all other scenarios.
>
> > From: michael.partri...@petrosys.com.au
> > To: wix-users@lists.sourceforge.net
> > Date: Tue, 13 Aug 2013 04:07:56 +
> > Subject: Re: [WiX-users] Adding

Re: [WiX-users] Adding a new dependent file to shared component without breaking component rules

[David Watson]

This is now a bug in product1. It needs fixing at a priority that your
product owner decides. You must have an update strategy for that product,
what if it has a critical security issue/flaw?

You could release product2 as a burn bundle and include a fix in it for
product1 by adding a major upgrade msi or msp to it along with your product2
msi.

Dave


-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com] 
Sent: 13 August 2013 15:16
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Adding a new dependent file to shared component
without breaking component rules

No, don't force features to not be uninstalled when uninstalling. Crazy
things will happen. In general, don't mess with feature selection lightly.

Michael, I misread the word "dependency". I think you have analyzed the math
on this correctly. This is one of the scenarios where the Component Rules are
fundamentally broken. Windows Installer expected you to not add dependencies
like this... but devs will be devs and it'd be nice if they actually handled
it correctly.




On Tue, Aug 13, 2013 at 2:55 AM, Blair Murri  wrote:

> You could put D2.dll into its own feature, and force that feature to 
> not be removed on product removal if product 1 is still installed. You 
> get the same "effect" of D2.dll getting orphaned but at least you 
> don't perpetrate the problems of sharing binaries in the same 
> component in all other scenarios.
>
> > From: michael.partri...@petrosys.com.au
> > To: wix-users@lists.sourceforge.net
> > Date: Tue, 13 Aug 2013 04:07:56 +
> > Subject: Re: [WiX-users] Adding a new dependent file to shared 
> > component
> without breaking component rules
> >
> > If I put D2.dll in its own component, then, assuming Product1 and
> Product2 installed, when Product2 is uninstalled, D2.dll will be removed.
> However, A.dll will still be at version 1.1.0, so will have lost its 
> dependency and thusly won't run.
> >
> > NB: I can't change Product1 - it's already in the field and won't 
> > have
> any updates. In reality Product1 and Product2 are different versions 
> of our product that can be installed side-by-side - users like to have 
> access to previous versions.
> >
> > Cheers,
> > Michael
> >
> > -Original Message-
> > From: Rob Mensching [mailto:r...@robmensching.com]
> > Sent: Monday, 12 August 2013 6:14 PM
> > To: General discussion for Windows Installer XML toolset.
> > Subject: Re: [WiX-users] Adding a new dependent file to shared 
> > component
> without breaking component rules
> >
> > Why not put D2.dll in it's own Component?
> >
> >
> > On Sun, Aug 11, 2013 at 10:37 PM, Michael Partridge <
> michael.partri...@petrosys.com.au> wrote:
> >
> > > Hi All,
> > >
> > > I was wondering if the state of play has changed at all since
> > >
>
http://stackoverflow.com/questions/703359/wix-add-new-file-to-shared-componen
twasdiscussed?
> > >
> > > Basically, I have Product1 (already released) and Product2 (in
> > > development) which both share the same component A.dll. A.dll is 
> > > installed to %COMMONFILES%/MyProducts/.
> > >
> > > Product1 installs A.dll version 1.0.0, which is dependent upon D1.dll.
> > > Product2 installs A.dll version 1.1.0, which is dependent upon 
> > > D1.dll and D2.dll.
> > >
> > > Due to the way that A.dll is used (it's a COM component registered 
> > > in a thirdparty application, and we can only register one .dll) 
> > > there isn't the option of creating newA.dll and putting that into
Product2.
> > > (At least not without breaking Product1.)
> > >
> > > I think my only option is to add D2.dll in A.dll's component, 
> > > breaking the component rules, and live with the fact that D2.dll 
> > > will remain on the user's computer if they uninstall Product2 then 
> > > uninstall Product1. At least then, if someone uninstalls Product2 
> > > our .dll will continue to run correctly.
> > >
> > > Does anyone have any further insight?
> > >
> > > Thanks,
> > > Michael
> > >
> > > --
> > > 
> > >  Get 100% visibility into Java/.NET code with AppDynamics 
> > > Lite!
> > > It's a free troubleshooting tool designed for production.
> > > Get down to code-level detail for bottlenecks, with <2% overhead.
> > > Download for free and get started troubleshooting in minutes.
> > > http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/os
> > > tg.c lktrk ___
> > > WiX-users mailing list
> > > WiX-users@lists.sourceforge.net
> > > https://lists.sourceforge.net/lists/listinfo/wix-users
> > >
> > >
> >
> --
> 
> > Get 100% visibility into Java/.NET code with AppDynamics Lite!
> > It's a free troubleshooting tool designed for production.
> > Get down to code-level detail for bottlenecks, with <2% overhead.
> > Download for free and get started troubleshooting

Re: [WiX-users] Versioning on small updates

[David Watson]

You need to update the file version to allow windows installer to know
whether or not to overwrite any existing file.
http://msdn.microsoft.com/en-us/library/windows/desktop/aa368599(v=vs.85).asp
x

I don't think the string version is used but I always keep them both in sync
anyway.
Windows installer honours and recognises all four parts of file versions (you
are correct that it only recognises the first 3 parts of msi product
versions).



-Original Message-
From: Nicolás Alvarez [mailto:nicolas.alva...@gmail.com] 
Sent: 06 August 2013 06:42
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Versioning on small updates

According to the MSDN documentation, small updates are for small fixes that
don't change the product version. But I can't find definite information on
what to do with *file* versions. Do I still need to increase the file version
(in the VERSIONINFO resource) of Win32 PE files that I modify in a small
update patch?

If yes, is that the numeric FILEVERSION, the string FileVersion, or both? And
can I bump only the 4th component, or does Windows Installer only take the
first three into account? (Perhaps I'm mixing things up and that's only for
MSI product versions, not file versions...)

--
Nicolás

-
-
Get your SQL database under version control now!
Version control is standard for application code, but databases havent caught
up. So what steps can you take to put your SQL databases under version
control? Why should you start doing it? Read more to find out.
http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk
___
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.
--
Get your SQL database under version control now!
Version control is standard for application code, but databases havent 
caught up. So what steps can you take to put your SQL databases under 
version control? Why should you start doing it? Read more to find out.
http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Need help, how to put a condition on a merge module in Product.wxs [P]

[David Watson]

Sorry I may have confused the issue by stating how I did it, the main
question was does this (or something similar) not work ?

Along the lines of 





 



-Original Message-
From: Steven Ogilvie [mailto:steven.ogil...@titus.com] 
Sent: 31 July 2013 17:26
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Need help, how to put a condition on a merge module
in Product.wxs [P]

Classification: Public
Can't use WIXLIBS to replace the MERGEMODULES (Rob confirmed that with me)

I am installing 5 Services, they each go into a separate folder off the
Services parent folder.

They share 8-10 WIXLIBS each (common files for each service, didn't make
sense to create new component for each file 5 times)

Hence I can't use WIXLIBS for the Merge Modules nor can I throw everything
into the Product.wxs since I would be repeating  files 5 times 10-20 files...

Was able to change 3 other installers from 2 solutions down to 1 solution and
able to create x86 and x64 MSI's

Might just leave this one alone :(

Steve

-Original Message-
From: David Watson [mailto:dwat...@sdl.com]
Sent: July-31-13 12:08 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Need help, how to put a condition on a merge module
in Product.wxs [P]

I did it by not using merge modules, I used pure wixlibs.

http://wyrdfish.wordpress.com/2011/01/05/32-and-64-bit-msis-from-a-single-sou
rce-file/

So my components are pulled into the msi by ComponentGroupRef not by MergeID.

I only have the relevant bitness wixlib referenced in the wixproj.


Can you work around the issue with some pre-processing?

e.g.




 

You seem to be trying to include both sets of merge module into the msi at
compile time then deciding on what to install at runtime when you actually
need to decide at compile time.

Dave W.

-Original Message-
From: Steven Ogilvie [mailto:steven.ogil...@titus.com]
Sent: 31 July 2013 13:55
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Need help, how to put a condition on a merge module
in Product.wxs [P]

Classification: Public
I originally have two solutions for the Services installer, in the x86
product.wxs I have the 5 x86 merge modules, in the x64 product.wxs I have the
5 x64 merge modules...
So there are two sets of merge modules x86 compiled and x64 compiled

I am trying to make 1 solution using the configurations to build x86 MSI x64
MSI

Steve

-Original Message-
From: Blair Murri [mailto:os...@live.com]
Sent: July-31-13 1:23 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Need help, how to put a condition on a merge module
in Product.wxs [P]

You need one set of merge modules for x64 and another for x86, correct?
 
Use conditional compilation. You don't need all the merge modules in the x86,
correct? Why put them there?
 
Or am I missing something?
 
> From: steven.ogil...@titus.com
> To: wix-users@lists.sourceforge.net; d...@agilityrecordbook.com
> Date: Tue, 30 Jul 2013 16:19:37 +
> Subject: Re: [WiX-users] Need help, how to put a condition on a merge 
> module in Product.wxs [P]
> 
> Classification: Public
> Yup I have the configuration set in the Solution file for my Services 
> Solution, and in each MergeModule WIXProj I have set up x86/x64 
> configurations so it is built twice once for x86 and once for x64 and 
> placed in different folders wixlib/wixlibx64 (both merge modules and
> wixlibs)
> 
> So I have 1 MergeModule project / 1 wixlib project but multiple 
> configurations to handle the x86/x64
> 
> Looks like I am pooched...
> 
> Steve
> 
> -Original Message-
> From: David Watson [mailto:dwat...@sdl.com]
> Sent: July-30-13 12:11 PM
> To: General discussion for Windows Installer XML toolset.; David 
> Connet
> Subject: Re: [WiX-users] Need help, how to put a condition on a merge 
> module in Product.wxs [P]
> 
> Isn't the win64 setting on the component so you need to build a 64bit 
> and a
> 32 bit version of each merge module (or wixlib).
> This is easily done with a shared .wxs file and a compilation setting.
> 
> I have 32 and 64 bit components all up my build tree just because one
package needs a 32 and a 64 bit msi.
> 
> (another) Dave
> 
> 
> -Original Message-
> From: Steven Ogilvie [mailto:steven.ogil...@titus.com]
> Sent: 30 July 2013 16:54
> To: David Connet; General discussion forWindows Installer XML toolset.
> Subject: Re: [WiX-users] Need help, how to put a condition on a merge 
> module in Product.wxs [P]
> 
> Classification: Public
> Sigh same merge modules just compiled under x86 and x64
> 
> Get the error:
> 
> Error 49  The merge module 'EnterpriseServicesMM_x64' contains a file
> identifier,
> 'fil2502525491FAEBF0E

Re: [WiX-users] Need help, how to put a condition on a merge module in Product.wxs [P]

[David Watson]

I did it by not using merge modules, I used pure wixlibs.

http://wyrdfish.wordpress.com/2011/01/05/32-and-64-bit-msis-from-a-single-sou
rce-file/

So my components are pulled into the msi by ComponentGroupRef not by MergeID.

I only have the relevant bitness wixlib referenced in the wixproj.


Can you work around the issue with some pre-processing?

e.g.







You seem to be trying to include both sets of merge module into the msi at
compile time then deciding on what to install at runtime when you actually
need to decide at compile time.

Dave W.

-Original Message-
From: Steven Ogilvie [mailto:steven.ogil...@titus.com] 
Sent: 31 July 2013 13:55
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Need help, how to put a condition on a merge module
in Product.wxs [P]

Classification: Public
I originally have two solutions for the Services installer, in the x86
product.wxs I have the 5 x86 merge modules, in the x64 product.wxs I have the
5 x64 merge modules...
So there are two sets of merge modules x86 compiled and x64 compiled

I am trying to make 1 solution using the configurations to build x86 MSI x64
MSI

Steve

-Original Message-
From: Blair Murri [mailto:os...@live.com]
Sent: July-31-13 1:23 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Need help, how to put a condition on a merge module
in Product.wxs [P]

You need one set of merge modules for x64 and another for x86, correct?
 
Use conditional compilation. You don't need all the merge modules in the x86,
correct? Why put them there?
 
Or am I missing something?
 
> From: steven.ogil...@titus.com
> To: wix-users@lists.sourceforge.net; d...@agilityrecordbook.com
> Date: Tue, 30 Jul 2013 16:19:37 +
> Subject: Re: [WiX-users] Need help, how to put a condition on a merge 
> module in Product.wxs [P]
> 
> Classification: Public
> Yup I have the configuration set in the Solution file for my Services 
> Solution, and in each MergeModule WIXProj I have set up x86/x64 
> configurations so it is built twice once for x86 and once for x64 and 
> placed in different folders wixlib/wixlibx64 (both merge modules and
> wixlibs)
> 
> So I have 1 MergeModule project / 1 wixlib project but multiple 
> configurations to handle the x86/x64
> 
> Looks like I am pooched...
> 
> Steve
> 
> -Original Message-
> From: David Watson [mailto:dwat...@sdl.com]
> Sent: July-30-13 12:11 PM
> To: General discussion for Windows Installer XML toolset.; David 
> Connet
> Subject: Re: [WiX-users] Need help, how to put a condition on a merge 
> module in Product.wxs [P]
> 
> Isn't the win64 setting on the component so you need to build a 64bit 
> and a
> 32 bit version of each merge module (or wixlib).
> This is easily done with a shared .wxs file and a compilation setting.
> 
> I have 32 and 64 bit components all up my build tree just because one
package needs a 32 and a 64 bit msi.
> 
> (another) Dave
> 
> 
> -Original Message-
> From: Steven Ogilvie [mailto:steven.ogil...@titus.com]
> Sent: 30 July 2013 16:54
> To: David Connet; General discussion forWindows Installer XML toolset.
> Subject: Re: [WiX-users] Need help, how to put a condition on a merge 
> module in Product.wxs [P]
> 
> Classification: Public
> Sigh same merge modules just compiled under x86 and x64
> 
> Get the error:
> 
> Error 49  The merge module 'EnterpriseServicesMM_x64' contains a file
> identifier,
> 'fil2502525491FAEBF0E0D0ED1FE352E76D.9EFC3F5B_3D47_4233_A162_371DEF5D8
> E92', that is duplicated either in another merge module or in a 
> File/@Id attribute.
> File identifiers must be unique.  Please change one of the file identifiers
> to a different value. C:\Dev\ Setup\Services_Setup\Product.wxs282
> 1 Services_Setup
> 
>   Title="Merge modules for 32 bit OS"
>  Level="1"
>  Display="expand"
>  ConfigurableDirectory="DIRECTORY_PATH_SERVICES">
>   ...
>   
>   
> 
>   
> 
>   Title="Merge modules for 64 bit OS"
>  Level="1"
>  Display="expand"
>  ConfigurableDirectory="DIRECTORY_PATH_SERVICES">
>   ...
>   
>   
> 
>   
> 
> ...
> 
SourceFile="$(env.SharedServices)\Installers\wixlib\ServicesMergeModule.msm"
> Language="1033"/> ...
>  SourceFile="$(env.SharedServices)\Installers\wixlibx64\ServicesMergeMo
> dule.ms
> m" Language="1033"/>
> 
> -Original Message-
> From: David Connet [mailto:d...@agilityrecordbook.c

Re: [WiX-users] Need help, how to put a condition on a merge module in Product.wxs [P]

[David Watson]

Isn't the win64 setting on the component so you need to build a 64bit and a
32 bit version of each merge module (or wixlib).
This is easily done with a shared .wxs file and a compilation setting.

I have 32 and 64 bit components all up my build tree just because one package
needs a 32 and a 64 bit msi.

(another) Dave 


-Original Message-
From: Steven Ogilvie [mailto:steven.ogil...@titus.com] 
Sent: 30 July 2013 16:54
To: David Connet; General discussion forWindows Installer XML toolset.
Subject: Re: [WiX-users] Need help, how to put a condition on a merge module
in Product.wxs [P]

Classification: Public
Sigh same merge modules just compiled under x86 and x64

Get the error:

Error   49  The merge module 'EnterpriseServicesMM_x64' contains a file
identifier,
'fil2502525491FAEBF0E0D0ED1FE352E76D.9EFC3F5B_3D47_4233_A162_371DEF5D8E92',
that is duplicated either in another merge module or in a File/@Id attribute.
File identifiers must be unique.  Please change one of the file identifiers
to a different value.   C:\Dev\ Setup\Services_Setup\Product.wxs282
1   Services_Setup


  ...
  
  

  


  ...
  
  

  

...
 ...


-Original Message-
From: David Connet [mailto:d...@agilityrecordbook.com]
Sent: July-30-13 11:10 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Need help, how to put a condition on a merge module
in Product.wxs [P]

Assign them to a feature and condition the feature.

Dave



- Original Message -
From: Steven Ogilvie 
To: General discussion for Windows Installer XML toolset.

Cc: 
Sent: Tuesday, July 30, 2013 7:16 AM
Subject: Re: [WiX-users] Need help, how to put a condition on a merge module
in Product.wxs [P]

Classification: Public
The 5 merge modules have  of about 10
wixlibs The files in the MergeModules and WixLibs are built as AnyCPU however
since I need to install the services for 64 bit OS and 32 bit OS I need two
MSI's one for 32 and one for 64 bit

So I am not using any binary files that are specific for 32 bit or 64 bit, I
just need to include the MergeModules in 1 product.wxs file The Merge Modules
themselves are built x86 and x64 and are located in two different folders...

So the question is, HOW do I conditionally install the merge modules based on
the OS bitness?

Thanks,

Steve

-
-
Get your SQL database under version control now!
Version control is standard for application code, but databases havent caught
up. So what steps can you take to put your SQL databases under version
control? Why should you start doing it? Read more to find out.
http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

 
This message has been marked as Public by Steven Ogilvie on July-30-13
11:53:30 AM.

The above classification labels were added to the message by TITUS Message
Classification. For more information visit www.titus.com.

 



-
-
Get your SQL database under version control now!
Version control is standard for application code, but databases havent caught
up. So what steps can you take to put your SQL databases under version
control? Why should you start doing it? Read more to find out.
http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk
___
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.


--
Get your SQL database under version control now!
Version control is standard for application code, but databases havent 
caught up. So what steps can you take to put your SQL databases under 
version control? Why should you start doing it? Read more to find out.
http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Unattended upgrade of Burn package

[David Watson]

I don't think burn currently supports this kind of scenario well (it may but
I am not an expert).

What you could do is make a per-user burn bundle that just installs your msi
silently then add that as an .exe package to your main with-prerequisites
bundle.

Or indeed leave it the way you have it and maybe flag the upgradable msi as
visible in ARP and supply the msi directly when you service it.

Or you could work out how burn is deciding to show the UAC prompt and fix it
so it works in your scenario if possible.

Dave

-Original Message-
From: dave [mailto:d...@swordfishsoftware.co.nz] 
Sent: 30 July 2013 06:02
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Unattended upgrade of Burn package

I'd like to use Burn to install multiple pre-requisites (VC++ redist, console
app) and two desktop application msi packages. One of these desktop
applications is a client program to be remotely upgraded without elevation.
I have it installing to LocalAppData and major upgrades work fine without
elevation.

Now, can I install this client app via Burn and then run a major upgrade on
it using just the msi package? I have installed via Burn with the
pre-requisites and this raises UAC as expected. I ran a major upgrade using
just the msi and this performed as expected but put a new entry into Programs
and Features.

I cannot run the complete burn bundle as a major upgrade in quiet mode as
this raises the UAC prompt, even though only the client app is updated with a
new version.

Is this even possible? How do I go about it?

My bundle:

- VC++ redist (installed via burn)
- console app (requires elevation, installed via burn)
- client app (DOESN'T require elevation, installed via burn) <- I want to
upgrade this silently either with burn or msi
- server app (requires elevation, installed via burn)

Thanks

Dave



--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Unattended-upgr
ade-of-Burn-package-tp7587678.html
Sent from the wix-users mailing list archive at Nabble.com.

-
-
Get your SQL database under version control now!
Version control is standard for application code, but databases havent caught
up. So what steps can you take to put your SQL databases under version
control? Why should you start doing it? Read more to find out.
http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk
___
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.


--
Get your SQL database under version control now!
Version control is standard for application code, but databases havent 
caught up. So what steps can you take to put your SQL databases under 
version control? Why should you start doing it? Read more to find out.
http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] [wix-users] Impact of installed burn?

[David Watson]

Hi,

We have been shipping with our own (non-burn) chainer packages for years and
not had any problems with these scenarios. In my experience if a
mass-deployment system is being used the end users machines are locked down
so they can't install software by hand so they could not use  an .exe to
install.

We supply Interactive .exe, silent.exe and instructions on how to unpack the
MSIs for mass deployment systems that cannot handle .exes also instructions
on how to package for citrix and app-v. Some very large customers do a mix
and match of all these deployment methods but it is typically site per site
based.

Dave

-Original Message-
From: Tomas Köhn [mailto:tomas.k...@cellavision.se] 
Sent: 25 July 2013 12:21
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] [wix-users] Impact of installed burn?

Thank you your replay.

I'm worried about the following scenarios:
* Administrators installs the program with the .msi file (their preferred
method). Later a user installs the program using setup.exe (burn)
* Users installs the setup.exe (burn), later administrators installs the
program (same version or different version) using the .msi file.

I'm worried about version conflicts because setup.exe (burn) have references
to the .msi file (setup.exe, burn only contains a single .msi).

/ Tomas

-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: den 24 juli 2013 19:20
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] [wix-users] Impact of installed burn?

What conflicts are you worried about exactly? One or more specific user
scenarios that expose the issue you think there is in Burn would probably
help a lot.


On Wed, Jul 24, 2013 at 3:58 AM, Tomas Köhn wrote:

> I agree, burn has a lot of cool features.
>
> Our problem is that administrators expects an .msi for easy remote 
> deployment, while other, smaller customers want to have an setup.exe 
> with checks dependency (.NET framework, OS etc.).
>
> If we at first installs with setup.exe, we might later have to install 
> .msi without conflicts and vice versa. If I understand correctly this 
> is not possible with burn, which is a shame because it has everything 
> we need and does it very well. What is a good alternative for this?
dotNetInstaller?
>
> Regards
> Tomas
>
> -Original Message-
> From: Rob Mensching [mailto:r...@robmensching.com]
> Sent: den 24 juli 2013 06:44
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] [wix-users] Impact of installed burn?
>
> The cool thing is that if you always use Bundles to install your MSI 
> packages, shared MSI packages will be correctly reference counted and 
> only removed when the last Bundle that needs it is removed. Totally 
> avoids all the bad behaviors.
>
>
> On Tue, Jul 23, 2013 at 10:00 AM, Wesley Manning  >wrote:
>
> > If the bundle exe is uninstalled it would uninstall the msi.  So you 
> > can install the standalone msi again after.  If you try to install 
> > msi after installing bundle exe the msi will not install as the 
> > bundle already installed it.
> > If you install MSI and then install bundle exe then you'll see two 
> > entries in ARP.  There are other effects too such as if you install 
> > a newer version of the MSI with the bundle exe already installed it 
> > will
> upgrade the MSI.
> >
> > Not sure if this will present a problem other than aesthetics.  
> > Should really use a MSI alone or burn alone and not mix the two.
> >
> > Wes
> >
> > -Original Message-
> > From: Tomas Köhn [mailto:tomas.k...@cellavision.se]
> > Sent: July-23-13 6:09 AM
> > To: General discussion for Windows Installer XML toolset.
> > Subject: Re: [WiX-users] [wix-users] Impact of installed burn?
> >
> > Thanks,
> >
> > Will this impact future installs of .msi files which has been part 
> > of bundle before (but has been uninstalled)?
> >
> > / Tomas
> >
> > -Original Message-
> > From: Wesley Manning [mailto:wmann...@dynagen.ca]
> > Sent: den 22 juli 2013 14:40
> > To: General discussion for Windows Installer XML toolset.
> > Subject: Re: [WiX-users] [wix-users] Impact of installed burn?
> >
> > Users will have no way to uninstall burn package AFAIK.  See 
> > http://www.joyofsetup.com/2013/07/05/burn-zero-one-or-n/ .
> >
> > Wes
> >
> > -Original Message-
> > From: Tomas Köhn [mailto:tomas.k...@cellavision.se]
> > Sent: July-22-13 8:20 AM
> > To: wix-users@lists.sourceforge.net
> > Subject: [WiX-users] [wix-users] Impact of installed burn?
> >
> > We need to support installation from both .exe and .msi (for remote 
> > program distribution). As I understand, burn can't be used without 
> > installing into ARP. We want the program installation to be the same 
> > from both .exe and .msi.
> >
> > If I set DisableModify="yes" DisableRemove="yes", the bundle (burn) 
> > application will not be visible in Program & Feature. What will be 
> > stored 

Re: [WiX-users] Error launching bootstrapper

[David Watson]

What error?

-Original Message-
From: Pasquale Fersini [mailto:basquale.fers...@gmail.com] 
Sent: 25 July 2013 14:42
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Error launching bootstrapper

Hi all,
on a user machine (Windows XP SP3) our setup, compiled with wix 3.8, doesn't
start, immediately going into error. No log possible. Double click
-> Error.
I don't know...

Ideas?

Regards,
Pasquale.
-
-
See everything from the browser to the database with AppDynamics Get
end-to-end visibility with application monitoring from AppDynamics Isolate
bottlenecks and diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today!
http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
___
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.


--
See everything from the browser to the database with AppDynamics
Get end-to-end visibility with application monitoring from AppDynamics
Isolate bottlenecks and diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today!
http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Installation failed. Try again?

[David Watson]

Don't you run it with the /layout parameter to download everything you need
locally then copy that to the other machine.

(Never tried it mind).

-Original Message-
From: Philip Mitchell [mailto:mitch...@trdeo.co.uk] 
Sent: 18 July 2013 12:17
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Installation failed. Try again?

I am trying to install Wix 3.7 onto a Windows 7 Pro machine, with VS2008 and
NO INTERNET. I have searched the internet (on another machine!) and tried
various suggestions including putting ProjectAggregator2.msi in the same
directory as the wix37.exe. All I get is the red boxes with the middle one
saying "Failed. Try again?". The log file generated is :

[16F8:1684][2013-07-18T11:40:44]i001: Burn v3.7.1224.0, Windows v6.1 (Build
7601: Service Pack 1), path: M:\wix37.exe, cmdline: ''
[16F8:1684][2013-07-18T11:40:44]i000: Initializing string variable
'InstallFolder' to value '[ProgramFilesFolder]WiX Toolset v3.7'
[16F8:1684][2013-07-18T11:40:44]i000: Setting string variable 'WixBundleLog'
to value
'C:\Users\*\AppData\Local\Temp\WiX_Toolset_v3.7.1224.0_20130718114044.log
' 

[16F8:1684][2013-07-18T11:40:44]i000: Setting string variable
'WixBundleOriginalSource' to value 'M:\wix37.exe'
[16F8:1684][2013-07-18T11:40:44]i000: Setting string variable 'WixBundleName'
to value 'WiX Toolset v3.7.1224.0'
[16F8:1684][2013-07-18T11:40:45]i000: Loading managed bootstrapper
application.
[16F8:1684][2013-07-18T11:40:45]i000: Creating BA thread to run
asynchronously.
[16F8:0C80][2013-07-18T11:40:46]i000: Running the WiX BA.
[16F8:1684][2013-07-18T11:40:46]i100: Detect begin, 8 packages
[16F8:0C80][2013-07-18T11:40:46]i000: Creating a UI.
[16F8:1684][2013-07-18T11:40:46]i000: Registry key not found. Key =
'SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full'
[16F8:1684][2013-07-18T11:40:46]i000: Registry key not found. Key =
'SOFTWARE\Microsoft\Windows Installer XML\3.7'
[16F8:1684][2013-07-18T11:40:46]i052: Condition 'PreviousInstallFolder' 
evaluates to false.
[16F8:1684][2013-07-18T11:40:46]i000: Registry value not found. Key =
'SOFTWARE\Microsoft\VisualStudio\8.0', Value = 'InstallDir'
[16F8:1684][2013-07-18T11:40:46]i000: Setting string variable
'VS2008InstallFolder' to value 'c:\Program Files\Microsoft Visual Studio
9.0\Common7\IDE\'
[16F8:1684][2013-07-18T11:40:46]i000: Registry key not found. Key =
'SOFTWARE\Microsoft\VisualStudio\11.0'
[16F8:1684][2013-07-18T11:40:46]i000: Registry value not found. Key =
'SOFTWARE\Microsoft\VisualStudio\10.0', Value = 'InstallDir'
[16F8:1684][2013-07-18T11:40:46]e000: Error 0x80070005: Failed to open
uninstall registry key.
[16F8:1684][2013-07-18T11:40:46]e000: Error 0x80070005: Failed to initialize
per-machine related bundles.
[16F8:1684][2013-07-18T11:40:46]e000: Error 0x80070005: Failed to detect
related bundles.
[16F8:1684][2013-07-18T11:40:46]i199: Detect complete, result: 0x80070005
[16F8:1684][2013-07-18T11:41:59]i200: Plan begin, 8 packages, action: 
Unknown
[16F8:1684][2013-07-18T11:41:59]e000: Error 0x80070057: Invalid action state.
[16F8:1684][2013-07-18T11:41:59]e000: Error 0x80070057: Failed to get default
request state for action.
[16F8:1684][2013-07-18T11:41:59]e000: Error 0x80070057: Failed to set default
package state.
[16F8:1684][2013-07-18T11:41:59]e000: Error 0x80070057: Failed to process
package.
[16F8:1684][2013-07-18T11:41:59]e000: Error 0x80070057: Failed to plan
packages.
[16F8:1684][2013-07-18T11:41:59]i299: Plan complete, result: 0x80070057
[16F8:1684][2013-07-18T11:45:55]i500: Shutting down, exit code: 0x0
[16F8:1684][2013-07-18T11:45:55]i410: Variable: InstallFolder = C:\Program
Files\WiX Toolset v3.7
[16F8:1684][2013-07-18T11:45:55]i410: Variable: ProgramFilesFolder =
C:\Program Files\
[16F8:1684][2013-07-18T11:45:55]i410: Variable: VS2008InstallFolder =
c:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE\
[16F8:1684][2013-07-18T11:45:55]i410: Variable: WixBundleAction = 0
[16F8:1684][2013-07-18T11:45:55]i410: Variable: WixBundleElevated = 0
[16F8:1684][2013-07-18T11:45:55]i410: Variable: WixBundleLog =
C:\Users\*\AppData\Local\Temp\WiX_Toolset_v3.7.1224.0_20130718114044.log 

[16F8:1684][2013-07-18T11:45:55]i410: Variable: WixBundleManufacturer =
Microsoft Corporation
[16F8:1684][2013-07-18T11:45:55]i410: Variable: WixBundleName = WiX Toolset
v3.7.1224.0
[16F8:1684][2013-07-18T11:45:55]i410: Variable: WixBundleOriginalSource =
M:\wix37.exe
[16F8:1684][2013-07-18T11:45:55]i410: Variable: WixBundleProviderKey =
{963ac4b4-a882-4471-8db9-c4adc7b42dc4}
[16F8:1684][2013-07-18T11:45:55]i410: Variable: WixBundleTag =
[16F8:1684][2013-07-18T11:45:55]i410: Variable: WixBundleVersion =
3.7.1224.0
[16F8:1684][2013-07-18T11:45:55]i007: Exit code: 0x0, restarting: No


-
-
See everything from the browser to the database with AppDynamics Get
end-to-end visibility with application monitoring from AppDynamics Isolate
bottlenecks and diagnose root c

Re: [WiX-users] Newbie question

[David Watson]

Also you could use the Directory or DirectoryRef @FileSource  attribute to
say where all files in a folder are pulled in from then you can make your
component definitions very clean.

e.g. your example component would be :-







 More components.




This does change the component ID to 'Scheduling.exe' though, so beware of ID
clashes.

-Original Message-
From: Sean Hall [mailto:rhal...@hotmail.com] 
Sent: 16 July 2013 01:41
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Newbie question

Use a .wxi file.  For more info, look at this StackOverflow question
http://stackoverflow.com/questions/8495903/how-to-define-a-global-variable-in
-wix
 
Sean
 
> Date: Mon, 15 Jul 2013 16:46:13 -0700
> From: kpet...@otaksoft.com
> To: wix-users@lists.sourceforge.net
> Subject: [WiX-users] Newbie question
> 
> Hi,
> 
> I do
> 
>  SP10\release 2" ?>
> 
> above the product tag in my main.wxs file. I have a number of fragment 
> files, each handling a large number of DLLs for certain product categories.
> 
> I now want to refer to the LocalRootDir from within these fragment 
> files
> 
>   
>   KeyPath="yes"
>   Vital="yes"
>   Source="$(var.LocalRootDir)\Scheduling.exe" />
>   
> 
> I have not been able to do this without redefining LocalRootDir in 
> each of the fragment files.
> 
> Clearly, I am not doing things right. How can I achieve this?
> 
> TIA,
> Kai
> --
>  See everything from the browser to the database with 
> AppDynamics Get end-to-end visibility with application monitoring from 
> AppDynamics Isolate bottlenecks and diagnose root cause in seconds.
> Start your free trial of AppDynamics Pro today!
> http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.c
> lktrk ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
  
-
-
See everything from the browser to the database with AppDynamics Get
end-to-end visibility with application monitoring from AppDynamics Isolate
bottlenecks and diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today!
http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
___
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.


--
See everything from the browser to the database with AppDynamics
Get end-to-end visibility with application monitoring from AppDynamics
Isolate bottlenecks and diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today!
http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Votive installation

[David Watson]

Votive has been part of the standard wix install for a while. If you have
installed 3.7 you should have wix templates (etc.) available in visual
studio.

There should be a "windows Installer Xml" template group if you do file->new
project.

If not try a repair.

-Original Message-
From: Harwood, Ray [mailto:rharw...@carondelet.org] 
Sent: 12 July 2013 13:39
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Votive installation

I've successfully installed Wix 3.7, and want to install Votive for Wix
projects under VS2010 at work and VS2012 at home.  Unfortunately the only
reference I can locate regarding installing Votive says to install Votive.msi
from the Wix install... but I can only find Votive DLL's (votive2005.dll,
votive2008.dll, votive2010.dll).

Any help on getting the Wix projects visible in Visual Studio 2010 (and 2012
if possible) would be helpful.

Ray

J. Ray Harwood | Project Manager/Custom Development: Unity/CARS/DLCT
Carondelet Health Network



CONFIDENTIALITY NOTICE:
This email message and any accompanying data or files is confidential and may
contain privileged information intended only for the named recipient(s). If
you are not the intended recipient(s), you are hereby notified that the
dissemination, distribution, and or copying of this message is strictly
prohibited. If you receive this message in error, or are not the named
recipient(s), please notify the sender at the email address above, delete
this email from your computer, and destroy any copies in any form
immediately. Receipt by anyone other than the named recipient(s) is not a
waiver of any attorney-client, work product, or other applicable privilege.
-
-
See everything from the browser to the database with AppDynamics Get
end-to-end visibility with application monitoring from AppDynamics Isolate
bottlenecks and diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today!
http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
___
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.


--
See everything from the browser to the database with AppDynamics
Get end-to-end visibility with application monitoring from AppDynamics
Isolate bottlenecks and diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today!
http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Resolve Light 1056 Warning

[David Watson]

Merge modules are only really of use these days to share components with
other installation technology.

If you are totally wix based use wixlibs or wix fragments. 

-Original Message-
From: Steven Ogilvie [mailto:steven.ogil...@titus.com] 
Sent: 11 July 2013 13:48
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Resolve Light 1056 Warning

Sigh,

I am confused... When I was using InstallShield (for many years) I was told
to always use Merge Modules, easier for upgrading, and easier for grouping
"features".

I have a Server MSI and a Services MSI which is bundled in burn so the
bootstrapper can take care of the pre reqs etc...

In my Services MSI I have 6 Merge Modules, where each Service is a Merge
Module, I also have several WixLibs of "common files" and share those WixLibs
within the Merge Modules. The Merge Modules where used mainly for
Upgrading...

Are the majority of you saying it makes more sense to get rid of the Merge
Modules and just use the WixLibs?

Steve

-Original Message-
From: John Cooper [mailto:jocoo...@jackhenry.com]
Sent: July-11-13 8:34 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Resolve Light 1056 Warning

Yes, I really hate merge modules.  Wixlibs are much better.  Always have
issues with merge modules I haven't authored.

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




-Original Message-
From: Kathy Morey
Sent: Wednesday, July 10, 2013 4:22 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Resolve Light 1056 Warning

FYI 

It turns out that, although John's suggestion did work, different Microsoft
merge modules have different values for some of the standard folders, and so
I will be following Rob's suggestion and just ignoring those warnings.

Thanks.

-Original Message-
From: Kathy Morey
Sent: Wednesday, July 10, 2013 5:08 PM
To: 'General discussion for Windows Installer XML toolset.'
Subject: RE: Resolve Light 1056 Warning

Thanks, John.

That did it for me.


-Original Message-
From: John Cooper
Sent: Wednesday, July 10, 2013 12:50 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Resolve Light 1056 Warning

I was able to get the ".:System32" by using







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




-Original Message-
From: Kathy Morey
Sent: Wednesday, July 10, 2013 11:22 AM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Resolve Light 1056 Warning

I am creating a WiX installer for an application that requires some Microsoft
merge modules.

I'm getting several warnings like:

warning LGHT1056: The Directory table contains a row with primary key(s)
'SystemFolder' which cannot be merged from the merge module
'C:\_blah\blah\COMCAT.MSM'.  This is likely due to collision of rows with the
same primary key(s) (but other different values in other columns) between the
database and the merge module.

I looked at the merge module and my MSI with Orca and found this difference
in the DefaultDir column of the Directory table:

MM DefaultDir - .:System32
My DefaultDir - System32

How do I author my project so that I get the ".:" designation in the
DefaultDir column?

Kathy Morey
Synergy Software Engineer
Profitstars, a Jack Henry Company
700 Tower Drive, Suite 600
Troy MI 48098
Office: 248.879.0316 ext. 454809
Email: kmo...@profitstars.com
NOTICE: This electronic mail message and any files transmitted with it are
intended exclusively for the individual or entity to which it is addressed.
The message, together with any attachment, may contain confidential and/or
privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure or
distribution is strictly prohibited. If you have received this message in
error, please immediately advise the sender by reply email and delete all
copies.
-
-
See everything from the browser to the database with AppDynamics Get
end-to-end visibility with application monitoring from AppDynamics Isolate
bottlenecks and diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today!
http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
NOTICE: This electronic mail message and any files transmitted with it are
intended exclusively for the individual or entity to which it is addressed.
The message, together with an

Re: [WiX-users] PatchCertificates element and Insignia.exe

[David Watson]

Does it work if you remove the PatchCertificates elements?

I.e. is insignia hand holding you and doing everything so you do not need to?



-Original Message-
From: Georg von Kries [mailto:g...@creativbox.net] 
Sent: 08 July 2013 15:54
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] PatchCertificates element and Insignia.exe

Hi Jacob,

signing is indeed working without any problem. But if you have a
 element in your MSI, signing the MSI with insignia
(actually it is done by an MSbuild target) will change the included
certificates in the MsiDigitalCertificate table.

The following snipped (e.g. in product.wxs) will create entries in the MSI
tables MsiDigitalCertificate and MsiPatchCertificate:


  


The certificate will get the identifier "MyCertificate" which is referenced
in MsiPatchCertificate. 

If you are now using external cabs and sign the MSI, the "MyCertificate" is
removed from the MsiDigitalCertificate table and a new one is added for any
external cab. They will get the certificates thumbprint as the identifier but
MsiPatchCertificate is still referencing "MyCertificate" which will break the
MSI IMHO.

It is currently not an issue for me, as I have no plans to use patches in the
near future. But I was asking myself if this is an bug or if I did something
wrong.

Thanks for your help,
Georg


-Ursprüngliche Nachricht-
Von: Hoover, Jacob [mailto:jacob.hoo...@greenheck.com]
Gesendet: Montag, 8. Juli 2013 16:38
An: General discussion for Windows Installer XML toolset.
Cc: wix-users@lists.sourceforge.net
Betreff: Re: [WiX-users] PatchCertificates element and Insignia.exe

I've been signing a msi and its external cabs without issue.

Can you provide the steps you are using to see if I can spot anything?

On Jul 8, 2013, at 9:30 AM, "Georg von Kries"  wrote:

> Hi all,
> 
> 
> 
> I've been using a  element in our installers for 
> several years now, just in case we want to provide a patch and allow 
> UAC
patching.
> After switching to use external cab files, I have mentioned that this 
> is broken.
> 
> 
> 
> When using external cabs, singing them and inscribing the digital 
> certificate via Insignia.exe, it will remove the certificates provided 
> in the PatchCertificates element from the MsiDigitalCertificate table 
> and add a new entry with the certificate used for singing the cab 
> files. This is actually the same certificate (in our case), but the 
> identifier in the MsiDigitalCertificate table is being replaced.
> Insignia (or actually the
> Inscriber) will use the certificates thumbprint as the identifier. 
> This invalidates the foreign key in the MsiPatchCertificate table.
> 
> Additionally I cannot just use the certificate thumbprint as the 
> identifier in  the  element, because it might 
> start with a number which makes it invalid as an identifier.
> 
> 
> 
> Therefore I think there are two bugs in the Inscriber. 
> InscribeDatabase()
> method:
> 
> 1.   It should not remove existing certificates from the
> MsiDigitalCertificate table
> 
> 2.   The used identifier can be invalid, if the certificate thumbprint
> starts with a number. E.g. an underscore should be added at the 
> beginning
> 
> 
> 
> Am I missing something or is this a known limitation/bug? 
> 
> 
> 
> Kind regards,
> 
> Georg von Kries
> 
> 
> 
> 
> 
> --
>  This SF.net email is sponsored by Windows:
> 
> Build for Windows Store.
> 
> http://p.sf.net/sfu/windows-dev2dev
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users


--
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



-
-
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev
___
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.


--
This SF.net email is sponsored by Windows:

Build for Windows Store.

Re: [WiX-users] Authenticode signatures

[David Watson]

It should come up as unsigned in the UAC prompt, if you have that disabled
you won't see anything. You can usually still install it.

-Original Message-
From: Ivo Beltchev [mailto:i...@ibeltchev.com] 
Sent: 07 July 2013 23:34
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Authenticode signatures

Hi

 

I have a digital certificate and I signed my MSI with it. When I view the
properties of the file in Explorer it shows the certificate correctly. So far
so good.

 

Then I modified the MSI file in a binary editor (changed one byte). Now when
I run the signtool I get an error that the verification failed. So far so
good.

 

But when I view the file properties I still see the certificate. I was able
to run the MSI and install it. I was expecting Explorer to detect the file as
corrupted and for the MSI to fail to install.

 

What am I missing? Is there an extra step during the WiX pipeline that I need
to do, or were my expectations wrong that a file modification will be caught
by Windows?

 

Thanks

Ivo

 

-
-
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev
___
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.


--
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] instaling a bundle to install an older msi

[David Watson]

Generally people fix the issue and release a later build version, so your
scenario is quite odd.

If you can't do that you could take the msi with build 3698 in it and edit it
so that it does a major upgrade* (one that uninstalls and reinstalls) with
orca or insted (you may need to re-sign it after modifying it). 

Major upgrade details in case you were not doing that:-
http://wix.sourceforge.net/manual-wix3/major_upgrade.htm
You must schedule an early RemoveExistingProducts or any versioned dlls will
not be downgraded.

Then add that to a bundle with a higher version than any other you have
released.

This will make it look like a new version of the application is being
installed and the early scheduling of remove existing products should
hopefully remove the later binaries and allow them to be downgraded.

Hacky but easier than re-writing a BA.

-Original Message-
From: jo...@msli.com [mailto:jo...@msli.com] 
Sent: 03 July 2013 17:03
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] instaling a bundle to install an older msi

That's the only way?

Isn't there a way to force the user to uninstall one bundle before installing
a new one?

The reason I'm resistant to a custom BA is that I don't know how to approach
programming a BA correctly.  I know perl, python, bash, some C (from a unix
world).  I have made ant scripts to run wix commands, and I have learned wix
to make an msi and a basic bundle, but the bundle will never pass QA as it
is.

Are there no other options?

On Wed, 2013-07-03 at 02:13 -0700, Blair Murri wrote:
> The only way to do that today would be to write a custom BA that cycles
through plan and apply twice: once to remove the previous bundle and the
second time to install the MSI.
>  
> > From: jo...@msli.com
> > To: wix-users@lists.sourceforge.net
> > Date: Tue, 2 Jul 2013 18:13:45 -0700
> > Subject: [WiX-users] instaling a bundle to install an older msi
> > 
> > Can I make a bundle that always uninstalls the previous msi before 
> > installing the new one?
> > 
> > I have a bundle that installed an msi.
> > 
> > The bundle Version= 2013.07.01.0,
> > the msi Version = 3.0.1
> > the program build 3699.
> > 
> > There was a problem with build 3699 so I must release build 3698, in 
> > a way that is easy on the users.
> > 
> > May I create a bundle that will install the build 3698 some how?
> > 
> > I tried to increment the bundle Version= 2013.07.02.0, and build 
> > using the older msi, and install the bundle, "Programs and 
> > Feactures" increments the bundle version, but the msi was not 
> > downgrade to build 3698.
> > 
> > How can I deal with this situation?
> > 
> > My bundle.wxs
> >   > xmlns="http://schemas.microsoft.com/wix/2006/wi";
> > xmlns:bal="http://schemas.microsoft.com/wix/BalExtension";
> > xmlns:util="http://schemas.microsoft.com/wix/UtilExtension";
> > >
> > 
> >> Name="$(var.MyInstallerName)"
> > Version="$(var.BundleVersion)"
> > Manufacturer="$(var.MyCompanyName)"
> > Copyright="(c) All rights reserved."
> > UpgradeCode="$(var.Guid_Bundle)"
> > HelpTelephone="$(var.HelpPhone)"
> > HelpUrl="$(var.HelpUrl)"
> > UpdateUrl="$(var.UpdateUrl)"
> > AboutUrl="$(var.AboutUrl)"
> > Condition="((VersionNT >= v5.1) 
> > AND (ServicePackLevel >= 3)) 
> > OR ((VersionNT >= v5.2) 
> > AND (ServicePackLevel >= 2)) 
> > OR (VersionNT >= v6.0)"
> > IconSourceFile="$(var.ProdIcon)"
> >   >
> > 
> >  >   Id="WixUIBannerBmp"
> >   Value="../ProgramFiles/Resources/Images/InstallerHeaderImage.bmp"
> > />
> > 
> >  >   Id="WixStandardBootstrapperApplication.HyperlinkLicense"
> > >
> >> LicenseUrl="EULA.html"
> > LogoFile="$(var.ProdIcon)"
> > SuppressRepair="yes"
> > SuppressOptionsUI="yes"
> >   />  
> >   
> > 
> > 
> > 
> > 
> >  >   Id="RegistrySearchWinPcapHas" 
> >   Variable="WinPcapInstalled"
> >   Root="HKLM"
> >
Key="SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\WinPcapInst"
> >   Result="exists"
> > />
> >  >   Id="RegistrySearchWinPcapMajor" 
> >   Variable="WinPcapVersionMajor"
> >   Root="HKLM"
> >
Key="SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\WinPcapInst"
> >   Value="VersionMajor"
> >   Format="raw"
> >   Result="value"
> > />
> >  >   Id="RegistrySearchWinPcapMinor" 
> >   Variable="WinPcapVersionMinor"
> >   Root="HKLM"
> >
Key="SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\WinPcapInst"
> >   Value="VersionMinor"
> >   Format="raw"
> >   Result="value"
> > />
> > 
> >  >   Id="RegistrySearchBonjourHas" 
> >   Variable="BonjourDLL"
> >   Root="HKLM"
> > Key="SOFTWARE\Classes\AppID\Bonjour.DLL"
> >   Result="exists"
> > />
> >  >   Id="RegistrySearchBonjourValue" 
> >   Variable="BounjourVersion"
> >   Root="

Re: [WiX-users] SQL CE 4.0 Package

[David Watson]

Wesley

I filled in the unsubscribe form on the website for you, you need to reply to
that email (not this one) and you will be unsubscribed.

Dave

-Original Message-
From: Wesley Wells [mailto:wwe...@midsouthmetalsupply.com] 
Sent: 27 June 2013 17:00
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] SQL CE 4.0 Package

I Just talked to Wix and they were supposed to unsubscribe me to all these
emails!!!

-Original Message-
From: Nicholas Pierce [mailto:nicholas.pie...@permasense.com]
Sent: Thursday, June 27, 2013 10:50 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] SQL CE 4.0 Package

Just write the version number, with a v in front and no quoting (i.e.
SQL_SERVER_VERSION >= v10.50).

Nicholas

On 27 June 2013 16:06, snowkoan  wrote:

> Cool. So we have a Burn variable called SqlCe40Version, that contains 
> a version string like "14.0.0.0"
>
> How can we do a version comparison with a hardcoded string, like 
> "v4.0.8876.1"
>
>
>
> --
> View this message in context:
> http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/SQL-CE-4
> -0-Package-tp7586592p7586910.html Sent from the wix-users mailing list 
> archive at Nabble.com.
>
>
> --
>  This SF.net email is sponsored by Windows:
>
> Build for Windows Store.
>
> http://p.sf.net/sfu/windows-dev2dev
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>

--
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


-
No virus found in this message.
Checked by AVG - www.avg.com
Version: 2013.0.3345 / Virus Database: 3204/6445 - Release Date: 06/27/13


-
-
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev
___
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.


--
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Require admin rights to msp

[David Watson]

The patch certificates go in the wix for your original msi.

Then you use signtool to sign that msi and any patch msp that you create.

If you have already released your MSI then you will either need to re-release
it as a major upgrade to include the embedded certificate or release a patch
with them in but that patch will need to be run elevated and subsequent
patches will be able to bypass UAC.

-Original Message-
From: chintala srinivas [mailto:chentala.srini...@gmail.com] 
Sent: 27 June 2013 17:18
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Require admin rights to msp

Thanks Jacob and Blair

By changing the custom-action attribute to Impersonate="no" from "yes" is
resolved my issue. But Signing the MSP is very important thing for patch
installation.

I am not able to sign the msp as Jacob suggested, because I unable to add the
PatchCertificates to my patch.wxs.

I followed the below steps for signing MSI and MSP:
1. Signed the MSI by giving the below post build event.

 "C:\Program Files\Microsoft
SDKs\Windows\v6.0A\bin\signtool.exe" sign /f $(SolutionDir)\xxx.pfx /p xx
/t http:// http://timestamp.digicert.com /v
$(ProjectDir)\bin\$(ConfigurationName)\en-US\xxx.msi

2. Signing the MSP by giving the same postbuild event as above, Then the MSP
is digitally signature by seeing it from properties. But MsiPatchCertificate
table is not coming.

I missed something, So MsiPatchCertificate table is not coming.

Regards,
Srinivas.


On Wed, Jun 26, 2013 at 2:01 PM, David Watson  wrote:

> What Jacob suggests works, we have been using it for several years, if 
> the certificate is in the original msi and it and the patch are signed 
> by the same certificate then you do not need to elevate to install.
>
> It's fun when the certificate expires though as you need to use a 
> hotfix to deliver the new certificate which is signed by the old 
> certificate before it expires so you can then sign by the new 
> certificate in future patches.
>
> -Original Message-
> From: Blair Murri [mailto:os...@live.com]
> Sent: 26 June 2013 06:53
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Require admin rights to msp
>
> I believe so. Please test and report back (I'd like confirmation 
> either way).
>
> > Date: Wed, 26 Jun 2013 02:11:19 +0530
> > From: chentala.srini...@gmail.com
> > To: wix-users@lists.sourceforge.net
> > Subject: Re: [WiX-users] Require admin rights to msp
> >
> > Hi,
> >
> > The actual requirement is
> > I have a msi which is having elevated rights(InstallPrivileges 
> > ="elevated", Privileged Launched condition and digitally signed).
> >
> > And simply created the patch by following the Link:
> > http://wix.sourceforge.net/manual-wix2/patch_building.htm with out 
> > adding signing or any additional things, This is working sucessfully 
> > in all machine except the machines having UAC on. If we run the msp 
> > through AdminCommandPrompt it works fine(executing Impersonate="yes"
> > customactions) on UAC-ON machine also.
> >
> > Signing the msp is the solution for this problem?
> >
> > Regards,
> > Srinivas.
> >
> > On Tue, Jun 25, 2013 at 11:24 PM, Blair Murri  wrote:
> >
> > > Method #2 - apply from an elevated command prompt.
> > >
> > > I'm a little unclear about the requirement. If the MSI requires 
> > > elevation, any applied MSP will prompt for elevation as needed and 
> > > all non-impersonated in-script actions will run elevated (same as 
> > > the MSI, adding an MSP doesn't change how that works).
> > >
> > > If the original MSI doesn't require elevation and the MSP 
> > > introduces that requirement (due to some new thing its doing) then 
> > > LUA patching won't accommodate that requirement. You really should 
> > > use a major upgrade (and possibly a bootstrapper that gives you a 
> > > working upgrade path) to replace that original MSI.
> > >
> > > Blair
> > >
> > > > From: jacob.hoo...@greenheck.com
> > > > To: wix-users@lists.sourceforge.net
> > > > Date: Tue, 25 Jun 2013 17:10:15 +
> > > > Subject: Re: [WiX-users] Require admin rights to msp
> > > >
> > > > Digitally sign the original MSI, include the public cert in the
> > > MsiPatchCertificate table, and then sign the MSP with the same
> certificate.
> > > >
> > > > 
> > > >   
> > > > 
> > > >
> > > > And in the wixproj,
> > > >
> > >

Re: [WiX-users] Require admin rights to msp

[David Watson]

What Jacob suggests works, we have been using it for several years, if the
certificate is in the original msi and it and the patch are signed by the
same certificate then you do not need to elevate to install.

It's fun when the certificate expires though as you need to use a hotfix to
deliver the new certificate which is signed by the old certificate before it
expires so you can then sign by the new certificate in future patches.

-Original Message-
From: Blair Murri [mailto:os...@live.com] 
Sent: 26 June 2013 06:53
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Require admin rights to msp

I believe so. Please test and report back (I'd like confirmation either way).
 
> Date: Wed, 26 Jun 2013 02:11:19 +0530
> From: chentala.srini...@gmail.com
> To: wix-users@lists.sourceforge.net
> Subject: Re: [WiX-users] Require admin rights to msp
> 
> Hi,
> 
> The actual requirement is
> I have a msi which is having elevated rights(InstallPrivileges 
> ="elevated", Privileged Launched condition and digitally signed).
> 
> And simply created the patch by following the Link:
> http://wix.sourceforge.net/manual-wix2/patch_building.htm with out 
> adding signing or any additional things, This is working sucessfully 
> in all machine except the machines having UAC on. If we run the msp 
> through AdminCommandPrompt it works fine(executing Impersonate="yes" 
> customactions) on UAC-ON machine also.
> 
> Signing the msp is the solution for this problem?
> 
> Regards,
> Srinivas.
> 
> On Tue, Jun 25, 2013 at 11:24 PM, Blair Murri  wrote:
> 
> > Method #2 - apply from an elevated command prompt.
> >
> > I'm a little unclear about the requirement. If the MSI requires 
> > elevation, any applied MSP will prompt for elevation as needed and 
> > all non-impersonated in-script actions will run elevated (same as 
> > the MSI, adding an MSP doesn't change how that works).
> >
> > If the original MSI doesn't require elevation and the MSP introduces 
> > that requirement (due to some new thing its doing) then LUA patching 
> > won't accommodate that requirement. You really should use a major 
> > upgrade (and possibly a bootstrapper that gives you a working 
> > upgrade path) to replace that original MSI.
> >
> > Blair
> >
> > > From: jacob.hoo...@greenheck.com
> > > To: wix-users@lists.sourceforge.net
> > > Date: Tue, 25 Jun 2013 17:10:15 +
> > > Subject: Re: [WiX-users] Require admin rights to msp
> > >
> > > Digitally sign the original MSI, include the public cert in the
> > MsiPatchCertificate table, and then sign the MSP with the same
certificate.
> > >
> > > 
> > >   
> > > 
> > >
> > > And in the wixproj,
> > >
> > >   
> > > http://timestamp.digicert.com /a "%(SignCabs.FullPath)"" 
> > />
> > >   
> > >
> > >   
> > > http://timestamp.digicert.com /a 
> > "%(SignMsi.FullPath)"" />
> > >   
> > >
> > > I use custom logic to detect the location of SignTool, but that 
> > > should
> > get you started.  Note, group policy can still disable LUA patching.
> > >
> > > -Original Message-
> > > From: chintala srinivas [mailto:chentala.srini...@gmail.com]
> > > Sent: Tuesday, June 25, 2013 11:53 AM
> > > To: General discussion for Windows Installer XML toolset.
> > > Subject: [WiX-users] Require admin rights to msp
> > >
> > > Hi,
> > >
> > > I have a patch(.msp) file which will works fine only if it runs 
> > > from
> > administrative command prompt on UAC on machine.
> > > Can anyone please let me know how to give admin privileges to .msp.
> > >
> > > Regards,
> > > Srinivas.
> > >
> > 
> > --
> > > This SF.net email is sponsored by Windows:
> > >
> > > Build for Windows Store.
> > >
> > > http://p.sf.net/sfu/windows-dev2dev
> > > ___
> > > WiX-users mailing list
> > > WiX-users@lists.sourceforge.net
> > > https://lists.sourceforge.net/lists/listinfo/wix-users
> > >
> > >
> > 
> > --
> > > This SF.net email is sponsored by Windows:
> > >
> > > Build for Windows Store.
> > >
> > > http://p.sf.net/sfu/windows-dev2dev
> > > ___
> > > WiX-users mailing list
> > > WiX-users@lists.sourceforge.net
> > > https://lists.sourceforge.net/lists/listinfo/wix-users
> >
> >
> > 
> > -- This SF.net email is sponsored by Windows:
> >
> > Build for Windows Store.
> >
> > http://p.sf.net/sfu/windows-dev2dev
> > ___
> > WiX-users mailing list
> > WiX-users@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/wix-users
> >
> --
>  This SF.net email is sponsored by Windows:
> 
> Build for Windows Store.
> 
> http://p.sf.net/sfu/windows-d

Re: [WiX-users] Installing a ExePackage with many payloads

[David Watson]

Do a search/replace on the generated components wix or use an xslt to
transform it into payloads if it's something you will need to do repeatedly,
in fact you can pass an xslt to heat to transform it for you.

-Original Message-
From: nianderneves [mailto:niander.ne...@gmail.com] 
Sent: 25 June 2013 19:33
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Installing a ExePackage with many payloads

I tried to use the Heat.exe to create the PayloadGroup, but the heat has just
generated components





--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Installing-a-Ex
ePackage-with-many-payloads-tp7586808p7586843.html
Sent from the wix-users mailing list archive at Nabble.com.

-
-
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev
___
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.


--
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Passing properties to merge modules

[David Watson]

I assume that the type has to match the field type in the table into which
you are substituting the value, in this case the Target Column in the
CustomAction table which is of type formatted which is text.

-Original Message-
From: TimM [mailto:timmay...@smarttech.com] 
Sent: 19 June 2013 15:26
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Passing properties to merge modules

Okay if I change the Configuration format to Text then the projects all build
and it seems to work. So it does not seem to like it if the format is
Integer?

So this will work for now as I did not need this value to actually be
integer so it works fine as Text, but if if a value actually needs to be an
integer then more work would have to be done here to figure out why that did
not initially work for me.

Tim.



--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Passing-propert
ies-to-merge-modules-tp5417112p7586701.html
Sent from the wix-users mailing list archive at Nabble.com.

-
-
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev
___
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.


--
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Passing properties to merge modules

[David Watson]

Don't you need an = in the substitution value?



It's been a long time since I did this
(http://wyrdfish.wordpress.com/2011/01/05/configurable-merge-modules/) so I
may be wrong.

-Original Message-
From: TimM [mailto:timmay...@smarttech.com] 
Sent: 18 June 2013 23:00
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Passing properties to merge modules

Okay I am trying this out and I can not seem to get it working.

We are using WiX 3.7 and all it seems to do is delete the property. Maybe I
am missing something really easy and it is just escaping me. Here is what I
have:

In Merge Module:









In Parent project:






The main differences are I am using DirectoryRef, formatting to Interger, and
the property is not initially defaulted to a value in the parent install, it
is only valid if passed on command line..

Here is bits of the install log:
MSI (s) (BC:B8) [15:46:28:947]: Command Line: FOO=1
CURRENTDIRECTORY=c:\Users\timm\Desktop CLIENTUILEVEL=2 CLIENTPROCESSID=3856
MSI (s) (BC:B8) [15:46:29:072]: PROPERTY CHANGE: Adding FOO property. Its
value is '1'.
MSI (s) (BC:B8) [15:46:43:431]: Doing action: Set_FOO Action start 15:46:43:
Set_FOO.
Action ended 15:46:43: Set_FOO. Return value 1.
MSI (s) (BC:B8) [15:46:43:603]: Doing action:
setFoo.F5F26EB0_E10F_4C42_9337_E3138BE966BC
MSI (s) (BC:B8) [15:46:43:603]: *PROPERTY CHANGE: Deleting
FOO.F5F26EB0_E10F_4C42_9337_E3138BE966BC property. Its current value is
'0'.*
Action start 15:46:43: setFoo.F5F26EB0_E10F_4C42_9337_E3138BE966BC.
Action ended 15:46:43: setFoo.F5F26EB0_E10F_4C42_9337_E3138BE966BC. Return
value 1.
Property(S): FOO = 1

So if you can see what I might be doing wrong I would appreciate finding
out...

Thanks,

Tim.



--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Passing-propert
ies-to-merge-modules-tp5417112p7586685.html
Sent from the wix-users mailing list archive at Nabble.com.

-
-
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev
___
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.


--
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Patching error

[David Watson]

If you install your program on a test machine then run a repair from ARP or
the command line does it fail with the same error?

If you have not persisted these settings then they will be undefined or set
to whatever default you specified during a repair or patch, unless you only
install patches from the command line and re-specify the parameters. Error
0x80070103 is "No more data is available." which suggests that the properties
are unset.

The 'ignoring' message is a warning when properties are not secure (i.e. you
did not set the @secure attribute on the property definition) that means it
does not get passed between the execute and ui sequences. It's usually a good
idea to do this for public properties.

Dave

-Original Message-
From: George Fleming [mailto:gef...@microsoft.com] 
Sent: 14 June 2013 17:25
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Patching error

What do you mean by "repairs correctly"?  The patch log shows errors, so I
assumed that means it didn't repair correctly?

I don't store the values of SERVICEACCOUNT or SERVICEPASSWORD, but they are
provided via command-line parameters.  However, I just noticed from the log
these lines:

Ignoring disallowed property SERVICEACCOUNT Ignoring disallowed property
SERVICEPASSWORD

-Original Message-
From: David Watson [mailto:dwat...@sdl.com]
Sent: Friday, June 14, 2013 1:50 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Patching error

A patch application is just a repair with all relevant patch transformations
applied to the msi.
Check if your MSI repairs correctly.
Do you persist SERVICEACCOUNT and SERVICEPASSWORD?


-Original Message-
From: George Fleming [mailto:gef...@microsoft.com]
Sent: 13 June 2013 22:54
To: WiX-users@lists.sourceforge.net
Subject: [WiX-users] Patching error

I following online instructions and created a patch (msp file).  There were
no errors during the creation.  When I tried to verify the patch by applying
it, I got following error:

MSI (s) (C0:F0) [13:36:29:463]: Executing op: ActionStart(Name=CreateUser,,)
MSI (s) (C0:F0) [13:36:29:463]: Executing op:
CustomActionSchedule(Action=CreateUser,ActionType=11265,Source=BinaryData,Tar
get=**,CustomActionData=**)
MSI (s) (C0:88) [13:36:29:463]: Invoking remote custom action. DLL:
C:\Windows\Installer\MSIA410.tmp, Entrypoint: CreateUser MSI (s) (C0:9C)
[13:36:29:463]: Generating random cookie.
MSI (s) (C0:9C) [13:36:29:463]: Created Custom Action Server with PID 3760
(0xEB0).
MSI (s) (C0:A8) [13:36:29:495]: Running as a service.
MSI (s) (C0:FC) [13:36:29:495]: Hello, I'm your 32bit Elevated custom action
server.
CreateUser:  Error 0x80070103: failed to read attributes from custom action
data CustomAction CreateUser returned actual error code 1603 (note this may
not be 100% accurate if translation happened inside sandbox) Action ended
13:36:29: InstallFinalize. Return value 3.

My code that has "CreateUser" in it is:

  



  


  

I am a bit at loss as to how to fix this problem.  I have heard that when
patching, custom actions lose their parameters.  Is this true?  If util:user
is internally implemented as a custom action, how do I get around this?

Thanks,

George
-
-
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev
___
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.


-
-
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users




-
-
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

--
This SF.net email is sponsored by Windows:

B

Re: [WiX-users] Patch not visible in ARP if MSI installed via Bundle

[David Watson]

Personally I would write a patch bundle, the reason I don't do it already is
it would involve customizing our chainer and I want to move to burn so it
would be wasted effort.

The bundle arp entry and the individual msi entries are slightly confusing to
the end user but we just named the bundle one carefully. Until we migrate it
works for us.

Dave

-Original Message-
From: rowbot [mailto:james.row...@microfocus.com] 
Sent: 14 June 2013 11:45
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Patch not visible in ARP if MSI installed via Bundle

Indeed, if I rename :

HKEY_CLASSES_ROOT\Installer\Products\4109501100F01FEC\Product
Name

neither the MSI or the MSP are visible in ARP (!)

This is a real problem...

Anyone, any input?






--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Patch-not-visib
le-in-ARP-if-MSI-installed-via-Bundle-tp7586533p7586539.html
Sent from the wix-users mailing list archive at Nabble.com.

-
-
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev
___
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.


--
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Patch not visible in ARP if MSI installed via Bundle

[David Watson]

I think if you delete the key it and its updates would not be visible in ARP.


-Original Message-
From: rowbot [mailto:james.row...@microfocus.com] 
Sent: 14 June 2013 10:18
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Patch not visible in ARP if MSI installed via Bundle

Yes, patch bundle is an option but if it's just installing one MSP, a EXE
around it seems a bit clunky (and it's also another UI that needs
creating/maintaining)

I wonder if we don't hide the MSI entry (Visible="yes")... is there some way
of deleting the MSI's Uninstall key?




--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Patch-not-visib
le-in-ARP-if-MSI-installed-via-Bundle-tp7586533p7586536.html
Sent from the wix-users mailing list archive at Nabble.com.

-
-
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev
___
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.


--
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Patch not visible in ARP if MSI installed via Bundle

[David Watson]

I don't think so, this is why we don't hide our msi entries, in case someone
wants to uninstall a patch.
It would be nice if there were a way to show updates but hide the msi.

I don't use burn yet, but I believe that you can author a patch bundle which
I assume you would be able to uninstall from arp. If so it's yet another
reason for us to ditch our custom chainer.

Dave

-Original Message-
From: rowbot [mailto:james.row...@microfocus.com] 
Sent: 14 June 2013 09:40
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Patch not visible in ARP if MSI installed via Bundle

I've installed an MSI using a Bundle, and then installed an MSP..

The MSP is not visible in 'View installed updates' (!)

I presume this is because the MSI is installed with ARPSYSTEMCOMPONENT=1

This is not good news 

Is there a fix/workaround?

Thanks,




--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Patch-not-visib
le-in-ARP-if-MSI-installed-via-Bundle-tp7586533.html
Sent from the wix-users mailing list archive at Nabble.com.

-
-
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev
___
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.


--
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Patching error

[David Watson]

A patch application is just a repair with all relevant patch transformations
applied to the msi.
Check if your MSI repairs correctly.
Do you persist SERVICEACCOUNT and SERVICEPASSWORD?


-Original Message-
From: George Fleming [mailto:gef...@microsoft.com] 
Sent: 13 June 2013 22:54
To: WiX-users@lists.sourceforge.net
Subject: [WiX-users] Patching error

I following online instructions and created a patch (msp file).  There were
no errors during the creation.  When I tried to verify the patch by applying
it, I got following error:

MSI (s) (C0:F0) [13:36:29:463]: Executing op: ActionStart(Name=CreateUser,,)
MSI (s) (C0:F0) [13:36:29:463]: Executing op:
CustomActionSchedule(Action=CreateUser,ActionType=11265,Source=BinaryData,Tar
get=**,CustomActionData=**)
MSI (s) (C0:88) [13:36:29:463]: Invoking remote custom action. DLL:
C:\Windows\Installer\MSIA410.tmp, Entrypoint: CreateUser MSI (s) (C0:9C)
[13:36:29:463]: Generating random cookie.
MSI (s) (C0:9C) [13:36:29:463]: Created Custom Action Server with PID 3760
(0xEB0).
MSI (s) (C0:A8) [13:36:29:495]: Running as a service.
MSI (s) (C0:FC) [13:36:29:495]: Hello, I'm your 32bit Elevated custom action
server.
CreateUser:  Error 0x80070103: failed to read attributes from custom action
data CustomAction CreateUser returned actual error code 1603 (note this may
not be 100% accurate if translation happened inside sandbox) Action ended
13:36:29: InstallFinalize. Return value 3.

My code that has "CreateUser" in it is:

  



  


  

I am a bit at loss as to how to fix this problem.  I have heard that when
patching, custom actions lose their parameters.  Is this true?  If util:user
is internally implemented as a custom action, how do I get around this?

Thanks,

George
-
-
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev
___
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.


--
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Wix help

[David Watson]

http://wyrdfish.wordpress.com/2011/01/05/32-and-64-bit-msis-from-a-single-sou
rce-file/

-Original Message-
From: Subbiah Ganesan [mailto:subbiahtv...@gmail.com] 
Sent: 13 June 2013 06:47
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Wix help

Use wix preprocessor directives to distinguish 32 bit and 64 bit requirements
and build twice changing the preprocessor variable.


On Thu, Jun 13, 2013 at 10:24 AM, Vik Jairath wrote:

> Hello,
>
> I'm new to wix and I would appreciate some help with an issue i'm 
> encountering.  I have a Product.wxs file that has 32 bit components.  
> This is run on 64 bit and 32 bit platforms.
>
> I now need to use the same .wxs file but with some added dlls for the 
> 64 bit platform(need to be installed to program files instead of 
> program files (x86).
>
> I'd like to do this with the same .wxs file but generate two msi's.  
> Is there an easy way to do this?  I'm using Nant.
>
> Thanks in advance.
>
>
> --
>  This SF.net email is sponsored by Windows:
>
> Build for Windows Store.
>
> http://p.sf.net/sfu/windows-dev2dev
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
-
-
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev
___
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.


--
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Installing files in second directory chain?

[David Watson]

ProgramData is actually known as CommonAppDataFolder
http://msdn.microsoft.com/en-us/library/windows/desktop/aa367992(v=vs.85).asp
x

so try








Dave

-Original Message-
From: Alan Y. Balkany [mailto:alank...@yahoo.com] 
Sent: 11 June 2013 23:16
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Installing files in second directory chain?

Hello,

I'm trying to install program files and configuration files.

On Windows 7, files in the c:\Program Files tree can't be modified, so I'm
installing the config files in c:\ProgramData.  WIX won't let me.

All the WIX Directory examples I've seen have a SINGLE directory chain under
PFiles:

        
            
                
                    
                
             ...

What I want to do is have a second directory chain:

        
            
                
                    
                
            
            
                
                    
                
            
            
            
                
                    
                
            
        

where the ConfigDir is c:\ProgramData..., and I use the INKUSECONFIGDIR id to
indicate where to place the files:

        
           
                
            ...

But the files don't end up in C:\ProgramData\Jetrion\Ink Usage Calculator\...

What am I doing wrong?

Thanks!
Alan
-
-
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev
___
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.


--
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Clear property value on uninstall

[David Watson]

If you have uninstalled, the persisted property registry key should not be
there.

Check that the keys have been removed before installing your new version.


-Original Message-
From: chennam [mailto:chatrapathi.chen...@gmail.com] 
Sent: 05 June 2013 15:30
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Clear property value on uninstall

Hi,

I am making my Installer to Install into specific folder location instead of
Programfiles using a Property INSTALLLOCATION. Ans I pass its value through
command line during Installation.

MSI (c) (18:98) [08:04:53:170]: PROPERTY CHANGE: Adding INSTALLLOCATION
property. Its value is 'D:\Websites\CBUDirectUAT'.

But When I Installed previously version of MSI on same machine the
INSTALLOCATION property value was set to 'D:\Websites\CBUDirectUATAlt1' .

Now I uninstalled previous version from (ARP) and installing the new version
with new property value for INSTALLLOCATION='D:\Websites\CBUDirectUAT'.

But the installer is installing into same old location
D:\Websites\CBUDirectUATAlt1 instead of new one.

See below for log the new version MSI is changing the INSTALLLOCATION
property value to old one even though I passed new one.


Action 8:04:53: AppSearch. Searching for installed applications Action start
8:04:53: AppSearch.
AppSearch: Property: INSTALLLOCATION, Signature: REMEMBERPROPERTY MSI (c)
(18:98) [08:04:53:248]: Note: 1: 2262 2: Signature 3: -2147287038 MSI (c)
(18:98) [08:04:53:248]: PROPERTY CHANGE: Modifying INSTALLLOCATION property.
Its current value is 'D:\Websites\CBUDirectUAT'. Its new value:
'D:\Websites\CBUDirectUATAlt1\'.
Action ended 8:04:53: AppSearch. Return value 1.


I am Bit urgency with UAT. Can any one please help me to fix it and how to
clear previous property one after uninstall.


See below How i am saving the INSTALLLOCATION and help me out any statement
need to be added to it



  
   




  

  
 CMDREMEMBERPROPERTY


 





   
  


  
   
   
  



  







  



 
   








--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Clear-property-
value-on-uninstall-tp7586377.html
Sent from the wix-users mailing list archive at Nabble.com.

-
-
How ServiceNow helps IT people transform IT departments:
1. A cloud service to automate IT design, transition and operations
2. Dashboards that offer high-level views of enterprise services
3. A single system of record for all IT processes
http://p.sf.net/sfu/servicenow-d2d-j
___
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.


--
How ServiceNow helps IT people transform IT departments:
1. A cloud service to automate IT design, transition and operations
2. Dashboards that offer high-level views of enterprise services
3. A single system of record for all IT processes
http://p.sf.net/sfu/servicenow-d2d-j
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Creating multiple Minor Updates

[David Watson]

Your patch wix looks similar to mine but we use @MinorUpdateTargetRTM="yes"
on the patch element as that is what you are doing it may be worth a go.

-Original Message-
From: Joe Flynn [mailto:roo...@gmail.com] 
Sent: 22 May 2013 20:01
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Creating multiple Minor Updates

Hi All,

I have created a product MSI which is versioned 6.100.0 . I have then
successfully created a minor update which installs as 6.100.1. Below is the
patch.wxs file I use to accomplish this:




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

  


  

  



==

Everything is updated as expected when I apply this patch (MSP). I now want
to create a second patch, containing an additional file. This will be version
6.100.2, and I plan on making this cumulative, so that one could apply
6.100.2 and get the content of 6.100.1 as well. Below is the patch.wxs file
for my 6.100.2 update:

==


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

  


  
  

  


==

The patch builds as expected, and will apply to 6.100.0 without issue. The
problem arises when I attempt to go from 6.100.1 -> 6.100.2. I get the below
error in my MSI.LOG file, and the patch is not applied:

==

MSI (c) (60:50) [11:22:56:067]: SOFTWARE RESTRICTION POLICY:
C:\Public\Hotfix\EG\eguide_2.msp has a digital signature MSI (c) (60:50)
[11:22:56:070]: SOFTWARE RESTRICTION POLICY:
C:\Public\Hotfix\EG\eguide_2.msp is permitted to run at the 'unrestricted'
authorization level.
MSI (c) (60:50) [11:22:56:070]: SequencePatches starts. Product code:
{604F30E1-35F2-4E34-AA21-3E83CDE863E1}, Product version: 6.100.0.0, Upgrade
code: {7D1500B3-D638-4213-9772-894096C84768}, Product language 1033 MSI (c)
(60:50) [11:22:56:071]: Full optimizations are not possible in the patch
sequencer because new patch[es] had been added in the current transaction.
MSI (c) (60:50) [11:22:56:071]: Applicability checks need to be performed in
this transaction because new, 3.0 minor update patch[es] have been provided.
MSI (c) (60:50) [11:22:56:071]: PATCH SEQUENCER: verifying the applicability
of minor upgrade patch {B7C830A9-E120-48ED-BCC2-00C8989A5993}
against product code: {604F30E1-35F2-4E34-AA21-3E83CDE863E1}, product
version: 6.100.0.0, product language 1033 and upgrade code:
{7D1500B3-D638-4213-9772-894096C84768}
MSI (c) (60:50) [11:22:56:071]: Validating transform 'SEGPatch.1' with
validation bits 0x922 MSI (c) (60:50) [11:22:56:071]: Transform 'SEGPatch.1'
is valid.
MSI (c) (60:50) [11:22:56:071]: Note: 1: 2262 2: _Tables 3: -2147287038 MSI
(c) (60:50) [11:22:56:071]: Note: 1: 2262 2: _Columns 3: -2147287038 MSI (c)
(60:50) [11:22:56:071]: PATCH SEQUENCER: minor upgrade patch
{B7C830A9-E120-48ED-BCC2-00C8989A5993} is applicable.
MSI (c) (60:50) [11:22:56:071]: PATCH SEQUENCER: verifying the applicability
of minor upgrade patch C:\Public\Hotfix\EG\eguide_2.msp against product code:
{604F30E1-35F2-4E34-AA21-3E83CDE863E1}, product
version: 6.100.1.7000, product language 1033 and upgrade code:
{7D1500B3-D638-4213-9772-894096C84768}
MSI (c) (60:50) [11:22:56:071]: Validating transform 'SEGPatch.1' with
validation bits 0x922 MSI (c) (60:50) [11:22:56:071]: Note: 1: 2749 2:
SEGPatch.1 3:
C:\Public\Hotfix\EG\eguide_2.msp 4: 6.100.0.2789 5: 6.100.1.7000 MSI (c)
(60:50) [11:22:56:071]: 1: 2749 2: SEGPatch.1 3:
C:\Public\Hotfix\EG\eguide_2.msp 4: 6.100.0.2789 5: 6.100.1.7000 MSI (c)
(60:50) [11:22:56:071]: PATCH SEQUENCER: minor upgrade patch
C:\Public\Hotfix\EG\eguide_2.msp is not applicable.
MSI (c) (60:50) [11:22:56:071]: The #_QFESequence table with patches sorted
on Sequence within Patch Families:
MSI (c) (60:50) [11:22:56:071]: PatchGUID:
{B7C830A9-E120-48ED-BCC2-00C8989A5993} PatchFamily: SEGPatchFamily Sequence:
6.100.1 SequenceOrder: 0 Type: minor upgrade MSI (c) (60:50) [11:22:56:071]:
PATCH SEQUENCER: minor upgrade patch {B7C830A9-E120-48ED-BCC2-00C8989A5993}
cannot be superseded because there is no supersedence defined in
SEGPatchFamily family yet for this type MSI (c) (60:50) [11:22:56:071]: PATCH
SEQUENCER: minor upgrade patch {B7C830A9-E120-48ED-BCC2-00C8989A5993} will
attempt to supersede in SEGPatchFamily family, starting from sequence 6.100.1
MSI (c) (60:50) [11:22:56:071]: SequencePatches returns success.
MSI (c) (60:50) [11:22:56:071]: Final Patch Application Order:
MSI (c) (60:50) [11:22:56:071]: {B7C830A9-E120-48ED-BCC2-00C8989A5993} - MSI
(c) (60:50) [11:22:56:071]: Other Patches:
MSI (c) (60:50) [11:22:56:071]: Unknown\Absent:
{34353211-73FE-4960-9F31-FBEF2451A3AD} - C:\Public\Hotfix\EG\eguide_2.msp The
upgrade cannot be installed by the Windows Installer service because the
program to be upgraded may be missing, or the upgrade may update a different
version of the program. Verify tha

Re: [WiX-users] Specifying IIS app pool user (and password) viaproperties

[David Watson]

The User can be an Id of a  which in turn can have Domain, Name
and Password set as properties.

e.g. 



Dave

-Original Message-
From: Patrick Kristiansen [mailto:patr...@patrkris.dk] 
Sent: 21 May 2013 12:24
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Specifying IIS app pool user (and password)
viaproperties

Hi

Is it possible to specify the user that an IIS WebAppPool runs under through
a property?

Currently I'm getting an error when trying to build the .msi package and have
set 



Thanks in advance,
Patrick

-
-
Try New Relic Now & We'll Send You this Cool Shirt New Relic is the only
SaaS-based application performance monitoring service that delivers powerful
full stack analytics. Optimize and monitor your browser, app, & servers with
just a few lines of code. Try New Relic and get this awesome Nerd Life shirt!
http://p.sf.net/sfu/newrelic_d2d_may
___
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.


--
Try New Relic Now & We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring service 
that delivers powerful full stack analytics. Optimize and monitor your
browser, app, & servers with just a few lines of code. Try New Relic
and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Heat - Include question

[David Watson]

The usual thing to do here is generate wix file with everything in
componentgroup , then include a componentgroupref in a feature in your main
wxs file.

You can use Orca or Insted to open an msi file to see if contains what you
want.

Dave

-Original Message-
From: BGINFO4X [mailto:bginf...@kztsoftware.com] 
Sent: 17 May 2013 14:56
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Heat - Include question

Hello everyone,

I'm a new to WIX and I'm a little lost.

I want to create a .msi file from my project (with lots of files and
folders), so I use HEAT.
Heat works as exepcted and a new file is created (SampleGroup.wxs).

Then I try to "compile all" : "C:\Program Files\WiX Toolset v3.7\bin\candle"
SampleFirst.wxs SampleGroup.wxs

Until here all is ok, but the installed folder is EMPTY.

Why WIX doesn't include my source files from SampleGroup.wxs?

What I'm doing wrong? I need to add something in the main file
SampleFirst.wxs? Where and what?

Thanks a lot.

-
-
AlienVault Unified Security Management (USM) platform delivers complete
security visibility with the essential security capabilities. Easily and
efficiently configure, manage, and operate all of your security controls from
a single console and one unified framework. Download a free trial.
http://p.sf.net/sfu/alienvault_d2d
___
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.


--
AlienVault Unified Security Management (USM) platform delivers complete
security visibility with the essential security capabilities. Easily and
efficiently configure, manage, and operate all of your security controls
from a single console and one unified framework. Download a free trial.
http://p.sf.net/sfu/alienvault_d2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] error: system cannot open the device or file specified

[David Watson]

1) This http://support.microsoft.com/kb/834549 ?
2) Heat thinks the .exe is a com server, as it is another installer you can
ignore it. If you are bundling several packages together you may want to look
at the burn bootstrapper which will handle this much better than embedding
the sub installers in an msi.
3&4) Try manually running the compilation from the command line and
hardcoding some values until you work out which bit is wrong, or add
everything to a wixproj / solution if you have that option.


-Original Message-
From: jo...@msli.com [mailto:jo...@msli.com] 
Sent: 17 May 2013 00:16
To: WixUsers
Subject: [WiX-users] error: system cannot open the device or file specified

I am trying to setup a new wix project, but I am running into a few problems
and would love some help.

Below I include links to my wxs, wxi, ant build, and install logs so that you
may save me from this fiery hell.

Link to resources:https://gist.github.com/johnstile/5595744
It includes:
 build.xml : ant script calling heat, candle, light, and msiexec.
 MyProgram.wxs : wix project file
 MyProgram.variables.wxi - variables file  msi_install_log.txt - my failing
install log  build_log.txt - output from running: ant light

First issue: 

All my installers fail with error:

 "The system cannot open the device or file specified."

 See: msi_install_log.txt
 it isn't empty, and the paths look sane.
 What's the problem?

Second issue:

 heat warns about 5 files files, with errors like:

heat.exe : warning HEAT5150 : Could not harvest data from a file that was
expected to be a SelfReg DLL: C:\cygwin\home\build\current\EUROPA
\ProgramFiles\WinPcap_4_1_2.exe. If this file does not support SelfReg you
can ignore this warning. Otherwise, this error detail may be helpful to
diagnose the failure: Unable to load file: C:\cygwin\home\build
\current\EUROPA\ProgramFiles\WinPcap_4_1_2.exe, error: 5

 See: build_log.txt

 I need to distribute this exe as part of my installer, and there are other
exe's as well.  My installer will have to offer to install the other programs
if they are not installed already.

Third issue:

  I can't get preprocessor includes to read my wxi files.
  Either it errors with a path problem: 

C:\cygwin\home\build\current\EUROPA\Source\Compass.wxs(2) : error
CNDL0103 : The system cannot find the file 'Source/Compass.variables.wxi '
with type 'include'.Source trace:
C:\cygwin\home\build\current\EUROPA\Source\Compass.wxs: line 2

  Or it says my file is invalid.
  See: MyProgram.variables.wxi

Fourth issue:

  I can't get find a wild card for light to use all wixobj files under the
wixobj directory generated by candle.

Thank you for taking a look.


NOTICE: This email may contain confidential information.  Please see
http://www.meyersound.com/confidential/ for our complete policy.

-
-
AlienVault Unified Security Management (USM) platform delivers complete
security visibility with the essential security capabilities. Easily and
efficiently configure, manage, and operate all of your security controls from
a single console and one unified framework. Download a free trial.
http://p.sf.net/sfu/alienvault_d2d
___
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.


--
AlienVault Unified Security Management (USM) platform delivers complete
security visibility with the essential security capabilities. Easily and
efficiently configure, manage, and operate all of your security controls
from a single console and one unified framework. Download a free trial.
http://p.sf.net/sfu/alienvault_d2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Speed up installer for copy file using Heat

[David Watson]

Do you use the -suid heat option?


-Original Message-
From: Marco Tognacci [mailto:mark...@live.it] 
Sent: 15 May 2013 23:26
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Speed up installer for copy file using Heat

Yes, it could be possible to make an extension for changing the Ids as they
report location path, as the file will be ordered in the MSI table grouped by
their directory location?Or is there a way for naming the Ids generated by
heat as to report the directory path?My old Installation made by
InstallShield is very very faster than wix.


> From: dan.mad...@quanser.com
> To: wix-users@lists.sourceforge.net
> Date: Wed, 15 May 2013 16:13:56 -0400
> Subject: Re: [WiX-users] Speed up installer for copy file using Heat
> 
> I think he wants the component Ids to be such that if the component Ids are
sorted alphabetically then they end up in the same order as the files
themselves when the files are sorted alphabetically.
> 
> Dan
> 
> -Original Message-
> From: Neil Sleightholm [mailto:n...@x2systems.com]
> Sent: May-15-13 4:08 PM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Speed up installer for copy file using Heat
> 
> You shouldn't need to do this as WiX takes care of it for you, the files
are stored in the cab in alphabetical order no matter what order they are in
you source.
> 
> Neil
> 
> -Original Message-
> From: Marco Tognacci [mailto:mark...@live.it]
> Sent: 15 May 2013 21:03
> To: wix-users@lists.sourceforge.net
> Subject: [WiX-users] Speed up installer for copy file using Heat
> 
> I have used heat for harvest the files to install in my application. I have
read that to make install of file faster the Ids of the files that are
located in the same forder must be alphabetically consecutive so that they
will be installed in sequence, so is there some optimization for generating
the Ids for hte harvested file to follow the folder file path?Perhaps it
could be used a transformation *.xslt, do you know how it could be
defined?Thanks.   
> --
>  AlienVault Unified Security Management (USM) platform 
> delivers complete security visibility with the essential security
capabilities. Easily and efficiently configure, manage, and operate all of
your security controls from a single console and one unified framework.
Download a free trial.
> http://p.sf.net/sfu/alienvault_d2d
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
> 
> --
>  AlienVault Unified Security Management (USM) platform 
> delivers complete security visibility with the essential security 
> capabilities. Easily and efficiently configure, manage, and operate 
> all of your security controls from a single console and one unified 
> framework. Download a free trial.
> http://p.sf.net/sfu/alienvault_d2d
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
> 
> --
>  AlienVault Unified Security Management (USM) platform 
> delivers complete security visibility with the essential security 
> capabilities. Easily and efficiently configure, manage, and operate 
> all of your security controls from a single console and one unified 
> framework. Download a free trial.
> http://p.sf.net/sfu/alienvault_d2d
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
  
-
-
AlienVault Unified Security Management (USM) platform delivers complete
security visibility with the essential security capabilities. Easily and
efficiently configure, manage, and operate all of your security controls from
a single console and one unified framework. Download a free trial.
http://p.sf.net/sfu/alienvault_d2d
___
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.


--

Re: [WiX-users] WinRt/Metro App Sideloading installer

[David Watson]

Interesting, I looked into it briefly and didn't think it would be possible
due to all the hoops you have to jump through.



-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com] 
Sent: 15 May 2013 21:58
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] WinRt/Metro App Sideloading installer

Yes. Something to do. Haven't seen a lot of discussion about it yet, though.


On Wed, May 15, 2013 at 1:27 PM, Kevin Anthony
wrote:

> Is there plans in the future to include sideloading of windows 
> Runtime/Metro style apps?
>
> Thank you
> Kevin
>
> Kevin Anthony
>
>
> --
>  AlienVault Unified Security Management (USM) platform 
> delivers complete security visibility with the essential security 
> capabilities. Easily and efficiently configure, manage, and operate 
> all of your security controls from a single console and one unified 
> framework. Download a free trial.
> http://p.sf.net/sfu/alienvault_d2d
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
>
-
-
AlienVault Unified Security Management (USM) platform delivers complete
security visibility with the essential security capabilities. Easily and
efficiently configure, manage, and operate all of your security controls from
a single console and one unified framework. Download a free trial.
http://p.sf.net/sfu/alienvault_d2d
___
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.


--
AlienVault Unified Security Management (USM) platform delivers complete
security visibility with the essential security capabilities. Easily and
efficiently configure, manage, and operate all of your security controls
from a single console and one unified framework. Download a free trial.
http://p.sf.net/sfu/alienvault_d2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] upgrade mysteriously installs older file version

[David Watson]

The major upgrade pattern seems to be what you were trying to achieve and
it's the tried and trusted way of getting what you want.

Follow this http://wix.sourceforge.net/manual-wix3/major_upgrade.htm

Do not mess with reinstallmode in your bootstrapper, leave the defaults. You
could even use burn to replace your bootstrapper.

Hopefully the default early scheduling of RemoveExistingProducts will clean
out the previous confusion.

If you really want to delve into the minutiae of what is going wrong get a
verbose log and look at what the WI is doing on each file.

Dave


-Original Message-
From: József Koloszár [mailto:j...@erad.com] 
Sent: 08 May 2013 11:51
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] upgrade mysteriously installs older file version

hi all,

it's been a while, which means wix has worked great for us for a long time
now, but just recently we've hit a weird one:

we're providing regular upgrades packaged as msi's bootstrapped in an exe.
(the exe places the msi into windows temp, and invokes the lib equivalent of
msiexec /i blahblah.msi reinstall=all reinstallmode=vamus. (product and
upgrade codes are persistent across version, we change the package id -
there's only one package... and this has worked for years now).

we've recently started seeing incidents (on win7 mostly), where running the
installer of newer version would not replace files with the newer versions
contained in the msi. details: suppose msi version 1.1 of the product was
installed, which correctly deployed version 2.4 of file blahblah.exe to the
program folder. trying to install version 1.2, which contains v2.5 of
blahblah.exe (with the proper upgrade options mentioned above), the installer
runs (interactive ui clicked through with nexts) displays all the usual
(removing existing, copying new files, publishing product...), but in the end
the program folder still contains v2.4 of blahblah.exe.
- a restart does NOT help
- files and their versions are verified (used orca to make sure), double and
tripple checked.
- also did all tests manually (through msiexec command line), same results.
- we can't pin the behavior to specific versions or specific workstations, it
just happens. we've reproduced by going through versions, and at some point
it would just happen, not always between the same versions.
- even if i manually delete v2.4 exe and then run the 1.2 installer that
should deploy v2.5, from some magical cache winstaller still manages to
conjure v2.4 instead. it's mind numbing
- of course manually uninstalling the older version before installing the new
one works, but is not an acceptable workaround (ad deployment, grumpy users,
etc...)

any thoughts on what could be causing this? what are we missing? where to
look?

thanks to all in advance.

cheers,

joe
-
-
Learn Graph Databases - Download FREE O'Reilly Book "Graph Databases" is the
definitive new guide to graph databases and their applications. This 200-page
book is written by three acclaimed leaders in the field. The early access
version is available now. 

Download your free book today! http://p.sf.net/sfu/neotech_d2d_may
___
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.


--
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and 
their applications. This 200-page book is written by three acclaimed 
leaders in the field. The early access version is available now. 
Download your free book today! http://p.sf.net/sfu/neotech_d2d_may
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Skip Bundle Condition

[David Watson]

Add a SKIPCONDITIONS property to each of your conditions and pass that in.

-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com] 
Sent: 08 May 2013 09:31
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Skip Bundle Condition

You could implement that in a custom BA. The wixstdba doesn't have such a
concept.


On Wed, May 8, 2013 at 1:11 AM, Sam Boman  wrote:

> Is there any way to do like this when installing an application when 
> using Bundle bootstrapper:
> installer.exe /skip-conditions
>
> To make the installation run without checking the conditions 
> (VersionNT, ServicePackLevel).
>
> Best regards,
> Sam Boman
>
> --
>  Learn Graph Databases - Download FREE O'Reilly Book "Graph 
> Databases" is the definitive new guide to graph databases and their 
> applications. This 200-page book is written by three acclaimed leaders 
> in the field. The early access version is available now.
> Download your free book today! http://p.sf.net/sfu/neotech_d2d_may
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
>
-
-
Learn Graph Databases - Download FREE O'Reilly Book "Graph Databases" is the
definitive new guide to graph databases and their applications. This 200-page
book is written by three acclaimed leaders in the field. The early access
version is available now. 

Download your free book today! http://p.sf.net/sfu/neotech_d2d_may
___
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.


--
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and 
their applications. This 200-page book is written by three acclaimed 
leaders in the field. The early access version is available now. 
Download your free book today! http://p.sf.net/sfu/neotech_d2d_may
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Custom Action Extraction Issue

[David Watson]

I was guessing at what exactly you are doing. Yes get the utility to do its
own impersonation.

Or run a post install configuration utility.

-Original Message-
From: Joe Barker [mailto:joeb...@gmail.com] 
Sent: 03 May 2013 10:11
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Custom Action Extraction Issue

I'm already passing the credential info into the CA. Do you mean passing it
to the CA, to the pass to the utility and run impersonation in there?


I'll have to look and see if there's a way we can guarantee that the utility
will be called on first run, as our application is a web-based application,
so it's a little more difficult, as it only needs to be ran once per
server/install.

On Fri, May 3, 2013 at 9:53 AM, David Watson  wrote:

> Can you pass the credential info to the CA and do the impersonation 
> inside the utility?
> Or install the utility and call it on first run?
> -Original Message-
> From: Joe Barker [mailto:joeb...@gmail.com]
> Sent: 02 May 2013 16:36
> To: wix-users@lists.sourceforge.net
> Subject: [WiX-users] Custom Action Extraction Issue Hi, In my 
> installer, I have the user enter a domain/user/password combination at 
> the beginning which is then used as the user account to run an 
> application pool in IIS. This combination of domain/user/password is 
> then later impersonated as part of a custom action, which runs an 
> executable to handle some other application specifics before the installer
finishes.
> This custom action fails, however, unless I run the installer from a 
> command prompt that was launched with administrative privileges. After 
> some investigation, we've found that this is because the msi that's 
> executed from the administrative command prompt extracts CA's to 
> C:\Windows\Installer\, which means the impersonated user can read the 
> files; when the msi is executed from a normal prompt, or the GUI, CA's 
> are extracted to C:\Users\\AppData\Local\Temp\ (or somewhere 
> around there), meaning the user that's being impersonated doesn't have 
> permission to the folder, and therefore an exception is thrown.
> Is there any way to either control where the CA is extracted to, or to 
> work around this issue? Not impersonating the user isn't an option,
unfortunately.
> Any help would be much appreciated.
> Thanks,
> Joe
> --
> ---
> -
> Introducing AppDynamics Lite, a free troubleshooting tool for 
> Java/.NET Get 100% visibility into your production application - at no
cost.
> Code-level diagnostics for performance bottlenecks with <2% overhead 
> Download for free and get started troubleshooting in minutes.
> http://p.sf.net/sfu/appdyn_d2d_ap1
> ___
> 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.
> --
>  Get 100% visibility into Java/.NET code with AppDynamics Lite 
> It's a free troubleshooting tool designed for production Get down to 
> code-level detail for bottlenecks, with <2% overhead.
> Download for free and get started troubleshooting in minutes.
> http://p.sf.net/sfu/appdyn_d2d_ap2
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
-
-
Get 100% visibility into Java/.NET code with AppDynamics Lite It's a free
troubleshooting tool designed for production Get down to code-level detail
for bottlenecks, with <2% overhead.
Download for free and get started troubleshooting in minutes.
http://p.sf.net/sfu/appdyn_d2d_ap2
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

--
Get 100% visibility into Java/.NET code with AppDynamics Lite
It's a free troubleshooting tool designed for production
Get down to code-level detail for bottlenecks, with <2% overhead.
Download for free and get started troubleshooting in minutes.
http://p.sf.net/sfu/appdyn_d2d_ap2
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Custom Action Extraction Issue

[David Watson]

Can you pass the credential info to the CA and do the impersonation inside
the utility?

Or install the utility and call it on first run?

-Original Message-
From: Joe Barker [mailto:joeb...@gmail.com] 
Sent: 02 May 2013 16:36
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Custom Action Extraction Issue

Hi,

In my installer, I have the user enter a domain/user/password combination at
the beginning which is then used as the user account to run an application
pool in IIS. This combination of domain/user/password is then later
impersonated as part of a custom action, which runs an executable to handle
some other application specifics before the installer finishes.

This custom action fails, however, unless I run the installer from a command
prompt that was launched with administrative privileges. After some
investigation, we've found that this is because the msi that's executed from
the administrative command prompt extracts CA's to C:\Windows\Installer\,
which means the impersonated user can read the files; when the msi is
executed from a normal prompt, or the GUI, CA's are extracted to
C:\Users\\AppData\Local\Temp\ (or somewhere around there), meaning the
user that's being impersonated doesn't have permission to the folder, and
therefore an exception is thrown.

Is there any way to either control where the CA is extracted to, or to work
around this issue? Not impersonating the user isn't an option, unfortunately.
Any help would be much appreciated.

Thanks,
Joe
-
-
Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET Get
100% visibility into your production application - at no cost.
Code-level diagnostics for performance bottlenecks with <2% overhead Download
for free and get started troubleshooting in minutes.
http://p.sf.net/sfu/appdyn_d2d_ap1
___
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.


--
Get 100% visibility into Java/.NET code with AppDynamics Lite
It's a free troubleshooting tool designed for production
Get down to code-level detail for bottlenecks, with <2% overhead.
Download for free and get started troubleshooting in minutes.
http://p.sf.net/sfu/appdyn_d2d_ap2
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Properties Summary Tab Is Editable

[David Watson]

Interesting question and I've never noticed or thought about it.
By default it looks like you can edit the properties of any data file like
that, .exes seem to be blocked.
If you digitally sign your MSIs then the signature is broken if these are
edited, which is expected.
You can make the file read only to stop casual editing of the properties, so
I may start doing that in my build process.

Dave

-Original Message-
From: GregS [mailto:gsh...@actuate.com] 
Sent: 30 April 2013 23:01
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Properties Summary Tab Is Editable

I'm new to WiX so apologies if the answer to this question is obvious.

I've got my WiX installer working properly, but there's an odd problem with
the MSI. When you open the MSI's property tabsheet (by right-clicking on the
MSI in the Windows file explorer and selecting "Properties"), all the fields
on the Summary tab are editable: Title, Subject, Author, Comments, etc.
Actually all the fields on all the tabs are editable, but Summary is the
worst because it displays things, like the company name and copyright dates,
that users should not be able to edit.

I've seen this on Windows 7 and Windows XP.

Any idea of what would cause this? Is there an attribute I need to set in the
WiX XML to tell it these things should be read-only?

Thanks,
Greg S.



--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Properties-Summ
ary-Tab-Is-Editable-tp7585523.html
Sent from the wix-users mailing list archive at Nabble.com.

-
-
Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET Get
100% visibility into your production application - at no cost.
Code-level diagnostics for performance bottlenecks with <2% overhead Download
for free and get started troubleshooting in minutes.
http://p.sf.net/sfu/appdyn_d2d_ap1
___
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.


--
Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET
Get 100% visibility into your production application - at no cost.
Code-level diagnostics for performance bottlenecks with <2% overhead
Download for free and get started troubleshooting in minutes.
http://p.sf.net/sfu/appdyn_d2d_ap1
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] AllowDowngrades="yes" warning LGHT1076 : ICE61

[David Watson]

I think that using downgrades to support a rollback scenario is slightly
dangerous in that the user may not realize that they are putting an earlier
version on as it just gets on with it.

Most people block downgrades and let their users un-install and re-install an
older version or have any patch be un-installable to support downgrades. It's
also an extra set of scenarios to test. Do you run any upgrade configuration
that would need to be reversed? If so would you know in advance when you
release your old installer how to reverse it bearing in mind your future
version has not been written yet?

Also balance the support costs of people downgrading by accident and
contacting support against the slight pain of having to uninstall by hand to
install an older version.


-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com] 
Sent: 15 April 2013 16:55
To: afor...@cmu.edu; General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] AllowDowngrades="yes" warning LGHT1076 : ICE61

Yes. Curious why you want to support downgrades? Don't hear that very often.


On Mon, Apr 15, 2013 at 8:51 AM, Alain Forget  wrote:

> This is very insightful, thanks! So my MajorUpgrade tag looks like this:
>
>  />
>
> The WiX manual ( 
> http://wix.sourceforge.net/manual-wix3/major_upgrade.htm) says that 
> the Schedule="afterInstallInitialize" puts the RemoveExistingProducts
before anything is installed. So I think this is good, safe, and the way we
want it, correct?
>
> You also made a very good observation about possible shared resources.
> Fortunately, our software isn't installing anything that other 
> programs use (at least I can't imagine how that can happen).
>
> Alain
>
> -Original Message-
> From: Phil Wilson [mailto:phil.wil...@mvps.org]
> Sent: April 14, 2013 15:52
> To: 'General discussion for Windows Installer XML toolset.'
> Subject: Re: [WiX-users] AllowDowngrades="yes" warning LGHT1076 : 
> ICE61
>
> If your downgrade is effectively the same as an uninstall of the old 
> product followed by an install of the new product you should be ok, 
> and that depends on early sequencing of RemoveExistingProducts.
>
> If your RemoveExistingProducts is at the end somewhere, the upgrade is 
> like a merge of the components  (when coomponent guids are unchanged), 
> and that's true of what you call a downgrade or an upgrade. I don't 
> think Windows suspends the file version overwrite rules, and so will 
> still apply them. If your old version has files with version 5.0, and 
> the new one has versions of
> 6.0 a downgrade may leave you with the old version product with the 
> 6.0 file versions. That's my recollection anyway, and that's why the 
> best downgrade is simply to uninstall the broken new product and 
> reinstall the old one from the install media that you kept, right?
>
> Keep in mind components can be shared - let's say your new product 
> installed new shared Microsoft components that updated files because 
> of file version rules. Uninstalling that new product will simply 
> decrease the ref count on them and the new versions will remain on the 
> system. Reinstalling your older product will also apply file version 
> rules and those Microsoft files will not be replaced with older 
> versions from your older install. That's the same thing that happens 
> when your REP is at the end. So I think that's the issue
> - you can end up with an "older" product with a mishmash of file 
> versions that were probably never designed or tested to work together. 
> Obviously deserves a test and a sanity check to be sure I'm 
> remembering this correctly.
>
> Phil
>
>
> -Original Message-
> From: Alain Forget [mailto:afor...@cmu.edu]
> Sent: Saturday, April 13, 2013 1:54 PM
> To: wix-users@lists.sourceforge.net
> Subject: [WiX-users] AllowDowngrades="yes" warning LGHT1076 : ICE61
>
> I've recently added the AllowDowngrades="yes" attribute to my 
> MajorUpgrade element, which resulted in the following light warning:
>
> warning LGHT1076 : ICE61: This product should remove only older 
> versions of itself. No Maximum version was detected for the current 
> product.
> (WIX_UPGRADE_DETECTED)
>
> In a similar post ( see http://sourceforge.net/p/wix/bugs/2405/ ), Rob 
> explains that the warning is produced by the Windows Installer / ICE 
> team, and that they believe allowing downgrades or same version 
> upgrades is a bad idea.
>
> The reason I think we need to enable downgrades is if we push a new 
> major upgrade, but find out there's some critical and hard-to-fix flaw 
> we missed, and then want to quickly and easily rollback to an older 
> version.
>
> So the warning is making me wonder if there's a flaw in my logic. Your 
> thoughts?
>
> Alain
>
>
> ***
> Alain Forget, Ph.D.
> Postdoctoral Researcher
> CyLab, Carnegie Mellon University
> afor...@cmu.edu
> http://cups.cs.cmu.edu/~aforget/
> ***
>
>
>
>

Re: [WiX-users] Slow Installs

[David Watson]

Antivirus or index server are favourites.


-Original Message-
From: Dexter [mailto:d8x...@hotmail.com] 
Sent: 15 April 2013 15:33
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Slow Installs

Thank your for all the suggestions. I had already included many of the
suggestions into the original installation. I am now in the process of
determining why this occurs on only a few machines while others work fine. I
just don't know what environmental settings could be causing such a drastic
reduction in installation time.

Thank you,
Dex.



--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Slow-Installs-t
p7585123p7585153.html
Sent from the wix-users mailing list archive at Nabble.com.

-
-
Precog is a next-generation analytics platform capable of advanced analytics
on semi-structured data. The platform includes APIs for building apps and a
phenomenal toolset for data science. Developers can use our toolset for easy
data analysis & visualization. Get a free account!
http://www2.precog.com/precogplatform/slashdotnewsletter
___
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.


--
Precog is a next-generation analytics platform capable of advanced
analytics on semi-structured data. The platform includes APIs for building
apps and a phenomenal toolset for data science. Developers can use
our toolset for easy data analysis & visualization. Get a free account!
http://www2.precog.com/precogplatform/slashdotnewsletter
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Referencing filenames (without full path) anddirectories in formatted strings

[David Watson]

Indeed, directories are properties.

http://blogs.msdn.com/b/robmen/archive/2006/10/17/deciphering-the-msi-directo
ry-table-part-7-directories-are-properties.aspx


-Original Message-
From: Alain Forget [mailto:afor...@cmu.edu] 
Sent: 10 April 2013 16:02
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] Referencing filenames (without full path)
anddirectories in formatted strings

Thanks for the reply. I thought the syntax "[dirA]" was only for properties.
Does the Directory element also count as (or create) a property?

-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: April 10, 2013 10:38
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Referencing filenames (without full path) and
directories in formatted strings

What about "[dirA]".  The "[$dirA]" would be trying to get the directory of a
Component matching that Id, right?

On Mon, Apr 8, 2013 at 4:00 PM, Alain Forget  wrote:

> Hi all,
>
> Say we have the following structure:
>
> 
> 
> 
>   Name="ABC.class" DiskId='1'
> Source="source/path/to/ABC.class" KeyPath='yes' />  
>   
>
> Then later on in the .wxs file, in Custom Actions, I want to refer to 
> the above file and directory A like so:
>
>   Id="Set_cmdRunABC" Property="cmdRunABC "
> Value=""java" -cp [$dirA] "[#fileABCClass]" /> 
>  DllEntry="CAQuietExec" Return="check" Impersonate="no" />
>
> The problem lies with [$dirA] and [#fileABCClass]:
>
> 1) How can I specifically refer to an install directory location path 
> (to replace the "[$dirA]"), where no components are being installed in 
> that directory (but only in subdirectories, that have libraries and 
> stuff that ABC.class needs)?
> 2) How do I get a file's name *without* the full path (as is returned 
> by "[#fileABCClass]")?
>
> Thanks, and let me know if anything here isn't clear.
>
> Alain
>
> ***
> Alain Forget, Ph.D.
> Postdoctoral Researcher
> CyLab, Carnegie Mellon University
> afor...@cmu.edu
> http://cups.cs.cmu.edu/~aforget/
> ***
>
>
>
>
> --
>  Minimize network downtime and maximize team effectiveness.
> Reduce network management and security costs.Learn how to hire the 
> most talented Cisco Certified professionals. Visit the Employer 
> Resources Portal 
> http://www.cisco.com/web/learning/employer_resources/index.html
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
>
-
-
Precog is a next-generation analytics platform capable of advanced analytics
on semi-structured data. The platform includes APIs for building apps and a
phenomenal toolset for data science. Developers can use our toolset for easy
data analysis & visualization. Get a free account!
http://www2.precog.com/precogplatform/slashdotnewsletter
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


-
-
Precog is a next-generation analytics platform capable of advanced analytics
on semi-structured data. The platform includes APIs for building apps and a
phenomenal toolset for data science. Developers can use our toolset for easy
data analysis & visualization. Get a free account!
http://www2.precog.com/precogplatform/slashdotnewsletter
___
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.


--
Precog is a next-generation analytics platform capable of advanced
analytics on semi-structured data. The platform includes APIs for building
apps and a phenomenal toolset for data science. Developers can use
our toolset for easy data analysis & visualization. Get a free account!
http://www2.precog.com/precogplatform/slashdotnewsletter
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] How to create and reference a custom pre-requisitepackage

[David Watson]

The username and password could be stored encrypted in the bundle (when
passwords are supported or in a custom BA).
I've done this in MSIs / custom chainers before with custom actions, also for
persisting credentials in the registry.

Dave

-Original Message-
From: Spud [mailto:andysmi...@gmail.com] 
Sent: 10 April 2013 12:10
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] How to create and reference a custom
pre-requisitepackage

Thanks Neil, I knew security would be an issue / can of worms, but at least I
can now stop looking for something that doesn't exist :)

Cheers again.



--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/How-to-create-a
nd-reference-a-custom-pre-requisite-package-tp7584968p7585032.html
Sent from the wix-users mailing list archive at Nabble.com.

-
-
Precog is a next-generation analytics platform capable of advanced analytics
on semi-structured data. The platform includes APIs for building apps and a
phenomenal toolset for data science. Developers can use our toolset for easy
data analysis & visualization. Get a free account!
http://www2.precog.com/precogplatform/slashdotnewsletter
___
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.


--
Precog is a next-generation analytics platform capable of advanced
analytics on semi-structured data. The platform includes APIs for building
apps and a phenomenal toolset for data science. Developers can use
our toolset for easy data analysis & visualization. Get a free account!
http://www2.precog.com/precogplatform/slashdotnewsletter
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users