wix/src/test/burn, branch bob/UpdateRegistrationAcrossUpgrades A mirror of https://github.com/wixtoolset/wix.git https://git.lua4.win/wix/atom?h=bob%2FUpdateRegistrationAcrossUpgrades 2025-03-24T22:18:52+00:00 Update registration disappears during upgrade. 2025-03-24T22:18:52+00:00 Bob Arnson bob@firegiant.com 2025-03-21T01:14:12+00:00 urn:sha1:f3fb208959d5ef2f8df19f518224d413b233f751 Update registration is stored in a shared registry key that Burn takes care to keep around across upgrades. The approach it used broke between WiX v3 and WiX v5. This change makes it work again by writing update registration when the session ends. Fix ups for Domain Group creation / removal. 2025-02-12T07:14:49+00:00 Bevan Weiss bevan.weiss@gmail.com 2025-01-03T04:06:15+00:00 urn:sha1:8f5130afdc60f4957086e41d62cfe9f8d70d5321 Signed-off-by: Bevan Weiss <bevan.weiss@gmail.com> Group creation and update PR nits and feedback fixes 2025-02-12T07:14:49+00:00 Rob Mensching rob@firegiant.com 2024-12-25T02:11:55+00:00 urn:sha1:eda11c7eb726da970de68c5b353f946d1da0a7a3 Add/Remove Group Membership rollback handled. 2025-02-12T07:14:49+00:00 Bevan Weiss bevan.weiss@gmail.com 2024-08-04T11:13:44+00:00 urn:sha1:5b4a6538ee06988c75b717bd905197fb670e6142 Fixups to a few test cases. Signed-off-by: Bevan Weiss <bevan.weiss@gmail.com> Group Add/Remove working. 2025-02-12T07:14:49+00:00 Bevan Weiss bevan.weiss@gmail.com 2024-07-06T11:03:57+00:00 urn:sha1:644276562dcadd65fcb0e9a7c06c704cdda36423 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> CreateGroups additions 2025-02-12T07:14:49+00:00 Bevan Weiss bevan.weiss@gmail.com 2024-06-18T09:03:40+00:00 urn:sha1:7b1bb025dea1d1e9e144cce0dcbba2d86f053b8f Signed-off-by: Bevan Weiss <bevan.weiss@gmail.com> Rewrite Prereq tests after hardening and bypassing .NET GUI errors 2025-02-11T23:49:33+00:00 Rob Mensching rob@firegiant.com 2025-02-11T21:53:50+00:00 urn:sha1:040e50ec2859c1de70cd8e9f957474321774f293 Failures were seen in MSI Unit Tests around Firewall rules within 2025-02-11T22:57:26+00:00 Bevan Weiss bevan.weiss@gmail.com 2025-01-01T04:41:46+00:00 urn:sha1:cfb2df2e88b9ee273852124bbbdb1342207e96f9 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> Emit deprecation warning for Heat. 2025-01-23T13:44:13+00:00 Bob Arnson bob@firegiant.com 2025-01-23T03:45:45+00:00 urn:sha1:63223d5c023846ab7b4cef222326c913d2e0521f Fixes https://github.com/wixtoolset/issues/issues/8913 Rename "bundle id" concept to "bundle code" 2024-12-30T14:45:49+00:00 Rob Mensching rob@firegiant.com 2024-12-30T02:01:20+00:00 urn:sha1:523c66a62a619e6aa9f30070173ea33edfb5e328 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".