wix-users — Mailing list for questions/discussion about the Windows Installer XML toolset.

Re: [WiX-users] Managed Bootstrapper: Engine.EvaluateCondition() requires separate thread?

[Farrukhw <far...@gm...>]

Later I figured out that the separate thread is active during event calls. So
I tried it during *DetectComplete *event and it worked. <br/> <br/> But
before that, I had to parse *BootstrapperApplicationData.xml* file to get
*WixBalCondition* elements and get the collection into an array e.g.
BalConditions[]. 

Here is my code snippet:

        void BootstrapperApplication_DetectComplete(object sender,
DetectCompleteEventArgs e)
                {
                    string balCondtionMessages = string.Empty;
                    bool balConditionStatus = true;
                    foreach (var balCondition in
bootAppData.BundleData.BalConditions)
                    {
                        if
(!model.BootstrapperApplication.Engine.EvaluateCondition(balCondition.Condition))
                        {
                            balConditionStatus = false;
                            if (!String.IsNullOrEmpty(balCondtionMessages))
                            {
                                balCondtionMessages = balCondtionMessages +
'\n' + "- " + balCondition.Message;
                            }
                            else
                                balCondtionMessages = "- " +
balCondition.Message;
                        }
        
                        
                    }
    
                    if (!balConditionStatus) 
                    {
                     SetbalConditionMsg(balCondtionMessages);
                    }    
     }

This makes us parse for all conditions in our Bundle.wxs code, evaluate them
and display the related message in our Custom Bootstrapper UI.

Farrukhw wrote
> Hi,
> In my Managed Bootstrapper, I tried to call
> Engine.EvaluateCondition("MY_PROG_FOUND"); in Run() method. But it never
> evaluates and said something like: "This requires a running thread." and
> it never evaluates.
> 
> I'm trying to evaluate Bundle conditions in my managed bootstrapper but
> still no luck. 
> 
> MY_PROG_FOUND is defined in Bundle code:
> <util:RegistrySearch  Id="PETRELINSTALLLOCATION" 
>         Variable="MY_PROG_FOUND"                      
>         Root="HKLM"
>         Key="SYSTEM\CurrentControlSet\Control\Session Manager\Environment"       
>         Value="$(var.my_prog_env_var)"
>         Result="exists"
>     />
>     
>     
> <bal:Condition Message="[WixBundleName] required the installation of My
> Program.">
>       

>     
> </bal:Condition>
> How can I use Engine.EvaluateCondition() in managed bootstrapper? Does
> this requires to be called in a specific event, like DetectBegin()??
> 
> Any help would be really appreciated...
> Thanks a bunch.





--
View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Managed-Bootstrapper-Engine-EvaluateCondition-requires-separate-thread-tp7600793p7600836.html
Sent from the wix-users mailing list archive at Nabble.com.

Re: [WiX-users] .NET Prerequisite, Burn, and the ARP

[Jiri T. <ka...@vo...>]

Hello,
I have the same issue. I double-checked that .NET package is marked as
permanent and I tried both with and without rollback boundary but I still
get ARP entry right after .NET is installed as prerequisite. I'm using Wix
3.9.

My Chain is defined this way:
<Chain>
  <PackageGroupRef Id="NetFx45Redist"/>
  <RollbackBoundary />
  <PackageGroupRef Id="TestPackage" />
</Chain>

The log from initial run is this:

[0690:0168][2015-07-08T00:29:07]i001: Burn v3.9.1006.0, Windows v6.1 (Build
7601: Service Pack 1), path:
C:\Users\Administrator\Desktop\TestInstaller.exe, cmdline: '-burn.unelevated
BurnPipe.{4303C9F0-DB96-41D1-A217-26466A0A9178}
{253C2727-CA99-43F7-B8B1-CF0835E221F0} 380 '
... snip ...
[0690:0168][2015-07-08T00:29:07]i000: Loading prerequisite bootstrapper
application because managed host could not be loaded, error: 0x80070490.
[0690:0464][2015-07-08T00:29:07]i000: Setting version variable
'WixBundleFileVersion' to value '1.0.0.0'
[0690:0168][2015-07-08T00:29:07]i100: Detect begin, 2 packages
[0690:0168][2015-07-08T00:29:07]i000: Registry key not found. Key =
'SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full'
[0690:0168][2015-07-08T00:29:07]i052: Condition 'PreviousInstallFolder'
evaluates to false.
[0690:0168][2015-07-08T00:29:07]i052: Condition 'NETFRAMEWORK45 >= 378389'
evaluates to false.
[0690:0168][2015-07-08T00:29:07]i101: Detected package: NetFx45Redist,
state: Absent, cached: None
[0690:0168][2015-07-08T00:29:07]i101: Detected package: TestPackage, state:
Absent, cached: None
[0690:0168][2015-07-08T00:29:07]i199: Detect complete, result: 0x0
[0690:0168][2015-07-08T00:29:09]i200: Plan begin, 2 packages, action:
Install
[0690:0168][2015-07-08T00:29:09]w321: Skipping dependency registration on
package with no dependency providers: NetFx45Redist
[0690:0168][2015-07-08T00:29:09]i000: Setting string variable
'NetFx45FullLog' to value
'C:\Users\ADMINI~1\AppData\Local\Temp\TestInstaller_20150708002907_0_NetFx45Redist.log'
[0690:0168][2015-07-08T00:29:09]i201: Planned package: NetFx45Redist, state:
Absent, default requested: Present, ba requested: Present, execute: Install,
rollback: None, cache: Yes, uncache: No, dependency: None
[0690:0168][2015-07-08T00:29:09]i201: Planned package: TestPackage, state:
Absent, default requested: Absent, ba requested: None, execute: None,
rollback: None, cache: No, uncache: No, dependency: None
[0690:0168][2015-07-08T00:29:09]i299: Plan complete, result: 0x0
[0690:0168][2015-07-08T00:29:09]i300: Apply begin
[017C:054C][2015-07-08T00:29:09]i360: Creating a system restore point.
[017C:054C][2015-07-08T00:29:09]i362: System restore disabled, system
restore point not created.
[017C:054C][2015-07-08T00:29:09]i000: Caching bundle from:
'C:\Users\ADMINI~1\AppData\Local\Temp\{380d557e-ec88-4923-9924-a37299972102}\.be\TestInstaller.exe'
to: 'C:\ProgramData\Package
Cache\{380d557e-ec88-4923-9924-a37299972102}\TestInstaller.exe'
[017C:054C][2015-07-08T00:29:09]i320: Registering bundle dependency
provider: {380d557e-ec88-4923-9924-a37299972102}, version: 1.0.0.0
[017C:0504][2015-07-08T00:29:09]i305: Verified acquired payload:
NetFx45Redist at path: C:\ProgramData\Package
Cache\.unverified\NetFx45Redist, moving to: C:\ProgramData\Package
Cache\CD57380514DC157DF75A09D3E54C96D1DF3DF51A\redist\dotnetfx45_full_x86_x64.exe.
[017C:054C][2015-07-08T00:29:09]i301: Applying execute package:
NetFx45Redist, action: Install, path: C:\ProgramData\Package
Cache\CD57380514DC157DF75A09D3E54C96D1DF3DF51A\redist\dotnetfx45_full_x86_x64.exe,
arguments: '"C:\ProgramData\Package
Cache\CD57380514DC157DF75A09D3E54C96D1DF3DF51A\redist\dotnetfx45_full_x86_x64.exe"
/q /norestart /ChainingPackage "Test Installer" /log
"C:\Users\ADMINI~1\AppData\Local\Temp\TestInstaller_20150708002907_0_NetFx45Redist.log.html"'
[0690:0168][2015-07-08T00:33:20]i319: Applied execute package:
NetFx45Redist, result: 0x0, restart: None
[0690:0168][2015-07-08T00:33:20]i399: Apply complete, result: 0x0, restart:
None, ba requested restart:  No
[0690:0168][2015-07-08T00:33:20]i500: Shutting down, exit code: 0x0
[0690:0168][2015-07-08T00:33:20]i000: The prerequisites were successfully
installed. The bootstrapper application will be reloaded.
[0690:0168][2015-07-08T00:33:20]i006: Bootstrapper application requested to
be reloaded.
[0690:0168][2015-07-08T00:33:20]i000: Loading managed bootstrapper
application.
[0690:0168][2015-07-08T00:33:20]i000: Creating BA thread to run
asynchronously.
[0690:060C][2015-07-08T00:33:20]i000: Starting Bootstrapper. Assembly
CodeBase:file:///C:/Users/Administrator/AppData/Local/Temp/{380d557e-ec88-4923-9924-a37299972102}/.ba1/TestInstaller.DLL
[0690:060C][2015-07-08T00:33:20]i000: Command Action: Install Resume: None
Restart: Prompt Display: Full LayoutDir:  Passthrough: False Relation: None
... snip ...
[0690:060C][2015-07-08T00:33:50]i000: Exiting UI.
[0690:0168][2015-07-08T00:33:50]i500: Shutting down, exit code: 0xffffffff
[0690:0168][2015-07-08T00:33:50]i000: Shutting down without restart.
... snip ...
[0690:0168][2015-07-08T00:33:50]i007: Exit code: 0xffffffff, restarting: No




--
View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/NET-Prerequisite-Burn-and-the-ARP-tp7600376p7600835.html
Sent from the wix-users mailing list archive at Nabble.com.

Re: [WiX-users] Burn, deploy and rollback Patches

[MelMelRob <Fl...@an...>]

Nir Bar wrote
> Is patch 1.0.1 Uninstallable?
> https://msdn.microsoft.com/en-us/library/aa372102%28v=vs.85%29.aspx

   PatchMetadata
            AllowRemoval="yes"
there is more info here <http://wixtoolset.org/issues/4779/>  





--
View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-deploy-and-rollback-Patches-tp7600471p7600834.html
Sent from the wix-users mailing list archive at Nabble.com.

Re: [WiX-users] How to get the WixBundleLog value of "LogPathVariable" attribute ?

[Farrukhw <far...@gm...>]

Using Engine.StringVariables[WixBundleVariable] e.g. in your case:
Engine.StringVariables["WixBundleLog"];





--
View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/How-to-get-the-WixBundleLog-value-of-LogPathVariable-attribute-tp7598738p7600833.html
Sent from the wix-users mailing list archive at Nabble.com.

Re: [WiX-users] Patch rollback works, but previous applied patch does not show in 'view installed updates' (after rollback)

[MelMelRob <Fl...@an...>]

kirannhegde wrote
> 1. What happens  when you apply the patches outside of Burn?
> 2. Also, how did you make sure that Patch 2 is in the view when you
> uninstalled Patch 3?
> 3. Do you have a verbose windows installer log file?

Hi Kirian
1. Applying the patches only workes fine.
2. I assumed burn would take care of this, but it does not.  more info here
<http://wixtoolset.org/issues/4779/>  
3.  link to demo project and logs here
<http://filenurse.com/download/20eae9b495f74c059b165b19b49e0e28.html>  



--
View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Patch-rollback-works-but-previous-applied-patch-does-not-show-in-view-installed-updates-after-rollba-tp7600642p7600832.html
Sent from the wix-users mailing list archive at Nabble.com.

Re: [WiX-users] QuickTime is installing when it is already installed.

[garymonk <ga...@gu...>]

Amazing that I could look at that so many times and not see that. Thanks you
for the help!!



--
View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/QuickTime-is-installing-when-it-is-already-installed-tp7600756p7600831.html
Sent from the wix-users mailing list archive at Nabble.com.

Re: [WiX-users] Problem durring major upgrade /qb or /qn

[Phil W. <phi...@gm...>]

My apologies, I'm going too fast and not looking properly - I need to
look again.
---------------
Phil Wilson


On Tue, Jul 7, 2015 at 12:40 PM, AleksL <ly...@gm...> wrote:
> Hello, Phil. Thank you for answer.
>
> But I don't clear understand.
>
> /Q log shows " Product registered: entering
> maintenance mode" and "Skipping FindRelatedProducts action: not run in
> maintenance mode" which means that the product defined by the Q log
> ProductCode must already be installed/
>
> I think that those Q log lines shows time moment in remove phase during
> major upgrade. In this time second product does not installed yet and first
> product is removing. Isn't it?
>
> I think the behavior shown in UI log seems to be right, in that case in
> quiet mode seems to be wrong.
> Is this my mistake or this is a bug in windows installer?
>
>
>
>
>
>
> --
> View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Problem-durring-major-upgrade-qb-or-qn-tp7600784p7600827.html
> Sent from the wix-users mailing list archive at Nabble.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...@li...
> https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Uninstall running very Slow....

[TimM <Tim...@sm...>]

Here is the download link to the uninstall logs:
https://www.dropbox.com/s/5qivuotwbornc8t/UninstallLogs.zip?dl=0




--
View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Uninstall-running-very-Slow-tp7600812p7600828.html
Sent from the wix-users mailing list archive at Nabble.com.

Re: [WiX-users] Problem durring major upgrade /qb or /qn

[AleksL <ly...@gm...>]

Hello, Phil. Thank you for answer. 

But I don't clear understand.

/Q log shows " Product registered: entering 
maintenance mode" and "Skipping FindRelatedProducts action: not run in 
maintenance mode" which means that the product defined by the Q log 
ProductCode must already be installed/

I think that those Q log lines shows time moment in remove phase during
major upgrade. In this time second product does not installed yet and first
product is removing. Isn't it?

I think the behavior shown in UI log seems to be right, in that case in
quiet mode seems to be wrong.
Is this my mistake or this is a bug in windows installer?






--
View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Problem-durring-major-upgrade-qb-or-qn-tp7600784p7600827.html
Sent from the wix-users mailing list archive at Nabble.com.

Re: [WiX-users] Uninstall running very Slow....

[TimM <Tim...@sm...>]

Nope the VM's are strictly captured snapshots and therefore no accumulative
changes are applied to the images.

Another thing to note is that we have our own uninstaller application that
simply launch the uninstalls of our products that are selected by the user
and the tester noticed that the slow down more often when doing an
administration push of the uninstall in silent mode.

If he pushes the uninstall in UI mode, or runs the same cmds on the local
machines then the uninstalls do seem to go faster, at least that is how he
sees it.

I do not know how running the uninstaller in silent mode and being pushed by
the admin would make much difference, that that is what he is seeing.

I'll see about posting logs of the same uninstall were one is fast and the
other slow to see if someone can see anything unusual.



--
View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Uninstall-running-very-Slow-tp7600812p7600826.html
Sent from the wix-users mailing list archive at Nabble.com.

Re: [WiX-users] Uninstall running very Slow....

[Phil W. <phi...@gm...>]

It may help to post the logs somewhere anyway, just in case someone
here can see something unusual.

IIRC, the VM may be one of those that does accumulative changes but
keeps the original image intact, so each action requires checking the
original image and then searching the list of changes to get the
correct current state, as well as keeping the change cache up to date
with that uninstall. So if the different timings were, for example,
not both a fresh VM, install then uninstall, the timings could be
inconsistent because of that kind of thing.

Otherwise yes, you're right. if there's no change that you can make to
the MSI to speed it up and it's all internal installer actions then
get it looked at by Microsoft.  As for detecting that the uninstall is
slow, surely the progress bar already shows that.

---------------
Phil Wilson


On Tue, Jul 7, 2015 at 7:14 AM, TimM <Tim...@sm...> wrote:
> Our testing department has been doing some install/uninstall testing with our
> products and have reported that sometimes the uninstall can be very slow at
> times and therefore wanted to know if we can fix these.I reviewed the logs
> and there were no indication of any tasks taking an overall long time to do,
> just consistently slow over all.I mentioned that there was not much that I
> could do as it was probably that their machines were busy during uninstall
> and therefore simply slowed down the uninstall. And I also mentioned that if
> the slow down was in any of our custom actions that we could at least look
> into them, but if any of the build in tasks were the cause of the slow down
> then there was not much we could do about these. They basically stated if
> there was any thing that we could do to detect this slow down and why as
> they did not accept my response that it could have just been a busy
> machine.So is there anything that I can do, or see in the log that would
> explain the slow down so that I could report back as to why the slow downs
> are taking place?I was given two logs of the same product being uninstalled
> on 2 different VM machines and one completed within 1 min where as the other
> completed after 45 mins.Again looking at the logs simply shows that each
> step of the uninstall was just taking longer to perform, ie for the
> FileRemove actions it took 22 seconds on the fast uninstall, where as on the
> slow uninstall it took 24 mins.So if someone could better explain why the
> uninstalls may be taking longer in some cases that I could then explain to
> the testing department then maybe they will know that it is not something
> that I can fix in the install project and therefore not report as a bug.
> Sure having installs/uninstalls taking way longer than expected is not a
> good user experience, but if there is nothing that I can actually do to fix
> it then what else am I suppose to do???Thanks for any input.
>
>
>
> --
> View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Uninstall-running-very-Slow-tp7600812.html
> Sent from the wix-users mailing list archive at Nabble.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...@li...
> https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Problem durring major upgrade /qb or /qn

[Phil W. <phi...@gm...>]

Ah, sorry, I just got them the wrong way around. The UI log shows a
normal install. The Q log shows " Product registered: entering
maintenance mode" and "Skipping FindRelatedProducts action: not run in
maintenance mode" which means that the product defined by the Q log
ProductCode must already be installed.
---------------
Phil Wilson


On Tue, Jul 7, 2015 at 1:54 AM, AleksL <ly...@gm...> wrote:
> I don't think so.
>
> I am testing on Virtual machine. First, I run test_setup_1, then do snapshot
> and do major update on test_setup_2 in quiet mode.
> After analyzing results I restore to the snapshot and do major update on
> test_setup_2 with UI.
>
> You wrote:
> /but then you run the UI
> install and that log says " Product registered: entering maintenance
> mode"/
>
> But this belongs to remove phase during major upgrade.
> You can see any lines before
> /MSI (s) (68:1C) [00:35:12:488]: Doing action: RemoveExistingProducts/
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> --
> View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Problem-durring-major-upgrade-qb-or-qn-tp7600784p7600808.html
> Sent from the wix-users mailing list archive at Nabble.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...@li...
> https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Create FTP site with Wix 3.9

