This prevents the .NET ZipArchive (and friends) from keeping the whole
thing in memory, to support updating when we don't need to update the
Wixout when building a binary Wixlib.
Added translations in line with existing translations. I'm sure they'll
suffice for now, Google translate makes sense of them anyway.
Signed-off-by: Bevan Weiss <bevan.weiss@gmail.com>
Fixed bug in capping the thread count between 1 and processor count times 2. The "-ct 1000000" value was wrongly passed thru in the test CabinetFilesSequencedCorrectly
Added ThreadCount to UpdateFileFacadesCommand
When ::GetFileAttributesW returns 0xFFFFFFFF it means
'Invalid File/Folder'
So we should return a matching error message.
To avoid confusing invalid paths with junctions (in error message)
Unfortunately the constant for this is not defined.
So just define it here as though it would be.
Signed-off-by: Bevan Weiss <bevan.weiss@gmail.com>
Contains no files etc to verify that Remove action can still occur without
other elements bringing in the RemoveFiles Standard Action
Signed-off-by: Bevan Weiss <bevan.weiss@gmail.com>
Fix up lack of WIX CUSTOM_ACTION_DECORATION wrappers
Add new RuntimeTest skipper for Server Features / Optional Features.
Signed-off-by: Bevan Weiss <bevan.weiss@gmail.com>
Generally, clean up the handling of getting the domain from a server name by
centralizing and simplifying it behind an improved GetDomainFromServerName()
based on the buggy GetServerName().
Fixes 8576
Spillover from having more interactive controls. In WiX v3, showing a
page moved the focus as a typical person might expect. When WiX v4
added interactivity, the same code was used to update controls (e.g.,
when checking a checkbox set a property used in a `VisibleCondition` or
`EnableCondition` for another control on the same page). This change
prevents the focus-setting behavior if the same page is being shown.
Fixes https://github.com/wixtoolset/issues/issues/8144
Neither "reg import" nor "reg add" appeared to work inside the sandbox
So went with "regedit /s {path}" which did work.
Signed-off-by: Bevan Weiss <bevan.weiss@gmail.com>
Install both the x64 AND the x86 versions of Windows Desktop Runtime.
Needed for the Burn Integration tests.
And having dotnet files in the sandbox directory was annoying, so put
them all into an assets directory
Signed-off-by: Bevan Weiss <bevan.weiss@gmail.com>
Removed ARM64/AMD64 folders for dotnet, the Sandbox MUST match the host
here, so no point downloading the installer for the non-host platform.
Debugger could probably be reduced in the same manner, but have not in
this iteration.
Have also added a simple README, just to explain (very basic) operation.
Signed-off-by: Bevan Weiss <bevan.weiss@gmail.com>
By default enable /noauth and /anyuser on the debugger, and don't show the
security warning (/nosecuritywarn).
It'll still show the firewall warning prompt. Default settings should be
fine for firewall (Private networks).
Signed-off-by: Bevan Weiss <bevan.weiss@gmail.com>
It will now prompt for configuring the Remote Debugger if it can find it
on the host when doing the setup.
And will prompt within the Sandbox to run the Debugger at startup if found
It will also show the host-local IP address to connect to the debugger.
In addition, it will display a small menu to allow for simple selection of
a particular runtests.cmd version to execute.
I still haven't found a good way to get a debugger attached into the msiexec
environment without already having a coded breakpoint in, however.
Also added this sandbox folder to .gitignore, so that artifacts from here
aren't committed into the repo
Signed-off-by: Bevan Weiss <bevan.weiss@gmail.com>
Will automatically 'install' dotnet/dotnet sdk into sandbox at startup
based on versions in 'src/test/sandbox/{AMD64,ARM64}' (dotnet-runtime.zip
& dotnet-sdk.zip).
Running ./src/test/sandbox/setup_sandbox.bat will download the required
files (when run on the host).
If the files aren't available, and the guest has network, it will attempt
to download the files itself at startup.
Still to be done:
* menu at startup to allow easy one button selection of which particular
test set to run
* investigation into whether vstest.console.exe can be used to capture test
execution, and possibly have the sandbox available as a test runner, so MSI
tests could be run in the sandbox directly from the dev environment.
Signed-off-by: Bevan Weiss <bevan.weiss@gmail.com>
The MSBuild Version property is well-known and can be set by standard
processes. That can cause problem in the tests where the version is explicitly
set to validate WiX behaviors. So, we've switched to using the TestVersion
property that will be specific for our testing purposes.
Bob Arnson
Bevan Weiss
Chaojie
Martin Broholm Andersen
Rob Mensching
Rami
Kuba314
Peter Hull