[WiX-users] [WIX]: Display UAC message while launching MSI

[dileep s]

Hi All,

How to display UAC message while launching MSI?

Currently, I am getting UAC message after Install action done in MSI.

Anyone please help me on this?

Thanks in advance...
--
Sponsored by Intel(R) XDK 
Develop, test and display web and hybrid apps with a single code base.
Download it for free now!
http://pubads.g.doubleclick.net/gampad/clk?id=111408631&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Splash Screen

[wdh61]

OK, here's the real answer.  Gimp and ImageMagik output a bmp in bmp version
4 format.  ImageMagik does that as well but can also output version 3
format.  The resulting version 3 file will display in the installer.  So,
bmp splash screen files have to be version 3 format.



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

--
Sponsored by Intel(R) XDK 
Develop, test and display web and hybrid apps with a single code base.
Download it for free now!
http://pubads.g.doubleclick.net/gampad/clk?id=111408631&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] RemoveRegistryValues executing after WriteRegistryValues?

[Brian Gillespie]

Hi,

I'm using WiX 3.5 in VS 2010.

Some of my users are experiencing a problem after performing a major
upgrade of our product. One component (WiX for the component shown below)
seems to have it's file extension and mime type properly registered during
WriteRegistryValues, and then the registration is removed because
RemoveRegistryValues executes after WriteRegistryValues.

Our application includes VS2005 runtimes, and so I think our InstallExecute
sequencing may be less than ideal, but seems to hold together for the most
part:

*Install Execute:*

  
  

  

  
  
  




*Component registration is as follows:*

  
  
  
  

  

  



*Attached is the verbose install log.*
Of note are lines:
*Line 48242*: MSI (s) (5C:20) [09:35:54:748]: Executing op:
RegAddValue(Name=Content Type,Value=application/rhi,)

*Line 62911*: MSI (s) (5C:78) [09:36:06:713]: Executing op:
RegRemoveValue(Name=Content Type,Value=application/rhi,)

Any ideas how I can fix this? Please let me know if you need any other
details.

  - Brian

Brian Gillespie
Rhinoceros Development
Robert McNeel & Associates
--
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=84349351&iu=/4140/ostg.clktrk___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Deferred vs. elevation

[Tony]

Makes sense.  I thought about the 'per user' scenario shortly after I sent
the email.

Thanks


On Tue, Dec 3, 2013 at 1:39 PM, Phil Wilson  wrote:

> Being picky, the elevated deferred custom actions in a per system install
> run with the system account. If you have code that needs to do something on
> behalf of the installing user (an example might be access/administer a
> database or go to the network or a user profile mapped drive) the system
> account can't do those things because it typically has no network or
> database privilege and can't see network drives that belong to a user, not
> the system. The installing user can have the rights to do these things. I'm
> not saying that doing these things is always a good idea, but people do
> need them sometimes.  Plus an impersonated custom action can be elevated if
> launched from an elevated process, and I suspect that some bundled installs
> such as SQL use that capability.
>
> Phil Wilson
>
>
> On Tue, Dec 3, 2013 at 7:37 AM, Tony  wrote:
>
> > Is there something in the logs that would indicate that an action is
> being
> > executed with/without this impersonate flag set?
> >
> > It is nice that we have the options, but why would I want Impersonate set
> > to 'yes'?  Isn't the whole point of deferred actions to run with system
> > privileges?
> >
> >
> > On Tue, Dec 3, 2013 at 8:20 AM, Tony  wrote:
> >
> > > Thanks.
> > >
> > >
> > > On Tue, Dec 3, 2013 at 8:03 AM, Blair Murri  wrote:
> > >
> > >> msidbCustomActionTypeNoImpersonate in the Type column of the
> > CustomAction
> > >> table.
> > >>
> > >> http://msdn.microsoft.com/library/aa368069.aspx
> > >>
> > >> -Blair
> > >>
> > >> > Date: Tue, 3 Dec 2013 07:43:08 -0500
> > >> > From: yellowjacketl...@gmail.com
> > >> > To: wix-users@lists.sourceforge.net
> > >> > 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?
> > >> > > >
> > >> > > >  .../>
> > >> > > >
> > >> > > >  Return="check"
> > >> > > > 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:
> >

Re: [WiX-users] Splash Screen

[wdh61]

Something odd is going on with the splash screen image processing.  A bmp
that is output from ImageMagik won't display either.  (Although it will if I
open it in Paint, save and then rebuild the installer) I'm trying to change
the product version number at build time in the splash screen image.



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

--
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=84349351&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Deferred vs. elevation

[Phil Wilson]

Being picky, the elevated deferred custom actions in a per system install
run with the system account. If you have code that needs to do something on
behalf of the installing user (an example might be access/administer a
database or go to the network or a user profile mapped drive) the system
account can't do those things because it typically has no network or
database privilege and can't see network drives that belong to a user, not
the system. The installing user can have the rights to do these things. I'm
not saying that doing these things is always a good idea, but people do
need them sometimes.  Plus an impersonated custom action can be elevated if
launched from an elevated process, and I suspect that some bundled installs
such as SQL use that capability.

Phil Wilson


On Tue, Dec 3, 2013 at 7:37 AM, Tony  wrote:

> Is there something in the logs that would indicate that an action is being
> executed with/without this impersonate flag set?
>
> It is nice that we have the options, but why would I want Impersonate set
> to 'yes'?  Isn't the whole point of deferred actions to run with system
> privileges?
>
>
> On Tue, Dec 3, 2013 at 8:20 AM, Tony  wrote:
>
> > Thanks.
> >
> >
> > On Tue, Dec 3, 2013 at 8:03 AM, Blair Murri  wrote:
> >
> >> msidbCustomActionTypeNoImpersonate in the Type column of the
> CustomAction
> >> table.
> >>
> >> http://msdn.microsoft.com/library/aa368069.aspx
> >>
> >> -Blair
> >>
> >> > Date: Tue, 3 Dec 2013 07:43:08 -0500
> >> > From: yellowjacketl...@gmail.com
> >> > To: wix-users@lists.sourceforge.net
> >> > 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

Re: [WiX-users] wixtoolset.org popups

[Keith.Douglas]

For what it is worth, I haven't seen them from over here either.


Keith Douglas
Statistics Canada | 170 Tunney's Pasture Driveway, Ottawa ON K1A 0T6
Statistique Canada | 170, promenade Tunney's Pasture, Ottawa ON K1A 0T6
keith.doug...@statcan.gc.ca
Telephone | Téléphone 613-951-4405
Facsimile | Télécopieur 613-951-1966
Government of Canada | Gouvernement du Canada 


-Original Message-
From: Christopher Painter [mailto:chr...@iswix.com] 
Sent: December-03-13 10:50 AM
To: General discussion about the WiX toolset.; General discussion about the WiX 
toolset.
Subject: Re: [WiX-users] wixtoolset.org popups

My coworker supsects the shared hoster was comprised (either hack or $$$) and 
that they were then injecting a script tag in the response.


 From: "Rob Mensching" 
Sent: Tuesday, December 03, 2013 9:41 AM
To: "General discussion about the WiX toolset." 

Subject: Re: [WiX-users] wixtoolset.org popups

There should be *no* ads coming from wixtoolset.org. I've not seen them. If 
someone captures a browser log showing where the ads are coming from I'd like 
to dig into it.

Note: If all goes well, the FireGiant team is moving wixtoolset.org to a new 
web hoster this month. Looking forward to that given all the challenges we've 
had with this hoster the last year.

-Original Message-
From: Blair Murri [mailto:os...@live.com]
Sent: Tuesday, December 3, 2013 7:17 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] wixtoolset.org popups

I saw them yesterday as well. I'm not seeing them this morning, though.

-Blair

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

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

[Smagin Alexander]

 Blair, thank you for slarification.
But when I start building DevBundle, GenerateWixInclude.exe and docfromxsd.exe 
have crashed. 

There are exceptions which generated during building. Do you know how to fix 
them?

Sorry for russian error messages, I can translate if it's necessary.

"d:\Install\Wix\DevBundle\build\debug\x86\GenerateWixInclude.exe" -nologo 
"custommsierrors.h" "d:\Install\Wix\DevBundle\build\d
ebug\inc\caerr.wxi"
Необработанное исключение: System.IO.FileLoadException: Невозможно загрузить 
файл или сборку "GenerateWixInclude, Version=3.0.0
.0, Culture=neutral, PublicKeyToken=36e4ce08b8ecfb17" или один из зависимых от 
них компонентов. Сбой при проверке правильности
строгого имени. (Исключение из HRESULT: 0x8013141A)
Имя файла: "GenerateWixInclude, Version=3.0.0.0, Culture=neutral, 
PublicKeyToken=36e4ce08b8ecfb17" ---> System.Security.Securit
yException: Сбой при проверке правильности строгого имени. (Исключение из 
HRESULT: 0x8013141A)
Ошибкой завершилась сборка со следующим параметром Zone:
MyComputer
"d:\Install\Wix\DevBundle\build\debug\x86\docfromxsd.exe" -out 
"d:\Install\Wix\DevBundle\build\obj\debug\x86\chm\documents\xsd"
"..\libs\dutil\xsd\thmutil.xsd" "..\tools\wix\Xsd\wix.xsd" 
"..\tools\wix\Xsd\wixloc.xsd" "..\ext\BalExtension\wixext\Xsd\bal.x
sd" "..\ext\ComPlusExtension\wixext\xsd\complus.xsd" 
"..\ext\DependencyExtension\wixext\Xsd\Dependency.xsd" "..\ext\DifxAppExte
nsion\wixext\Xsd\difxapp.xsd" 
"..\ext\FirewallExtension\wixext\Xsd\firewall.xsd" 
"..\ext\GamingExtension\wixext\Xsd\gaming.xsd"
"..\ext\IIsExtension\wixext\xsd\iis.xsd" 
"..\ext\MsmqExtension\wixext\xsd\msmq.xsd" 
"..\ext\NetFxExtension\wixext\Xsd\netfx.xs
d" "..\ext\PSExtension\wixext\xsd\ps.xsd" 
"..\ext\SqlExtension\wixext\Xsd\sql.xsd" 
"..\ext\TagExtension\wixext\Xsd\tag.xsd" "..
\ext\UtilExtension\wixext\Xsd\util.xsd" "..\ext\VSExtension\wixext\xsd\vs.xsd" 
"..\ext\lux\wixext\Xsd\lux.xsd"
Необработанное исключение: System.IO.FileLoadException: Невозможно загрузить 
файл или сборку "DocFromXsd, Version=3.0.0.0, Cult
ure=neutral, PublicKeyToken=36e4ce08b8ecfb17" или один из зависимых от них 
компонентов. Сбой при проверке правильности строгого
имени. (Исключение из HRESULT: 0x8013141A)
Имя файла: "DocFromXsd, Version=3.0.0.0, Culture=neutral, 
PublicKeyToken=36e4ce08b8ecfb17" ---> System.Security.SecurityExcepti
on: Сбой при проверке правильности строгого имени. (Исключение из HRESULT: 
0x8013141A)
Ошибкой завершилась сборка со следующим параметром Zone:
MyComputer  
Thanks,
Alex.

Вторник,  3 декабря 2013, 15:13 UTC от Blair Murri :
>You will need to first install .Net Framework 3.5, recent versions of Visual 
>Studio (2010 or newer), then build and install the DevBundle branch (you can 
>remove the DevBundle installer if you wish, all the components it installs are 
>marked "permanent"). If you install multiple versions of VS, it is recommended 
>to install them in chronological order (personal experience) with their latest 
>service packs.
>
>Build instructions are (more-or-less) described here (the prerequisites 
>described are most easily obtained by following my previous instructions):  
>http://wixtoolset.org/documentation/manual/v3/wixdev/building_wix.html
> 
>The biggest missing piece from the above documentation pages is that 
>tools\OneTimeWixBuildInitialization.proj must be built using MSBuild from an 
>elevated command prompt at least once on any given build/dev box before you 
>can build the rest of the toolset (otherwise you will get build errors 
>starting early on). Also, it is best to build the entire toolset from the root 
>of the sources (after having built that one project file elevated) before you 
>descend into sub directories to work/build individual portions. Running the 
>developer command prompts for Visual Studio usually isn't necessary, although 
>MSBuild isn't usually in the path. You'll need the v4 MSBuild, which you can 
>add your path yourself, use the developer command prompt, prepend the MSBuild 
>calls with the path to the tool, or create your own alias/batch file to call 
>the tool.
>
>-Blair
>
>From: Smagin Alexander
>Sent: ‎Tuesday‎, ‎December‎ ‎03‎, ‎2013 ‎6‎:‎31‎ ‎AM
>To: General discussion for Windows Installer XML toolset.
>
>Hi people,
>I want to compile wix from source code, but I didn't find any readme files 
>"how to comlipe wix".
>
>Could any one give suggestions which tools are used and where I can read anout 
>it?
>
>Thanks,
>Alex.
--
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=84349351&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-us

Re: [WiX-users] wixtoolset.org popups

[Christopher Painter]

My coworker supsects the shared hoster was comprised (either hack or $$$) and 
that they were then injecting a script tag in the response.


 From: "Rob Mensching" 
Sent: Tuesday, December 03, 2013 9:41 AM
To: "General discussion about the WiX toolset." 

Subject: Re: [WiX-users] wixtoolset.org popups

