Comments (6)
Thanks. We need a verbose log, however: https://support.firegiant.com/hc/en-us/articles/230912407-Create-a-log-file-
from issues.
WiX v3.14 works like WiX v4 to support architecture-specific custom actions: If you have 64-bit components, you need to build the package with the right architecture.
from issues.
Please provide a repo with a minimal repro project and attach to this issue a verbose log showing the problem.
from issues.
Here is a package to reproduce.
Just launch the buildWIX314.bat with wix 3.14 installed. in Common.bat, you can change the path to use it with the 3.11.
It will install in %programfiles%\SetupWix314 a readme.txt
and in %programdata%\SetupWix314\ the subfolders Temp and LocalProjects should have full access to the group Users
And here is the log of the msi install :
MSIbe577.LOG
from issues.
Here is the verbose log :
verbose log.txt
I tried to build from visual studio with success (ACL are set in this case). So I compared the product.wixobj and saw differences :
the working one from VS2022 (x64 compilation)
<row sourceLineNumber="C:\TEMP\wix4test\SetupWix314\product.wxs*28">
<field>Directory</field>
<field>PROGRAMDATA.LocalProjects</field>
</row>
<row sourceLineNumber="C:\TEMP\wix4test\SetupWix314\product.wxs*30">
<field>CustomAction</field>
<field>SchedSecureObjects_x64</field>
</row>
<row sourceLineNumber="C:\TEMP\wix4test\SetupWix314\product.wxs*34">
<field>Directory</field>
<field>PROGRAMDATA.Temp</field>
</row>
<row sourceLineNumber="C:\TEMP\wix4test\SetupWix314\product.wxs*36">
<field>CustomAction</field>
<field>SchedSecureObjects_x64</field>
</row>
and the one from candle.exe :
<row sourceLineNumber="C:\TEMP\wix4test\SetupWix314\product.wxs*28">
<field>Directory</field>
<field>PROGRAMDATA.LocalProjects</field>
</row>
<row sourceLineNumber="C:\TEMP\wix4test\SetupWix314\product.wxs*30">
<field>CustomAction</field>
<field>SchedSecureObjects</field>
</row>
<row sourceLineNumber="C:\TEMP\wix4test\SetupWix314\product.wxs*34">
<field>Directory</field>
<field>PROGRAMDATA.Temp</field>
</row>
<row sourceLineNumber="C:\TEMP\wix4test\SetupWix314\product.wxs*36">
<field>CustomAction</field>
<field>SchedSecureObjects</field>
</row>
In this case there are no _x64 in SchedSecureObjects
so in my script I added "-arch x64" as parameter for candle.exe and bingo, it is working now.
With the 3.11 without specifying the arch, it was working.
from issues.
this commit trigger this change :
https://github.com/wixtoolset/wix3/blame/develop/src/tools/wix/CompilerCore.cs#L875
it is doing nothing in case of x86.
and the default platform value of candle is x86 : https://github.com/wixtoolset/wix3/blob/master/src/tools/candle/candle.cs#L52
from issues.
Related Issues (20)
- The Name property of a focusable element is null for the document on 'End-user license agreement' window. HOT 2
- The Name property of a focusable element is null for 'Status' progress bar available on 'Installing Microsoft SQL server...' window. HOT 2
- The RangeValue pattern of a progress bar doesn't have specific Minimum, Maximum, IsReadOnly values. HOT 2
- Page Not Found: /schemas/v4/wxs/util HOT 1
- Page Not Found: /schemas/v4/wxs/sql HOT 1
- Merge modules don't extract during decompilation
- error WIX0204: ICE80: This package contains 64 bit component 'Foo' but the Template Summary Property does not contain Intel64 or x64. HOT 5
- Page Not Found: /documentation/manual/v3/main/ HOT 1
- `wix msi decompile -x` removes modularization GUIDs from object fields HOT 2
- NetFx Extension Always Produces Warning WIX5439 During Build
- WIP: WiX v5: Default feature
- WiX should correctly set the MSICHECKCRCS property
- Consider `Ref` suffix for more attributes HOT 2
- Expose `WixShellExecBinary` custom action
- WIP: WiX v5: Default root directory
- Culture-specific `TargetPath` preprocessor variable no longer works in WiX v4 HOT 2
- RegisterFonts action is not added to the InstallExecuteSequence when fonts are being installed to the FontsFolder.
- Action SchedServiceConfig fails in MsiGetComponentState call during Windows Service installation HOT 4
- Mismatch between File/@Id behavior and documentation
- Level error messages do refer to Level attribute instead of Value attribute. HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from issues.