MonoGame ContentLoadException and platform-specific path resolution

The MonoGame Content Pipeline processes source assets into platform-specific .xnb binary files. While the ContentManager class resolves these paths relative to the Content root directory, behavior varies when deploying across different operating systems.

A specific challenge arises when moving a project from a case-insensitive environment, such as Windows, to a case-sensitive environment, such as Android or Linux. This can lead to a ContentLoadException during runtime, even if the assets were successfully compiled by the MGCB Editor and are present in the build output folder.

Given these constraints, what is the recommended strategy for ensuring path consistency across platforms? Does MonoGame provide a built-in mechanism to enforce case-sensitivity during the build phase to prevent deployment-time crashes?