There should be *no* ads coming from wixtoolset.org. I've not seen them. If 
someone captures a browser log showing where the ads are coming from I'd like 
to dig into it.

Note: If all goes well, the FireGiant team is moving wixtoolset.org to a new 
web hoster this month. Looking forward to that given all the challenges we've 
had with this hoster the last year.

-Original Message-
From: Blair Murri [mailto:os...@live.com] 
Sent: Tuesday, December 3, 2013 7:17 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] wixtoolset.org popups

I saw them yesterday as well. I'm not seeing them this morning, though.

-Blair

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

Re: [WiX-users] Deferred vs. elevation

[Tony]

Is there something in the logs that would indicate that an action is being
executed with/without this impersonate flag set?

It is nice that we have the options, but why would I want Impersonate set
to 'yes'?  Isn't the whole point of deferred actions to run with system
privileges?


On Tue, Dec 3, 2013 at 8:20 AM, Tony  wrote:

> Thanks.
>
>
> On Tue, Dec 3, 2013 at 8:03 AM, Blair Murri  wrote:
>
>> msidbCustomActionTypeNoImpersonate in the Type column of the CustomAction
>> table.
>>
>> http://msdn.microsoft.com/library/aa368069.aspx
>>
>> -Blair
>>
>> > Date: Tue, 3 Dec 2013 07:43:08 -0500
>> > From: yellowjacketl...@gmail.com
>> > To: wix-users@lists.sourceforge.net
>> > 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=*

Re: [WiX-users] wixtoolset.org popups

[Rob Mensching]

There should be *no* ads coming from wixtoolset.org. I've not seen them. If 
someone captures a browser log showing where the ads are coming from I'd like 
to dig into it.

Note: If all goes well, the FireGiant team is moving wixtoolset.org to a new 
web hoster this month. Looking forward to that given all the challenges we've 
had with this hoster the last year.

-Original Message-
From: Blair Murri [mailto:os...@live.com] 
Sent: Tuesday, December 3, 2013 7:17 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] wixtoolset.org popups

I saw them yesterday as well. I’m not seeing them this morning, though.

-Blair

--
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=84349351&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] wixtoolset.org popups

[Blair Murri]

I saw them yesterday as well. I’m not seeing them this morning, though.






-Blair





From: Christopher Painter
Sent: ‎Tuesday‎, ‎December‎ ‎03‎, ‎2013 ‎6‎:‎28‎ ‎AM
To: General discussion for Windows Installer XML toolset., General discussion 
for Windows Installer XML toolset.







I don't see it in Chrome but I do see it in IE.   I see it on multiple 
computers including clean snapshotted VM's so I don't think I'm infected on 
my end. 

At this point I'm thinking either this is intentional or the site has been 
hacked.   


 From: "John Ludlow" 
Sent: Tuesday, December 03, 2013 8:17 AM
To: "General discussion about the WiX toolset." 

Subject: Re: [WiX-users] wixtoolset.org popups

I'm not seeing any adverts. On Chrome I do have AdBlockerPlus, but it
didn't report a blocked popup, and when I disabled it and refreshed I
didn't see anything.

Of course, it might be that you're hitting a different server than I am.

On 3 December 2013 13:44, Christopher Painter  wrote:

>
> Is anyone else getting popup advertisements on wixtoolset.org?
> Advertisements from "infinityads" are what I'm seeing.
>
>
> 

--
> 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=84349351&iu=/4140/ostg.clktrk


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

--
Rapidly troubleshoot problems before they affect your business. Most IT 
organizations don't have a clear picture of how application performance 
affects their revenue. With AppDynamics, you get 100% visibility into your 

Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics 
Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349351&iu=/4140/ostg.clktrk


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

--
Rapidly troubleshoot problems before they affect your business. Most IT 
organizations don't have a clear picture of how application performance 
affects their revenue. With AppDynamics, you get 100% visibility into your 
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349351&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
Rapidly troubleshoot problems before they affect your business. Most IT 
organizations don't have a clear picture of how application performance 
affects their revenue. With AppDynamics, you get 100% visibility into your 
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349351&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 compile build wix by myself

[Blair Murri]

You will need to first install .Net Framework 3.5, recent versions of Visual 
Studio (2010 or newer), then build and install the DevBundle branch (you can 
remove the DevBundle installer if you wish, all the components it installs are 
marked "permanent"). If you install multiple versions of VS, it is recommended 
to install them in chronological order (personal experience) with their latest 
service packs.

Build instructions are (more-or-less) described here (the prerequisites 
described are most easily obtained by following my previous instructions): 
http://wixtoolset.org/documentation/manual/v3/wixdev/building_wix.html
 
