From 17c5d44ff3358d4b76a81da72608d7b00fbdb868 Mon Sep 17 00:00:00 2001
From: yao-msft <50888816+yao-msft@users.noreply.github.com>
Date: Mon, 29 Apr 2024 10:33:53 -0700
Subject: [PATCH] Explicitly add Microsoft.Management.Configuration as remoting
 server dependency (#4418) (#4419)

There's some issue with the build toolchain in internal pipeline that
deep dependencies (3 level deep) are not picked up by the build.
Explicitly adding the dependency fixed the issue. Manually validated the
release package produced by internal pipeline and mixed elevation works
as expected.
---
 .../ConfigurationRemotingServer.csproj                           | 1 +
 1 file changed, 1 insertion(+)

diff --git a/src/ConfigurationRemotingServer/ConfigurationRemotingServer.csproj b/src/ConfigurationRemotingServer/ConfigurationRemotingServer.csproj
index 110924477b..979171e0f8 100644
--- a/src/ConfigurationRemotingServer/ConfigurationRemotingServer.csproj
+++ b/src/ConfigurationRemotingServer/ConfigurationRemotingServer.csproj
@@ -34,6 +34,7 @@
 
   <ItemGroup>
     <ProjectReference Include="..\Microsoft.Management.Configuration.Processor\Microsoft.Management.Configuration.Processor.csproj" />
+    <ProjectReference Include="..\Microsoft.Management.Configuration\Microsoft.Management.Configuration.vcxproj" />
   </ItemGroup>
 
   <Target Name="PwshFiles" AfterTargets="AfterBuild">