| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
***Does not include a full conversion to traversal projects. The wix
segment already uses traversal projects extensively so there isn't a
significant per win, especially compared to the effort required...but
MSTest's method-level parallelism cuts test run time in half (~60->~30).
|
|
|
|
|
|
|
| |
The "bundle id" always had more in common with the PackageCode from the Windows
Installer. With the introduction of an actual Id attribute on the Bundle
element, there is potential for confusion, so there is finally real motivation
to rename "bundle id" to "bundle code".
|
|
|
|
| |
Completes 8584
|
| |
|
|
|
|
|
|
|
| |
...because SemVer is just a suggestion.
- Also fix missing NuGet cleanup.
- And update NuGet^2 packages because v6.3.1 has vulnerabilities.
|
|
|
|
| |
Fixes 7343
|
| |
|
|
|
|
| |
Closes 7241
|
|
|
|
|
|
|
|
| |
WiX v4 standardized on GitHub Actions for the build process. AppVeyor
served us well and provides a great service for free. But since we moved
to GitHub Actions let's not burn cycles on their build machines.
Closes 7175
|
|
|
|
|
|
|
|
|
|
| |
The WixToolset.Sdk is an MSBuild project SDK. It should be imported
using the Sdk.props. Allowing it to be imported via PackageReference is
unnecessary and creates double import problems. Prevent such imports to
point WiX users that don't understand the new MSBuild functionality
in the right direction.
Fixes 7148
|
|
|
|
| |
Fixes 7085
|
|
|
|
| |
Fixes 7035
|
|
|
|
|
|
|
| |
Write the tests for the test data in the WixToolset.Sdk test and fix
all the culture related bugs that fallout from that.
Fixes 69999
|
|
|
|
|
|
| |
Also, resolves bind variables in path fields.
Fixes 6995 and 7017
|
| |
|
|
|
|
| |
Fixes 6970
|
|
|
|
| |
Closes 6959
|
|
|
|
|
|
|
|
| |
WiX v3 extension loading had options that were rarely if ever used
and library paths modeled after C++. Given the new Sdk-style model
in WiX v4, we can simplify reference resolution.
Fixes 6945, 6946
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
"wix build" will load assemblies to read metadata which can cause
the assemblies to get locked in the process. Since MSBuild keeps
build processes alive this can cause work done by in-proc MSBuild
tasks (like the WixBuild) to get stuck. Moving the "wix build" out
of proc avoids any of those issues.
Moving out of proc also allows the WiX tasks to be AnyCPU which
simplifies the wix.targets (although did need to add code to find
the .NET Framework wix.exe).
Fixes 6595
|
| |
|
|
|
|
| |
Fixes 6857
|
|
|
|
|
|
|
| |
Moves Heat functionality to the "tools" layer and packages it all
up in WixToolset.Heat.nupkg for distribution in WiX v4.
Completes 6838
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
First, moved the tests build into a separate directory to prevent
collisions with shipping code. That requires each test to copy in
the required native binaries. Default the native binaries to x64
for testing since we've standardized on VS2022 which is all x64 all
the time. Finally, copy the native binaries into the .NET Framework
differently from .NET Core because .NET Framework does not support
cross-platform thus requires a different layout.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When the validation tests are run repeatedly, they will expose an issue
in the Windows Installer where ICE validations will occasionally
fail to send all error/warning messages. The inconsistency obviously
wreaks havoc on the tests.
The tests are still interesting (and complex) enough to keep around
for manual testing. So they were placed behind an #if for easy manual
inclusion.
Note that these are "negative tests" that expose the Windows Installer
inconsistency when expected failures are missing. Other validation tests
are "positive tests" that look for success and thus will always
succeed. Therefore, the positive tests stay active.
|
| |
|
| |
|
|
|
|
| |
This should prevent validation from running in parallel.
|
| |
|
| |
|
|
|
|
|
|
|
| |
In MSBuild this adds a new WindowsInstallerValidation target that
automatically runs validation after a successful build. From the
command-line the "wix msi" command gets a "validate" subcommand that
will validate an MSI or MSM file.
|
| |
|
| |
|
|
|
|
|
|
|
| |
A single tracking file can be enhanced more easily than continuing
to introduce specialized tracking files. In this case, we now
include output files that are copied and can differentiate them from
the built output files.
|
| |
|
| |
|
|
|
|
| |
Tests are not run inside of traversal projects so that skipped test warnings don't fail the build.
|
|
|
|
| |
Closes wixtoolset/issues#6407
|
| |
|
|
|
|
|
|
|
| |
Update v4.0 projects to target v4.7.2.
Skip all Bal managed host tests for now.
Remove ToolsVersion from DTF test projects.
Remove Microsoft.NETFramework.ReferenceAssemblies from Directory.Packages.props.
|
| |
|
|
|