The biggest missing piece from the above documentation pages is that 
tools\OneTimeWixBuildInitialization.proj must be built using MSBuild from an 
elevated command prompt at least once on any given build/dev box before you can 
build the rest of the toolset (otherwise you will get build errors starting 
early on). Also, it is best to build the entire toolset from the root of the 
sources (after having built that one project file elevated) before you descend 
into sub directories to work/build individual portions. Running the developer 
command prompts for Visual Studio usually isn't necessary, although MSBuild 
isn't usually in the path. You'll need the v4 MSBuild, which you can add your 
path yourself, use the developer command prompt, prepend the MSBuild calls with 
the path to the tool, or create your own alias/batch file to call the tool.






-Blair





From: Smagin Alexander
Sent: ‎Tuesday‎, ‎December‎ ‎03‎, ‎2013 ‎6‎:‎31‎ ‎AM
To: General discussion for Windows Installer XML toolset.





Hi people,
I want to compile wix from source code, but I didn't find any readme files "how 
to comlipe wix".

Could any one give suggestions which tools are used and where I can read anout 
it?

Thanks,
Alex.

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

[WiX-users] How to compile build wix by myself

[Smagin Alexander]

 Hi people,
I want to compile wix from source code, but I didn't find any readme files "how 
to comlipe wix".

Could any one give suggestions which tools are used and where I can read anout 
it?

Thanks,
Alex.

--
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=84349351&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] wixtoolset.org popups

[Christopher Painter]

I don't see it in Chrome but I do see it in IE.   I see it on multiple 
computers including clean snapshotted VM's so I don't think I'm infected on 
my end. 

At this point I'm thinking either this is intentional or the site has been 
hacked.   


 From: "John Ludlow" 
Sent: Tuesday, December 03, 2013 8:17 AM
To: "General discussion about the WiX toolset." 

Subject: Re: [WiX-users] wixtoolset.org popups

I'm not seeing any adverts. On Chrome I do have AdBlockerPlus, but it
didn't report a blocked popup, and when I disabled it and refreshed I
didn't see anything.

Of course, it might be that you're hitting a different server than I am.

On 3 December 2013 13:44, Christopher Painter  wrote:

>
> Is anyone else getting popup advertisements on wixtoolset.org?
> Advertisements from "infinityads" are what I'm seeing.
>
>
> 

--
> 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=84349351&iu=/4140/ostg.clktrk


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

--
Rapidly troubleshoot problems before they affect your business. Most IT 
organizations don't have a clear picture of how application performance 
affects their revenue. With AppDynamics, you get 100% visibility into your 

Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics 
Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349351&iu=/4140/ostg.clktrk


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

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

[John Cooper]

I would use firstSequence too.  It has worked well for me in this scenario as I 
do harvest data from one of my config files on upgrade.  I have a table-driven 
custom action that does a bunch of XML reads on XPATHs and stores them into 
properties.

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




-Original Message-
From: Blair Murri [mailto:os...@live.com] 
Sent: Monday, December 2, 2013 10:53 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Help migrating Serial number during upgrade

Another way is to set the @Execute attribute of the CustomAction element to the 
value firstSequence. Then you don't need to condition it nor create additional 
source files.
 
> Date: Tue, 3 Dec 2013 13:43:22 +1100
> From: goodridge@gmail.com
> To: wix-users@lists.sourceforge.net
> Subject: Re: [WiX-users] Help migrating Serial number during upgrade
> 
> To have it in both but execute once, a yourself tool is an include 
> file in both sequences. You'll probably find there are other CA that 
> should just be executed the once e.g.
>  
> 
> Then in SharedExecuteActions.wxi place a CA that has the condition NOT 
> SECONDSEQUENCE so it is only executed once:
>
>   
>
> 
> warm regards
> 
> Rob Goodridge
> 
> 
> On Tue, Dec 3, 2013 at 6:22 AM, Hoover, Jacob 
> wrote:
> 
> > Since the serial number is "user data" I would expect it to 
> > persist after uninstall. If this is a per machine install I'd expect 
> > the file to live under CommonAppData in a Mfg/App sub folder. As 
> > such, the only need for a CA is to read this data on major upgrade 
> > (if you really think the installer should be the one prompting for a 
> > serial number).  To be honest, I'd go with the recommended approach 
> > of the installer only doing the installing, and the registration 
> > happening upon first run of the application.
> >
> > That being said, if you really need this inside your 
> > installer, I wouldn't move the license file but rather I'd have a CA 
> > for reading all the info out of the file. Schedule this CA early in 
> > your sequence (have it in both but schedule it to only run once) and 
> > have it populate Secure and Hidden properties that would then be used to 
> > populate your dialog in the UI.
> >
> > -Original Message-
> > From: tyler.w.r...@accenture.com [mailto:tyler.w.r...@accenture.com]
> > Sent: Monday, December 02, 2013 12:41 PM
> > To: wix-users@lists.sourceforge.net
> > Subject: [WiX-users] Help migrating Serial number during upgrade
> >
> > Hello,
> >
> > I have been tasked with creating a custom action that will 
> > migrate the user's serial number during a major upgrade. I have a 
> > custom action that runs before RemoveExisting that moves the license 
> > file, but my problem is that we have a custom dialog if ran in GUI 
> > mode that prompts for the serial. Since this runs before my custom action 
> > it shows up blank.
> >
> > My question is will I need to use two custom actions one in the UI 
> > sequence and another in the InstallExecute sequence or is there a 
> > way I can just use one custom action and solve both cases.
> >
> > 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
> >
> > 
> > -- 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=84349351&iu=/4140/ostg
> > .clktrk ___
> > WiX-users ma

