IntegrationMSI E2E tests failing: Firewall case sensitivity

[bevanweiss]

When I do a fresh build, and run the MSI E2E tests, I'm getting a number of Firewall extension tests failing (~16 of them).
And it all appears to be because in the firewall rule it's expecting an upper case 'C' for the drive letter, but in the actual rule it's ending up with a lower case 'c'

  Failed WixToolsetTest.MsiE2E.FirewallExtensionTests.CanInstallAndUninstallFirewallRulesPackagedByDifferentModules [1 s]
  Error Message:
   Assert Failure: ApplicationNames differ on rule: WiXToolset401 Test - 0018
Expected: C:\Program Files (x86)\MsiPackage\file1.txt
Actual: c:\Program Files (x86)\MsiPackage\file1.txt

It does seem that the change below in the VerifyFirewallRule(string name, RuleDetails expected, UniqueCheck unique = null) method makes the errors go away.

-            Assert.True(expected.ApplicationName == actual.ApplicationName, FormatErrorMessage(name, "ApplicationNames", expected.ApplicationName, actual.ApplicationName, unique));
+            Assert.True(String.Equals(expected.ApplicationName, actual.ApplicationName,StringComparison.OrdinalIgnoreCase), FormatErrorMessage(name, "ApplicationNames", expected.ApplicationName, actual.ApplicationName, unique));

But I'm unsure if this still makes the test 'valid'. Are the firewall rules always case insensitive?
I've generally assumed Windows to be case-insensitive. But I know that there are ways to make certain aspects care about case, I'm unsure if firewall rules respect that however (or if they are always case insensitive).

[bevanweiss]

The issue was due to the path used to launch the runtests.cmd test file.
The path sent to the START command was c:\build\IntegrationMsi\Debug\net6.0-windows, with a lower case c:\
When replacing it with an upper case C:\, then these firewall tests started to pass fine.