NuGet.LockFile.props

<?xml version="1.0" encoding="utf-8"?>
<Project xmlns="http://schemas.microsoft.com/developer/msbuild/2003">

  <!-- This props file is intended to make sure in-repo projects restore with a NuGet
       lock file for compliance reasons, and furthermore to help differentiate the
       lock file (i.e. packages.lock.json) for projects that we build in in different
       variants, such as Paper vs. Fabric, Hermes vs. Chakra, etc.
       -->

  <PropertyGroup>
    <RestoreLockedMode Condition="'$(RestoreLockedMode)'=='' OR '$(BuildingInRnwRepo)'=='true'">true</RestoreLockedMode>
    <!--
      VS's NuGet restore cannot evaluate vcxproj PackageReferences through the project reference
      chain (the VC project system does not report them via the CPS nomination API). This causes
      NU1004 lock file mismatches for csproj files that reference vcxproj. Disable locked mode
      in VS so the initial restore succeeds and package targets load correctly.
      CI is unaffected: it passes /p:RestoreLockedMode=true as a global property which overrides this.
    -->
    <RestoreLockedMode Condition="'$(BuildingInsideVisualStudio)' == 'true' AND '$(MSBuildProjectExtension)' == '.csproj'">false</RestoreLockedMode>

    <NuGetLockFileName>packages</NuGetLockFileName>
    <NuGetLockFileName Condition="'$(UseExperimentalWinUI3)'=='true'">$(NuGetLockFileName).experimentalwinui3</NuGetLockFileName>
    <NuGetLockFilePath>.\$(NuGetLockFileName).lock.json</NuGetLockFilePath>
  </PropertyGroup>

</Project>