Re: [WiX-users] Signing bundles - changes needed to each bundle wixproj

[John Cooper]

I have worked for three different software companies (including Microsoft).  
Everybody does it very differently.  Even within Microsoft, there were very 
significant differences between the way MSN did things and the way some of the 
other teams operated.

I would prefer a very secure approach, but managers make decisions based on 
their calculus of risk, and my input is just that--only input.

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



-Original Message-
From: Blair Murri [mailto:os...@live.com] 
Sent: Monday, December 2, 2013 10:48 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Signing bundles - changes needed to each bundle wixproj

At one time at MSFT (don't know if it is still the case) the machine that did 
codesigning for (most? all?) teams worldwide was solely located in (IIRC) 
Puerto Rico, and the files had to be securely electronically transported there, 
signed, and securely transported back, by a system owned by the group managing 
production signing (despite most build servers being in Redmond, Washington). 
Direct access to the signtool tool wasn't of any use in that case.
 
At my current client, there is no "official" signing in any build leg that 
developers have direct access to. You tell them where your files are and they 
sign them. They sign everything before the "packaging" step of the build, but 
they have to "script" signing things that are "contained" by other things built 
during packaging, like external cabs any everything we stick into a bundle.
 
Seems like everyone does it differently. Maybe we should take a poll to see if 
there is any one "majority" way that we could optimize for, but even inside of 
MSFT it had to be done differently for "production" signing and "internal 
only-test" signing.
 
-Blair
 
> Date: Mon, 2 Dec 2013 22:08:16 +
> From: john.ludlow...@gmail.com
> To: wix-users@lists.sourceforge.net
> Subject: Re: [WiX-users] Signing bundles - changes needed to each bundle  
> wixproj
> 
> Fair enough. I guess we have it set up quite simply - a cert in a 
> folder on the file server with restricted access. This is imported 
> into the certificate store on the build machine by the build and 
> selected by sha1 hash when calling signtool. We also timestamp.
> 
> Therefore simply providing a path to signtool, the sha1 and the 
> timestamping url via properties would work for us - that seems like a 
> sensible default which could be overridden
> 
> Thanks
> On 2 Dec 2013 18:24, "Rob Mensching"  wrote:
> 
> > My experience is that you really want your private key under lock and key.
> > I heard the room with the private key at MSFT had a hand print 
> > reader. Even the WiX toolset submits our binaries off to a signing 
> > service to get signed. Never saw two organizations implement signing 
> > the same way. 
> >
> > -Original Message-
> > From: John Ludlow [mailto:john.ludlow...@gmail.com]
> > Sent: Monday, December 2, 2013 10:09 AM
> > To: General discussion about the WiX toolset.
> > Subject: Re: [WiX-users] Signing bundles - changes needed to each 
> > bundle wixproj
> >
> > I suppose that's a good point, Rob - there's lots of ways to sign stuff.
> > We tend to go to the signtool method (actually a specific version of 
> > signtool for reasons I can't remember) and I kind of figured that 
> > would be the
> > (ahem) generically preferred method of signing things that WiX cares about.
> >
> > Anyway, thanks for your help.
> >
> >
> > On 2 December 2013 17:59, Rob Mensching  wrote:
> >
> > > Ditto.
> > >
> > > And if you come up with a way to set these targets by default 
> > > correctly for the multitude of ways for signing binaries, we'd 
> > > love to discuss it on wix-devs.
> > >
> > > -Original Message-
> > > From: Blair Murri [mailto:os...@live.com]
> > > Sent: Monday, December 2, 2013 9:53 AM
> > > To: General discussion for Windows Installer XML toolset.
> > > Subject: Re: [WiX-users] Signing bundles - changes needed to each 
> > > bundle wixproj
> > >
> > > I don't believe there's a preference to one over the other. Each 
> > > has its own costs and risks. Whichever works better in your environment.
> > > MSBuild is flexible in that regard. (What I do with my clients 
> > > tends to vary based on the client's needs and customs).
> > >
> > >
> > >
> > >
> > >
> > >
> > > -Blair
> > >
> > >
> > >
> > >
> > >
> > > From: John Ludlow
> > > Sent: Monday, December 02, 2013 9:49 AM
> > > To: General discussion for Windows Installer XML toolset.
> > >
> > >
> > >
> > >
> > >
> > > I see - that was the impression I got from the documentation, but 
> > > I tend to prefer to stay out of those because any changes to the 
> > > .wixprojs are relatively hidden, and we'd have to do the change 
> > > for each bundle .wixproj (and probably each MSI .wixproj). Given 
>

Re: [WiX-users] wixtoolset.org popups

[John Ludlow]

I'm not seeing any adverts. On Chrome I do have AdBlockerPlus, but it
didn't report a blocked popup, and when I disabled it and refreshed I
didn't see anything.

Of course, it might be that you're hitting a different server than I am.


On 3 December 2013 13:44, Christopher Painter  wrote:

>
> Is anyone else getting popup advertisements on wixtoolset.org?
> Advertisements from "infinityads" are what I'm seeing.
>
>
> --
> 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=84349351&iu=/4140/ostg.clktrk
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
--
Rapidly troubleshoot problems before they affect your business. Most IT 
organizations don't have a clear picture of how application performance 
affects their revenue. With AppDynamics, you get 100% visibility into your 
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349351&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 migrating Serial number during upgrade

[tyler.w.reid]

Thank you all for the wonderful answers. I will try them out and see which one 
we like better. On a side note I agree that this is user data and should be 
handled differently, but this is one of our older installs that was done prior 
to my arrival so we haven't done much with it because we are still working on 
converting everything to WIX atm.

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
--
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=84349351&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] wixtoolset.org popups

[Christopher Painter]

Is anyone else getting popup advertisements on wixtoolset.org?  
Advertisements from "infinityads" are what I'm seeing.
 
--
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=84349351&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Deferred vs. elevation

[Tony]

Thanks.


On Tue, Dec 3, 2013 at 8:03 AM, Blair Murri  wrote:

> msidbCustomActionTypeNoImpersonate in the Type column of the CustomAction
> table.
>
> http://msdn.microsoft.com/library/aa368069.aspx
>
> -Blair
>
> > Date: Tue, 3 Dec 2013 07:43:08 -0500
> > From: yellowjacketl...@gmail.com
> > To: wix-users@lists.sourceforge.net
> > 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\SomeUse

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] Deferred vs. elevation

[Blair Murri]

msidbCustomActionTypeNoImpersonate in the Type column of the CustomAction table.
 
http://msdn.microsoft.com/library/aa368069.aspx
 
-Blair
 
> Date: Tue, 3 Dec 2013 07:43:08 -0500
> From: yellowjacketl...@gmail.com
> To: wix-users@lists.sourceforge.net
> 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 -- Excep

Re: [WiX-users] Deferred vs. elevation

[Tony]

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

Re: [WiX-users] Signing bundles - changes needed to each bundle wixproj

[John Ludlow]

A poll might be a good idea - at least then we / you know what the
situation is. If it turns out there's no sensible default because everyone
*is* doing everything a different way, then it's sensible to not provide a
default. If it turns out that actually a lot of people do it a similar way
then maybe it's worth providing a default.

Or perhaps it's just worth improving the documentation because that
improves both cases without breaking anybody.

I'd be happy to submit a documentation update. (And yes, the codeproject
article I said I'd do on extensions is still sitting half-finished waiting
for me to find time for it). One thing I think might be helpful is if
there's a topic on signing (or perhaps two - one for bundles and one for
MSIs). At the moment the experience is that I google "sign wix bundle" and
get to the insignia page - which tells me not to use that.

