Yes, MSIs declare the architecture they support. X86 MSIs can't write to x64
locations. MSIs that target Alpha (now long deprecated) can't install on x86 or
x64 or ia64 (also now deprecated?).
See the -arch cmd-line switch and Win64 attributes on various elements.
__
I know this isn't really specifically WiX related, but I also know you guys
know lots of MSI and installer stuff.
I'm seeing references to 32-bit MSIs vs. 64-bit MSIs.
Is there actually something inherently architecture-related about an MSI,
or is it just a matter of the 32/64 nature of the progr
Can we try using Appcmd.exe command to find the list of modules installed for
an application and then search "AppWarmup and DynamicCompression" in that
list using following command :
Eg : %windir%\system32\inetsrv\appcmd.exe list modules /app.name:"Default
Web Site"
--
View this message in cont
I an able to create registry entry using below :
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Not-to-create-key-under-HKCU-path-in-the-registry-tp7600703p7600741.html
Sent from the wix-users mailing list archiv
Patchwiz
-
Nir Bar
Freelance Developer
Mail: nir@panel-sw.com
Web: www.panel-sw.com
- C++ On Windows, Linux and Embedded Platforms
- WiX & InstallShield
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Patching-a-product-without
We would need the Burn log from %TEMP% to be able to diagnose this.
On Mon, Jun 29, 2015 at 3:49 AM, js69 wrote:
> In my Custom BA I noticed a weird change:
>
> In PlanPackageBegin:
>
>
>
> Debugging shows that myAction has the value "Cache". Seems to be an enum
> bug.
>
>
>
>
>
> --
> View this
In my Custom BA I noticed a weird change:
In PlanPackageBegin:
Debugging shows that myAction has the value "Cache". Seems to be an enum
bug.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Bug-in-3-10-0-1823-LaunchAction-Install-is-Cache-now-
7 matches
Mail list logo