[huntantr <ant...@sc...>]

I need to create an ftp site but can't seem to find any element or property
that supports this. Is there any way to do this through wix, or do I need to
create some custom actions? 

Thanks.



--
View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Create-FTP-site-with-Wix-3-9-tp7600820.html
Sent from the wix-users mailing list archive at Nabble.com.

Re: [WiX-users] Setting Compatibility Mode on shortcut for all users

[Hoover, J. <Jac...@gr...>]

You might need to deploy a shim db, though you'd have to define the specific compatibly settings you need.  

https://technet.microsoft.com/en-us/library/dd837647(v=ws.10).aspx

https://technet.microsoft.com/en-us/library/dd837648(WS.10).aspx


-----Original Message-----
From: Chris Moxon [mailto:chr...@eq...] 
Sent: Tuesday, July 07, 2015 8:41 AM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Setting Compatibility Mode on shortcut for all users

I just tried setting Windows 7 compatibility in the app manifest and removing the tick-box on the shortcut - but alas that makes our application fail.  It's using a third party ODBC driver that doesn't seem to work unless we have the tick-box selected on the short-cut.

-----Original Message-----
From: Hoover, Jacob [mailto:Jac...@gr...]
Sent: 06 July 2015 21:21
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Setting Compatibility Mode on shortcut for all users

Wouldn't the "right" way be to manifest the EXE declaring which version of Windows it is compatible with, and let the newer OS's decide if they need to shim the app?

-----Original Message-----
From: Phil Wilson [mailto:phi...@gm...]
Sent: Monday, July 06, 2015 3:11 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Setting Compatibility Mode on shortcut for all users

It might be "works as designed". Raymond Chen appears adamant that it shouldn't be done in an install anyway:

http://blogs.msdn.com/b/oldnewthing/archive/2010/03/11/9976571.aspx
---------------
Phil Wilson


On Mon, Jul 6, 2015 at 9:52 AM, Chris Moxon <chr...@eq...> wrote:
> I have a msi that has its InstallScope set to "perMachine" and it creates a shortcut which is available to all the users:
>
> <Directory Id="ProgramMenuFolder">
>
>    <Directory Id="CompanyShortcutsDir" Name="My Company" />
>
> </Directory>
>
>
> <Component Id="CMP_MainExeShortcut"
>
>            Directory="CompanyShortcutsDir"
>
>            Guid="{B857CD9E-XXXX-YYYY-F2090C50C985}">
>
>
>
>   <Shortcut Id="MyExeStartShortcut"
>
>             Name="My Product"
>
>             Description="$(var.WIX_PRODNAME)"
>
>             Target="[APPLICATIONFOLDER]MyApp.exe"
>
>             WorkingDirectory="APPLICATIONFOLDER"
>
>             Icon="my.ico" />
>
>
>
>   <RemoveFolder Id="RemoveCompanyShortcutsDir"
>
>                 On="uninstall" />
>
>
>
>   <RegistryValue Root="HKCU"
>
>                  Key="Software\MyCompany"
>
>                  Name="MainExeShortcut"
>
>                  Type="integer"
>
>                  Value="1"
>
>                  KeyPath="yes" />
>
> </Component>
>
>
>
> and the shortcut does indeed appear for all the users - so far so good !!
>
> But I also have this fragment of code:
>
>
>
>     <Component Id="CMP_MainExeShortcutCompat"
>
>           Directory="CompanyShortcutsDir"
>
>           Guid="{C748B7C6-XXXX-YYYY-7CB1823774DC}">
>
>
>
>
>
>   <RegistryValue Root="HKMU"
>
>          Key="SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers"
>
>          Name="[APPLICATIONFOLDER]MyApp.exe"
>
>          Type="string"
>
>          Value="~ WIN7RTM"
>
>          KeyPath="yes"/>
>
> </Component>
> who's purpose is to set the "Compatibility Mode" on the shortcut to be "Windows 7" - but this only happens for the user that installed our product, it doesn't get set on the shortcut for the other users who are likely to login to the PC.
> Does anyone know how I can set this flag on the shortcut for all the users ?
> Many Thanks,
> Chris.
>
>
> If you've received this email by mistake, we're sorry for bothering you. It may contain information that's confidential, so please delete it without sharing it. And if you let us know, we can try to stop it from happening again. Thank you.
>
> We may monitor any emails sent or received by us, or on our behalf. If we do, this will be in line with relevant law and our own policies.
>
> Eque2 Limited. Registered in England at Freetrade Exchange, 37 Peter Street, Manchester, M2 5GB. Registered number 08179642.
> ----------------------------------------------------------------------
> -------- 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...@li...
> 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...@li...
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...@li...
https://lists.sourceforge.net/lists/listinfo/wix-users


If you've received this email by mistake, we're sorry for bothering you. It may contain information that's confidential, so please delete it without sharing it. And if you let us know, we can try to stop it from happening again. Thank you.

We may monitor any emails sent or received by us, or on our behalf. If we do, this will be in line with relevant law and our own policies.

Eque2 Limited. Registered in England at Freetrade Exchange, 37 Peter Street, Manchester, M2 5GB. Registered number 08179642.

------------------------------------------------------------------------------
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...@li...
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Setting Compatibility Mode on shortcut for all users

[Wheeler, B. (DSHS/DCS) <BWh...@ds...>]

Although making the appropriate shortcut during installation is the best answer normally - If it isn't working this way could you create the per user shortcut a different way after installation completes.  Maybe Active Directory policy or power shell during logon or ????

-----Original Message-----
From: Chris Moxon [mailto:chr...@eq...] 
Sent: Tuesday, July 07, 2015 6:49 AM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Setting Compatibility Mode on shortcut for all users

Well perhaps Raymond Chen lives in a different world to the one I do.  Yes in an ideal world, we would fix our app so that it doesn't need the compatibility tick-box checked - but the problem with our app is that it uses a third party ODBC driver that is not compatible - we cannot change that part of our product ( & the third party in question aren't bothered about changing it either ) so we cannot fix our app.  Setting the tick-box on the shortcut for the current user is a quick, easy ( & cost effective ) solution to our needs - we just need to try and get it set for all users.

-----Original Message-----
From: Phil Wilson [mailto:phi...@gm...]
Sent: 06 July 2015 21:11
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Setting Compatibility Mode on shortcut for all users

It might be "works as designed". Raymond Chen appears adamant that it shouldn't be done in an install anyway:

http://blogs.msdn.com/b/oldnewthing/archive/2010/03/11/9976571.aspx
---------------
Phil Wilson


On Mon, Jul 6, 2015 at 9:52 AM, Chris Moxon <chr...@eq...> wrote:
> I have a msi that has its InstallScope set to "perMachine" and it creates a shortcut which is available to all the users:
>
> <Directory Id="ProgramMenuFolder">
>
>    <Directory Id="CompanyShortcutsDir" Name="My Company" />
>
> </Directory>
>
>
> <Component Id="CMP_MainExeShortcut"
>
>            Directory="CompanyShortcutsDir"
>
>            Guid="{B857CD9E-XXXX-YYYY-F2090C50C985}">
>
>
>
>   <Shortcut Id="MyExeStartShortcut"
>
>             Name="My Product"
>
>             Description="$(var.WIX_PRODNAME)"
>
>             Target="[APPLICATIONFOLDER]MyApp.exe"
>
>             WorkingDirectory="APPLICATIONFOLDER"
>
>             Icon="my.ico" />
>
>
>
>   <RemoveFolder Id="RemoveCompanyShortcutsDir"
>
>                 On="uninstall" />
>
>
>
>   <RegistryValue Root="HKCU"
>
>                  Key="Software\MyCompany"
>
>                  Name="MainExeShortcut"
>
>                  Type="integer"
>
>                  Value="1"
>
>                  KeyPath="yes" />
>
> </Component>
>
>
>
> and the shortcut does indeed appear for all the users - so far so good !!
>
> But I also have this fragment of code:
>
>
>
>     <Component Id="CMP_MainExeShortcutCompat"
>
>           Directory="CompanyShortcutsDir"
>
>           Guid="{C748B7C6-XXXX-YYYY-7CB1823774DC}">
>
>
>
>
>
>   <RegistryValue Root="HKMU"
>
>          Key="SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers"
>
>          Name="[APPLICATIONFOLDER]MyApp.exe"
>
>          Type="string"
>
>          Value="~ WIN7RTM"
>
>          KeyPath="yes"/>
>
> </Component>
> who's purpose is to set the "Compatibility Mode" on the shortcut to be "Windows 7" - but this only happens for the user that installed our product, it doesn't get set on the shortcut for the other users who are likely to login to the PC.
> Does anyone know how I can set this flag on the shortcut for all the users ?
> Many Thanks,
> Chris.
>
>
> If you've received this email by mistake, we're sorry for bothering you. It may contain information that's confidential, so please delete it without sharing it. And if you let us know, we can try to stop it from happening again. Thank you.
>
> We may monitor any emails sent or received by us, or on our behalf. If we do, this will be in line with relevant law and our own policies.
>
> Eque2 Limited. Registered in England at Freetrade Exchange, 37 Peter Street, Manchester, M2 5GB. Registered number 08179642.
> ----------------------------------------------------------------------
> -------- 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...@li...
> 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...@li...
https://lists.sourceforge.net/lists/listinfo/wix-users


If you've received this email by mistake, we're sorry for bothering you. It may contain information that's confidential, so please delete it without sharing it. And if you let us know, we can try to stop it from happening again. Thank you.

We may monitor any emails sent or received by us, or on our behalf. If we do, this will be in line with relevant law and our own policies.

Eque2 Limited. Registered in England at Freetrade Exchange, 37 Peter Street, Manchester, M2 5GB. Registered number 08179642.

------------------------------------------------------------------------------
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...@li...
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] product dependencies - with or without the Dependency Extension

[Reuss, M. <mat...@si...>]

Hello,

is there any documentation available on authoring and handling product dependencies? So far (3.9R2), the "How To: Author product dependencies" in the WiX help file is sill empty.
I have learnt that Burn can now handle dependencies without using the Dependency Extension, but I assume that there are more use cases for that extension (as the Provides Element can also be the child of a Component...) The lack of documentation makes this dependency feature somewhat confusing...

Is the registry key HKCR\Installer\Dependencies a WiX "invention", or is it used by Windows Installer as well?

Best regards

Matthias Reuss

[WiX-users] Uninstall running very Slow....

[TimM <Tim...@sm...>]

Our testing department has been doing some install/uninstall testing with our
products and have reported that sometimes the uninstall can be very slow at
times and therefore wanted to know if we can fix these.I reviewed the logs
and there were no indication of any tasks taking an overall long time to do,
just consistently slow over all.I mentioned that there was not much that I
could do as it was probably that their machines were busy during uninstall
and therefore simply slowed down the uninstall. And I also mentioned that if
the slow down was in any of our custom actions that we could at least look
into them, but if any of the build in tasks were the cause of the slow down
then there was not much we could do about these. They basically stated if
there was any thing that we could do to detect this slow down and why as
they did not accept my response that it could have just been a busy
machine.So is there anything that I can do, or see in the log that would
explain the slow down so that I could report back as to why the slow downs
are taking place?I was given two logs of the same product being uninstalled
on 2 different VM machines and one completed within 1 min where as the other
completed after 45 mins.Again looking at the logs simply shows that each
step of the uninstall was just taking longer to perform, ie for the
FileRemove actions it took 22 seconds on the fast uninstall, where as on the
slow uninstall it took 24 mins.So if someone could better explain why the
uninstalls may be taking longer in some cases that I could then explain to
the testing department then maybe they will know that it is not something
that I can fix in the install project and therefore not report as a bug.
Sure having installs/uninstalls taking way longer than expected is not a
good user experience, but if there is nothing that I can actually do to fix
it then what else am I suppose to do???Thanks for any input. 



