| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
| |
Fixes 8940
|
|
|
|
| |
Signed-off-by: Bevan Weiss <bevan.weiss@gmail.com>
|
| |
|
|
|
|
|
|
| |
Fixups to a few test cases.
Signed-off-by: Bevan Weiss <bevan.weiss@gmail.com>
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Local group membership Add/Remove working, however with
BUILTIN local system groups .NET doesn't appear to locate them as either
groups nor basic security Principals. Still needs work to fix the test
for nested groups. Ideally with some way to test for domain groups.
Signed-off-by: Bevan Weiss <bevan.weiss@gmail.com>
|
|
|
|
| |
Signed-off-by: Bevan Weiss <bevan.weiss@gmail.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Windows Sandbox.
This is potentially a Windows OS bug (it was from a Windows Insider build),
however shows that it's possible in the Firewall API to have multiple rules
which differ only in their Grouping.
So the testbench should consider different Grouping as making for a unique
firewall rule.
Signed-off-by: Bevan Weiss <bevan.weiss@gmail.com>
|
|
|
|
| |
Signed-off-by: Bevan Weiss <bevan.weiss@gmail.com>
|
|
|
|
| |
Fixes https://github.com/wixtoolset/issues/issues/8913
|
|
|
|
|
|
|
| |
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".
|
|
|
|
|
| |
Also, standardize .NET Core TFMs listed before .NET Framework TFMs for no
reason but to be consistent
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Table names updated for Wix4 prefix.
Custom action names similarly updated.
Table names Wix4ComPlusUserInApplicationRole,
Wix4ComPlusGroupInApplicationRole and Wix4ComPlusApplicationRoleProperty
had to be shortened to fit within MSI 31 character table name limit.
Migrated from fixed GUID for RegistrationHelper to use CLSIDFromProgID in
an attempt to fix behaviour under .NET 4+ DLLs.
Added setting of Partition enable if a Partition is configured in authoring,
new Windows config has Partitions disabled by default, and they don't work
at all under Windows workstation (non-server) versions.
Added a new Runtime condition for `RequireWindowsServer` which will skip
execution of Runtime test on workstation/desktop OSes, since COM+ Partitions
only work correctly under Windows Server.
Quite a lot of basic typos fixed also.
Signed-off-by: Bevan Weiss <bevan.weiss@gmail.com>
|
|
|
|
| |
Signed-off-by: Bevan Weiss <bevan.weiss@gmail.com>
|
|
|
|
| |
At least one person makes the same typo almost-but-not-quite everywhere.
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
| |
Fixes 8638
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
| |
firewall rules.
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>
|
|
|
|
|
|
|
| |
Fix a couple of copy-paste errors in the "don't have files from
host in Sandbox" path also.
Signed-off-by: Bevan Weiss <bevan.weiss@gmail.com>
|
|
|
|
|
|
| |
Not sure if it's ideal, but it works..
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>
|
|
|
|
|
|
| |
And a fix up for the tests not launching the first try
(due to delayed expansion).
Also fixed up the copying of the debugger files.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
| |
folder
Fixes 8078
|
| |
|
|
|
|
|
|
|
|
| |
WiX v4 (and probably v3) standardized on the error code E_MOREDATA when string
buffers were too small instead of E_INSUFFICIIENT_BUFFER. This fixes v5 to
match in a few missing cases.
Fixes 8094
|
| |
|
|
|
|
|
| |
Take this breaking change opportunity to simplify the header files used by
BA devs.
|
| |
|
|
|
|
| |
Fixes https://github.com/wixtoolset/issues/issues/8036.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Fixes https://github.com/wixtoolset/issues/issues/7798.
|
|
|
|
| |
UninstallArguments for the uninstall command line
|
| |
|
| |
|
|
|
|
| |
attributes
|
| |
|