From 22a8dca22fbf1d430c64502932c40fd8628f821d Mon Sep 17 00:00:00 2001
From: Andrew Arnott <andrew.arnott@microsoft.com>
Date: Tue, 20 Jun 2023 08:07:02 -0600
Subject: [PATCH] Use MSBuild computed full paths for input metadata

This fixes an issue @riverar reported in #356.
---
 .../build/Microsoft.Windows.CsWin32.props                     | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/src/Microsoft.Windows.CsWin32/build/Microsoft.Windows.CsWin32.props b/src/Microsoft.Windows.CsWin32/build/Microsoft.Windows.CsWin32.props
index 5ec07ae9..2ebc91df 100644
--- a/src/Microsoft.Windows.CsWin32/build/Microsoft.Windows.CsWin32.props
+++ b/src/Microsoft.Windows.CsWin32/build/Microsoft.Windows.CsWin32.props
@@ -19,8 +19,8 @@
   <Target Name="AssembleCsWin32InputPaths" BeforeTargets="GenerateMSBuildEditorConfigFileCore">
     <!-- Roslyn only allows source generators to see msbuild properties, to lift msbuild items into semicolon-delimited properties. -->
     <PropertyGroup>
-      <CsWin32InputMetadataPaths>@(ProjectionMetadataWinmd,'|')</CsWin32InputMetadataPaths>
-      <CsWin32InputDocPaths>@(ProjectionDocs,'|')</CsWin32InputDocPaths>
+      <CsWin32InputMetadataPaths>@(ProjectionMetadataWinmd->'%(FullPath)','|')</CsWin32InputMetadataPaths>
+      <CsWin32InputDocPaths>@(ProjectionDocs->'%(FullPath)','|')</CsWin32InputDocPaths>
     </PropertyGroup>
   </Target>
 </Project>