--
View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Uninstall-running-very-Slow-tp7600812.html
Sent from the wix-users mailing list archive at Nabble.com.

Re: [WiX-users] Setting Compatibility Mode on shortcut for all users

[Chris M. <chr...@eq...>]

Well perhaps Raymond Chen lives in a different world to the one I do.  Yes in an ideal world, we would fix our app so that it doesn't need the compatibility tick-box checked - but the problem with our app is that it uses a third party ODBC driver that is not compatible - we cannot change that part of our product ( & the third party in question aren't bothered about changing it either ) so we cannot fix our app.  Setting the tick-box on the shortcut for the current user is a quick, easy ( & cost effective ) solution to our needs - we just need to try and get it set for all users.

-----Original Message-----
From: Phil Wilson [mailto:phi...@gm...]
Sent: 06 July 2015 21:11
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Setting Compatibility Mode on shortcut for all users

It might be "works as designed". Raymond Chen appears adamant that it shouldn't be done in an install anyway:

http://blogs.msdn.com/b/oldnewthing/archive/2010/03/11/9976571.aspx
---------------
Phil Wilson


On Mon, Jul 6, 2015 at 9:52 AM, Chris Moxon <chr...@eq...> wrote:
> I have a msi that has its InstallScope set to "perMachine" and it creates a shortcut which is available to all the users:
>
> <Directory Id="ProgramMenuFolder">
>
>    <Directory Id="CompanyShortcutsDir" Name="My Company" />
>
> </Directory>
>
>
> <Component Id="CMP_MainExeShortcut"
>
>            Directory="CompanyShortcutsDir"
>
>            Guid="{B857CD9E-XXXX-YYYY-F2090C50C985}">
>
>
>
>   <Shortcut Id="MyExeStartShortcut"
>
>             Name="My Product"
>
>             Description="$(var.WIX_PRODNAME)"
>
>             Target="[APPLICATIONFOLDER]MyApp.exe"
>
>             WorkingDirectory="APPLICATIONFOLDER"
>
>             Icon="my.ico" />
>
>
>
>   <RemoveFolder Id="RemoveCompanyShortcutsDir"
>
>                 On="uninstall" />
>
>
>
>   <RegistryValue Root="HKCU"
>
>                  Key="Software\MyCompany"
>
>                  Name="MainExeShortcut"
>
>                  Type="integer"
>
>                  Value="1"
>
>                  KeyPath="yes" />
>
> </Component>
>
>
>
> and the shortcut does indeed appear for all the users - so far so good !!
>
> But I also have this fragment of code:
>
>
>
>     <Component Id="CMP_MainExeShortcutCompat"
>
>           Directory="CompanyShortcutsDir"
>
>           Guid="{C748B7C6-XXXX-YYYY-7CB1823774DC}">
>
>
>
>
>
>   <RegistryValue Root="HKMU"
>
>          Key="SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers"
>
>          Name="[APPLICATIONFOLDER]MyApp.exe"
>
>          Type="string"
>
>          Value="~ WIN7RTM"
>
>          KeyPath="yes"/>
>
> </Component>
> who's purpose is to set the "Compatibility Mode" on the shortcut to be "Windows 7" - but this only happens for the user that installed our product, it doesn't get set on the shortcut for the other users who are likely to login to the PC.
> Does anyone know how I can set this flag on the shortcut for all the users ?
> Many Thanks,
> Chris.
>
>
> If you've received this email by mistake, we're sorry for bothering you. It may contain information that's confidential, so please delete it without sharing it. And if you let us know, we can try to stop it from happening again. Thank you.
>
> We may monitor any emails sent or received by us, or on our behalf. If we do, this will be in line with relevant law and our own policies.
>
> Eque2 Limited. Registered in England at Freetrade Exchange, 37 Peter Street, Manchester, M2 5GB. Registered number 08179642.
> ----------------------------------------------------------------------
> -------- 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...@li...
> 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...@li...
https://lists.sourceforge.net/lists/listinfo/wix-users


If you've received this email by mistake, we're sorry for bothering you. It may contain information that's confidential, so please delete it without sharing it. And if you let us know, we can try to stop it from happening again. Thank you.

We may monitor any emails sent or received by us, or on our behalf. If we do, this will be in line with relevant law and our own policies.

Eque2 Limited. Registered in England at Freetrade Exchange, 37 Peter Street, Manchester, M2 5GB. Registered number 08179642.

Re: [WiX-users] Setting Compatibility Mode on shortcut for all users

[Chris M. <chr...@eq...>]

I just tried setting Windows 7 compatibility in the app manifest and removing the tick-box on the shortcut - but alas that makes our application fail.  It's using a third party ODBC driver that doesn't seem to work unless we have the tick-box selected on the short-cut.

-----Original Message-----
From: Hoover, Jacob [mailto:Jac...@gr...]
Sent: 06 July 2015 21:21
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Setting Compatibility Mode on shortcut for all users

Wouldn't the "right" way be to manifest the EXE declaring which version of Windows it is compatible with, and let the newer OS's decide if they need to shim the app?

-----Original Message-----
From: Phil Wilson [mailto:phi...@gm...]
Sent: Monday, July 06, 2015 3:11 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Setting Compatibility Mode on shortcut for all users

It might be "works as designed". Raymond Chen appears adamant that it shouldn't be done in an install anyway:

http://blogs.msdn.com/b/oldnewthing/archive/2010/03/11/9976571.aspx
---------------
Phil Wilson


On Mon, Jul 6, 2015 at 9:52 AM, Chris Moxon <chr...@eq...> wrote:
> I have a msi that has its InstallScope set to "perMachine" and it creates a shortcut which is available to all the users:
>
> <Directory Id="ProgramMenuFolder">
>
>    <Directory Id="CompanyShortcutsDir" Name="My Company" />
>
> </Directory>
>
>
> <Component Id="CMP_MainExeShortcut"
>
>            Directory="CompanyShortcutsDir"
>
>            Guid="{B857CD9E-XXXX-YYYY-F2090C50C985}">
>
>
>
>   <Shortcut Id="MyExeStartShortcut"
>
>             Name="My Product"
>
>             Description="$(var.WIX_PRODNAME)"
>
>             Target="[APPLICATIONFOLDER]MyApp.exe"
>
>             WorkingDirectory="APPLICATIONFOLDER"
>
>             Icon="my.ico" />
>
>
>
>   <RemoveFolder Id="RemoveCompanyShortcutsDir"
>
>                 On="uninstall" />
>
>
>
>   <RegistryValue Root="HKCU"
>
>                  Key="Software\MyCompany"
>
>                  Name="MainExeShortcut"
>
>                  Type="integer"
>
>                  Value="1"
>
>                  KeyPath="yes" />
>
> </Component>
>
>
>
> and the shortcut does indeed appear for all the users - so far so good !!
>
> But I also have this fragment of code:
>
>
>
>     <Component Id="CMP_MainExeShortcutCompat"
>
>           Directory="CompanyShortcutsDir"
>
>           Guid="{C748B7C6-XXXX-YYYY-7CB1823774DC}">
>
>
>
>
>
>   <RegistryValue Root="HKMU"
>
>          Key="SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers"
>
>          Name="[APPLICATIONFOLDER]MyApp.exe"
>
>          Type="string"
>
>          Value="~ WIN7RTM"
>
>          KeyPath="yes"/>
>
> </Component>
> who's purpose is to set the "Compatibility Mode" on the shortcut to be "Windows 7" - but this only happens for the user that installed our product, it doesn't get set on the shortcut for the other users who are likely to login to the PC.
> Does anyone know how I can set this flag on the shortcut for all the users ?
> Many Thanks,
> Chris.
>
>
> If you've received this email by mistake, we're sorry for bothering you. It may contain information that's confidential, so please delete it without sharing it. And if you let us know, we can try to stop it from happening again. Thank you.
>
> We may monitor any emails sent or received by us, or on our behalf. If we do, this will be in line with relevant law and our own policies.
>
> Eque2 Limited. Registered in England at Freetrade Exchange, 37 Peter Street, Manchester, M2 5GB. Registered number 08179642.
> ----------------------------------------------------------------------
> -------- 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...@li...
> 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...@li...
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...@li...
https://lists.sourceforge.net/lists/listinfo/wix-users


If you've received this email by mistake, we're sorry for bothering you. It may contain information that's confidential, so please delete it without sharing it. And if you let us know, we can try to stop it from happening again. Thank you.

We may monitor any emails sent or received by us, or on our behalf. If we do, this will be in line with relevant law and our own policies.

Eque2 Limited. Registered in England at Freetrade Exchange, 37 Peter Street, Manchester, M2 5GB. Registered number 08179642.

[WiX-users] unsubscribe

[Cedric L. <Ced...@as...>]

Re: [WiX-users] Patch rollback works, but previous applied patch does not show in 'view installed updates' (after rollback)

[kirannhegde <kir...@gm...>]

Hello,

What happens  when you apply the patches outside of Burn?
Also, how did you make sure that Patch 2 is in the view when you uninstalled
Patch 3?

Do you have a verbose windows installer log file?

Regards,
Kiran Hegde



--
View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Patch-rollback-works-but-previous-applied-patch-does-not-show-in-view-installed-updates-after-rollba-tp7600642p7600809.html
Sent from the wix-users mailing list archive at Nabble.com.

Re: [WiX-users] Problem durring major upgrade /qb or /qn

[AleksL <ly...@gm...>]

I don't think so.

I am testing on Virtual machine. First, I run test_setup_1, then do snapshot
and do major update on test_setup_2 in quiet mode.
After analyzing results I restore to the snapshot and do major update on
test_setup_2 with UI.

You wrote: 
/but then you run the UI 
install and that log says " Product registered: entering maintenance 
mode"/

But this belongs to remove phase during major upgrade.
You can see any lines before 
/MSI (s) (68:1C) [00:35:12:488]: Doing action: RemoveExistingProducts/






















--
View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Problem-durring-major-upgrade-qb-or-qn-tp7600784p7600808.html
Sent from the wix-users mailing list archive at Nabble.com.

Re: [WiX-users] how to add code signing to build script

[David B. <dav...@nt...>]

Thanks very much, Jacob - it’s working!

In case it helps anyone else: it works to use kSignCMD.exe (free download from K Software) in place of the 2 calls to signtool.


