From 1c6d9e28f7bb5e620823c024e33849dbb983a186 Mon Sep 17 00:00:00 2001
From: Sandy Armstrong <sandy@xamarin.com>
Date: Thu, 25 Jul 2019 06:17:17 -0700
Subject: Build: Use a property to access the vs-editor-api directory

This should make it easier for us to have all vs-editor-api references
point to vs-editor-core when available. There are some blockers to that
change, so for now just take this one preparatory step.
---
 main/msbuild/ReferencesVSEditor.Mac.props | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

(limited to 'main/msbuild')

diff --git a/main/msbuild/ReferencesVSEditor.Mac.props b/main/msbuild/ReferencesVSEditor.Mac.props
index 67ff2d19fa..b371f9f472 100644
--- a/main/msbuild/ReferencesVSEditor.Mac.props
+++ b/main/msbuild/ReferencesVSEditor.Mac.props
@@ -51,15 +51,15 @@
     <IncludeCopyLocal Include="Microsoft.VisualStudio.UI.Text.CurrentLineHighlighter.Implementation.dll" />
   </ItemGroup>
 
-  <Import Project="$(RootDirectory)external\vs-editor-api\build\Environment.props" />
-  <Import Project="$(RootDirectory)external\vs-editor-api\ProjectReferences.projitems" />
+  <Import Project="$(VSEditorApiDirectory)build\Environment.props" />
+  <Import Project="$(VSEditorApiDirectory)ProjectReferences.projitems" />
 
   <!-- MSBuild doesn't copy the FPF references as they match BCL assembly names -->
   <Target Name="CopyFPFAssemblies" AfterTargets="_CopyFilesMarkedCopyLocal" Condition="'$(ReferencesVSEditorCopyToOutput)'=='true'">
     <PropertyGroup>
       <FPFConfiguration>Release</FPFConfiguration>
       <FPFConfiguration Condition="$(Configuration.Contains('Debug'))">Debug</FPFConfiguration>
-      <FPFOutputPath>$(RootDirectory)external\vs-editor-api\bin\FPF\$(FPFConfiguration)\net472\</FPFOutputPath>
+      <FPFOutputPath>$(VSEditorApiDirectory)bin\FPF\$(FPFConfiguration)\net472\</FPFOutputPath>
     </PropertyGroup>
     <ItemGroup>
       <FPFOutputFiles Include="$(FPFOutputPath)PresentationCore.*" />
-- 
cgit v1.2.3