One (or two) topic(s) that listed the 3 (I think?) options for signing
might be easier for people to get to grips with. I think the options are:

For signing a Bundle:
   1) Build the bundle, then use the following commands as a post build
step:
 insignia   -ib bundle.exe   -o engine.exe
 signtool  /a engine.exe  /sha1/t 
 insignia   -ab engine bundle.exe   -o bundle.exe
 signtool /a bundle.exe  /sha1/t 

   2) Use the CustomAfterWixTargets property to specify a .targets file
which contains the SignBundle and SignBundleEngine targets

   3) Add the SignBundle and SignBundleEngine targets into your .wixproj
(probably by adding an  reference in your .wixproj to a .targets
file)

For signing an MSI:
   1) Build the MSI with external cabs, sign the cabs, then use insignia to
inscribe the MSI with the signature the cabs use (only relevant for MSIs
which use external cabs, I think?)

   2) Use the CustomAfterWixTargets property to specify a .targets file
which contains the SignCabs and SignMsi targets

   3) Add the SignCabs and SignMsi targets into your .wixproj (probably by
adding an  reference in your .wixproj to a .targets file)

Does that seem right?

Also, I did notice something in the help source:

  

I haven't used external containers yet so this one is new to me. However,
if I was to update the documentation I should probably include  this as
well.

Thanks



On 3 December 2013 04:47, Blair Murri  wrote:

> At one time at MSFT (don't know if it is still the case) the machine that
> did codesigning for (most? all?) teams worldwide was solely located in
> (IIRC) Puerto Rico, and the files had to be securely electronically
> transported there, signed, and securely transported back, by a system owned
> by the group managing production signing (despite most build servers being
> in Redmond, Washington). Direct access to the signtool tool wasn't of any
> use in that case.
>
> At my current client, there is no "official" signing in any build leg that
> developers have direct access to. You tell them where your files are and
> they sign them. They sign everything before the "packaging" step of the
> build, but they have to "script" signing things that are "contained" by
> other things built during packaging, like external cabs any everything we
> stick into a bundle.
>
> Seems like everyone does it differently. Maybe we should take a poll to
> see if there is any one "majority" way that we could optimize for, but even
> inside of MSFT it had to be done differently for "production" signing and
> "internal only-test" signing.
>
> -Blair
>
> > Date: Mon, 2 Dec 2013 22:08:16 +
> > From: john.ludlow...@gmail.com
> > To: wix-users@lists.sourceforge.net
> > Subject: Re: [WiX-users] Signing bundles - changes needed to each bundle
>  wixproj
> >
> > Fair enough. I guess we have it set up quite simply - a cert in a folder
> on
> > the file server with restricted access. This is imported into the
> > certificate store on the build machine by the build and selected by sha1
> > hash when calling signtool. We also timestamp.
> >
> > Therefore simply providing a path to signtool, the sha1 and the
> > timestamping url via properties would work for us - that seems like a
> > sensible default which could be overridden
> >
> > Thanks
> > On 2 Dec 2013 18:24, "Rob Mensching"  wrote:
> >
> > > My experience is that you really want your private key under lock and
> key.
> > > I heard the room with the private key at MSFT had a hand print reader.
> Even
> > > the WiX toolset submits our binaries off to a signing service to get
> > > signed. Never saw two organizations implement signing the same way.
> 
> > >
> > > -Original Message-
> > > From: John Ludlow [mailto:john.ludlow...@gmail.com]
> > > Sent: Monday, December 2, 2013 10:09 AM
> > > To: General discussion about the WiX toolset.
> > > Subject: Re: [WiX-users] Signing bundles - changes needed to each
> bundle
> > > wixproj
> > >
> > > I suppose that's a good point, Rob - there's lots of ways to sign
> stuff.
> > > We tend to go to the signtool method (actual

Re: [WiX-users] [WIX]: How to add ListView control using themes

[Sergey Yukhno]

Use not  Hi All,
>
> How to add ListView control in themes file?
>
> I have create ListView control in HyperlinkTheme.xml
>
> 
>
>  "yes" TabStop="yes" ImageListGroupHeader="LVSIL_GROUPHEADER">
>
> Book1
>
> Book2
>
> 
>
>  "yes" FontId="0">Next
>
>   
>
> Is building correctly.
>
> When I ran the bootstrapper.exe it doesnot show any UI.
>
> I think its got corrupted?
>
>
>
> How to add ListView control using themes?
>
>
>
> Can anyone please help me on this?
>
>
> Thanks in advance...
> --
> 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=84349351&iu=/4140/ostg.clktrk
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users


--
Rapidly troubleshoot problems before they affect your business. Most IT 
organizations don't have a clear picture of how application performance 
affects their revenue. With AppDynamics, you get 100% visibility into your 
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349351&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users