commit 2ea30553b333b00e631ec49529bf765c0dd4b008
parent 5f7b46bad68161b06bda2d3fbff8b9e9132ec927
Author: yao-msft <50888816+yao-msft@users.noreply.github.com>
Date: Sat, 27 Apr 2024 01:01:46 -0700
Explicitly add Microsoft.Management.Configuration as remoting server dependency (#4418)
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.
###### Microsoft Reviewers: [Open in
CodeFlow](https://microsoft.github.io/open-pr/?codeflow=https://github.com/microsoft/winget-cli/pull/4418)
Diffstat:
1 file changed, 1 insertion(+), 0 deletions(-)
diff --git 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">