> On Jul 6, 2015, at 4:13 PM, Hoover, Jacob <Jac...@gr...> wrote:
> 
> The error you are getting is: FDIERROR_NOT_A_CABINET
> 
> (This would go after your last call to light.)
> 
> http://neilsleightholm.blogspot.com/2012/05/wix-burn-tipstricks.html
> 
> Signing a package
> 
> insignia -ib Setup.exe -o engine.exe
> signtool engine.exe (extra parameters excluded for simplicity)
> insignia -ab engine.exe Setup.exe -o Setup.exe
> signtool Setup.exe
> 
> Though it's easier to use a wixproj and the MSBuild tasks, and then just override the targets.
> 
> -----Original Message-----
> From: David Burson [mailto:dav...@nt...] 
> Sent: Monday, July 06, 2015 1:01 PM
> To: General discussion about the WiX toolset.
> Subject: [WiX-users] how to add code signing to build script
> 
> Hi,
> 
> I’m brand new to code signing.  Just got my certificate through K Software, a Comodo reseller.  I tried adding a call to kSignCMD.exe at the end of my build script, and it appears to work:  the properties for my installer show my certificate, and the UAC prompt when I install also shows me as the publisher.
> 
> However, the installer fails.  The start of the log looks fine as far as I can see, but here’s how the log ends:
> 
> Apply begin
> Creating a system restore point.
> Created a system restore point.
> Caching bundle from: 'C:\Users\david\AppData\Local\Temp\{e3cdbd3a-6ab1-4f6c-94b2-4f005172e581}\.be\MapCreatorSetup-x64-1.1.3.exe' to: 'C:\ProgramData\Package Cache\{e3cdbd3a-6ab1-4f6c-94b2-4f005172e581}\MapCreatorSetup-x64-1.1.3.exe'
> Registering bundle dependency provider: {e3cdbd3a-6ab1-4f6c-94b2-4f005172e581}, version: 1.1.3.0 Acquiring container: WixAttachedContainer, copy from: C:\mc\MapCreatorSetup-x64-1.1.3.exe
> Setting string variable 'WixBundleLastUsedSource' to value 'C:\mc\'
> Error 0x80070001: Failed to extract all files from container, erf: 1:2:0 Error 0x80070001: Failed to wait for operation complete.
> Error 0x80070001: Failed to open container.
> Error 0x80070001: Failed to open container: WixAttachedContainer.
> Failed to extract payloads from container: WixAttachedContainer to working path: C:\Users\david\AppData\Local\Temp\{e3cdbd3a-6ab1-4f6c-94b2-4f005172e581}\F0BE7EF5275BEDA1781A0DC8690CC9EBB929A6A8, error: 0x80070001.
> Error 0x80070001: Failed while caching, aborting execution.
> Removed bundle dependency provider: {e3cdbd3a-6ab1-4f6c-94b2-4f005172e581}
> Removing cached bundle: {e3cdbd3a-6ab1-4f6c-94b2-4f005172e581}, from path: C:\ProgramData\Package Cache\{e3cdbd3a-6ab1-4f6c-94b2-4f005172e581}\
> Apply complete, result: 0x80070001, restart: None, ba requested restart:  No
> 
> I’ve examined this Insignia documentation:  http://wixtoolset.org/documentation/manual/v3/overview/insignia.html but I don’t really understand what I’m supposed to do to get code signing to be part of my build script.  Here are what I assume is the pertinent information about my build script:
> 
> After my build script builds all the components and produces an .exe, it calls candle.exe on about a dozen .wxs files, representing various components such as localization, help file, license, and finally the actual product.
> 
> Next, it calls light.exe with the .wixobj’s produced in the previous steps, to create an msi.
> 
> Then it calls candle.exe on my bundle.wxs.
> 
> Finally, it calls light.exe on the bundle.wixobj.
> 
> Where in these steps should I insert call(s) to sign my code, and what should those calls look like?  Also, is there any command I can add to the script that will output whether code signing worked?
> 
> Thanks,
> David
> 
> ------------------------------------------------------------------------------
> 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...@li...
> 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...@li...
> https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Problem durring major upgrade /qb or /qn

[Phil W. <phi...@gm...>]

There  appears to be something wrong with your test methodology. The
quiet log shows a run that finds an upgrade, but then you run the UI
install and that log says " Product registered: entering maintenance
mode" and "Skipping FindRelatedProducts action: not run in maintenance
mode", and "Skipping RemoveExistingProducts action: current
configuration is maintenance mode or an uninstall" so you seem to be
running the UI install with a ProductCode that is already installed on
the system.

Re: [WiX-users] QuickTime is installing when it is already installed.

[Hoover, J. <Jac...@gr...>]

Just a guess but...



<util:RegistrySearch Root="HKLM"
Key="SOFTWARE\Clients\Media\QuickTime" Result="exists"
Variable="QuickTimeFound64" Win64="yes" />
        <util:RegistrySearch Root="HKLM"
Key="SOFTWARE\Clients\Media\QuickTime" Result="exists"
Variable="QuickTimeFound32" Win64="no" />


-----Original Message-----
From: garymonk [mailto:ga...@gu...] 
Sent: Monday, July 06, 2015 1:20 PM
To: wix...@li...
Subject: Re: [WiX-users] QuickTime is installing when it is already installed.

I cannot get this to work correctly. Here is the log...

[08B4:040C][2015-07-06T10:50:14]i000: Registry key not found. Key = 'HKEY_LOCAL_MACHINE\SOFTWARE\Clients\Media\QuickTime'
[08B4:040C][2015-07-06T10:50:14]i000: Setting numeric variable 'QuickTimeFound64' to value 0
[08B4:040C][2015-07-06T10:50:14]i000: Registry key not found. Key = 'HKEY_LOCAL_MACHINE\SOFTWARE\Clients\Media\QuickTime'

My registry...

<http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/file/n7600799/Capture.png> 

My code...

<util:RegistrySearch Root="HKLM"
Key="HKEY_LOCAL_MACHINE\SOFTWARE\Clients\Media\QuickTime" Result="exists"
Variable="QuickTimeFound64" Win64="yes" />
        <util:RegistrySearch Root="HKLM"
Key="HKEY_LOCAL_MACHINE\SOFTWARE\Clients\Media\QuickTime" Result="exists"
Variable="QuickTimeFound32" Win64="no" />
        
        <Chain>
            <PackageGroupRef Id="PackageGroup_NetFx35Redist"/>
            <PackageGroupRef Id="PackageGroup_NetFx40Redist"/>
            <PackageGroupRef Id="PackageGroup_SQLServer2012"/>

            <ExePackage Id="Package_QuickTime" Cache="no"
Compressed="$(var.Compressed)"
                          Description="Apple QuickTime 7"
DownloadUrl="$(var.GuruDownloadRepo)/{2}"
                         
SourceFile="..\Prerequisites\QuickTimeInstaller.exe"
                          Name="Prerequisites\QuickTimeInstaller.exe"
                          Permanent="yes" DisplayName="Apple QuickTime 7"
                          DetectCondition="QuickTimeFound64 AND QuickTimeFound32" />

The way I think this should work is that QuickTime32 is false and
QuickTime64 should be true, but as you can see from the log it still comes back as false.

I have tried including "Wow6432Node" in the 64bit path but it didn't make any difference.

I would appreciate any help!! 



--
View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/QuickTime-is-installing-when-it-is-already-installed-tp7600756p7600799.html
Sent from the wix-users mailing list archive at Nabble.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...@li...
https://lists.sourceforge.net/lists/listinfo/wix-users