-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When <AppId> is child of <Package>: System.ArgumentNullException during build #7738
Comments
The call stack looks like this: wix.exe : error WIX0001: System.ArgumentNullException: Value cannot be null. [C:\Projects\ZDD\SetupZDD\Package\Package.wixproj] The command exited with code -2147467261. (TaskId:53) Output Property: _WixBuildExitCode=-2147467261 (TaskId:53) Done executing task "WixBuild" -- FAILED. (TaskId:53) |
The System.ArgumentNullException is because the parent component ID is null. Since the parent is a package, there is no parent component. However, this did work in v3.14, and the schema documentation states that the parent of can be a . |
Bugs
If this issue is a bug:
Which version of WiX are you building with?
WiX 4.0.2
Which version of Visual Studio are you building with (if any)?
Visual Studio 2022 17.7.4
Which version of the WiX Toolset Visual Studio Extension are you building with (if any)?
HeatWave for VS2022
Which version of .NET are you building with?
4.8
If the problem occurs when installing your packages built with WiX, what is the version of Windows the package is running on?
n/a
Describe the problem and the steps to reproduce it.
Add an
<AppId>
element like this as a direct child of the<Package>
element:When you try to build the package, it will fail with the following error:
wix.exe : error WIX0001: System.ArgumentNullException: Value cannot be null.
If you remove the
<AppId>
element, the problem goes away.This worked in WiX 3.14.
When you try to build the package, it will fail with the following error:
If you remove the
<AppId>
element, the problem goes away.This worked in WiX 3.14.
The text was updated successfully, but these errors were encountered: