The NormalizePathBadGlobalroot test was skipped due to failing on newer .NET versions where path validation behavior has changed. This test was checking that FileUtilities.NormalizePath(@"\\?\globalroot\XXX") would throw an ArgumentException, but .NET Core 2.1+ no longer validates globalroot paths as a security concern.

Problem

The test was expecting:

• FileUtilities.NormalizePath(@"\\?\globalroot\XXX") to throw ArgumentException
• But instead the method returned the path value, causing Assert.Null() to fail with NullException

Root Cause

Similar to other path validation tests in the same file, .NET Core 2.1+ removed the security validation for globalroot paths that was present in .NET Framework. The underlying Path.GetFullPath() method no longer throws exceptions for these paths.

Solution

Permanently deleted the test since:

1. The security validation it was testing is no longer performed by the .NET runtime
2. Other similar path validation tests in the file are marked with [WindowsFullFrameworkOnlyFact] to only run on older .NET Framework versions
3. This test was completely skipped rather than conditionally executed, indicating the validation is obsolete

Changes

• Removed the NormalizePathBadGlobalroot test method (19 lines)
• Removed the associated empty #if FEATURE_LEGACY_GETFULLPATH conditional compilation block
• Verified the build succeeds with no compilation errors

Fixes #4205.

💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.