When building with msbuild.exe from the command-line, project references are not taken into account, so the build order of the projects must be explicitly specified in the solution. This issue appeared with the addition of the property /p:BuildingInsideVisualStudio=true, which was required for successfully building Outlines.Package.wapproj using msbuild.exe (see PR #94)
Ideally, we should find a way to successfully build Outlines.Package.wapproj without /p:BuildingInsideVisualStudio=true, but if we don't succeed, a solution might be to import Microsoft.Common.targets in projects with project refences and specify the OutputDirbased of the configuration and platform.
eg. add the following to Outlines.App.csproj:
<Import Project="$(MSBuildExtensionsPath)\Current\bin\Microsoft.Common.targets"/>
When building with msbuild.exe from the command-line, project references are not taken into account, so the build order of the projects must be explicitly specified in the solution. This issue appeared with the addition of the property
/p:BuildingInsideVisualStudio=true
, which was required for successfully buildingOutlines.Package.wapproj
using msbuild.exe (see PR #94)Ideally, we should find a way to successfully build
Outlines.Package.wapproj
without/p:BuildingInsideVisualStudio=true
, but if we don't succeed, a solution might be to importMicrosoft.Common.targets
in projects with project refences and specify theOutputDir
based of the configuration and platform.eg. add the following to Outlines.App.csproj:
<Import Project="$(MSBuildExtensionsPath)\Current\bin\Microsoft.Common.targets"/>
Relevant documentation: