You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Build.ps1 hardcoded configuration to Release by configurationForMrtAndAnyCPU, which caused BuildAll.ps1 with configuration Debug failed on clean build, it failed with error:
Cannot find path '<WindowsAppSDKPath>\BuildOutput\Release\x64\mrm\MRM.dll' because it does not exist.
at <ScriptBlock>, <WindowsAppSDKPath>\BuildAll.ps1: line 304
Steps to reproduce the bug
Run a clean build (all release output need to be removed) of BuildAll.cmd -Configuration:Debug.
It seems that there are a special configuration variable for MRT called configurationForMrtAndAnyCPU, which is hardcoded to "Release",
and when build MRT, it uses configurationToRun.
If we run BuildAll.cmd in Debug mode, after build MRT, when copying output, it will look result from Release directory, and those dll is not found.
Expected behavior
No response
Screenshots
No response
NuGet package version
None
Packaging type
No response
Windows version
No response
IDE
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
Describe the bug
Build.ps1
hardcoded configuration toRelease
byconfigurationForMrtAndAnyCPU
, which causedBuildAll.ps1
with configurationDebug
failed on clean build, it failed with error:Steps to reproduce the bug
Run a clean build (all release output need to be removed) of
BuildAll.cmd -Configuration:Debug
.It seems that there are a special configuration variable for MRT called configurationForMrtAndAnyCPU, which is hardcoded to "Release",
and when build MRT, it uses configurationToRun.
If we run
BuildAll.cmd
inDebug
mode, after build MRT, when copying output, it will look result fromRelease
directory, and those dll is not found.Expected behavior
No response
Screenshots
No response
NuGet package version
None
Packaging type
No response
Windows version
No response
IDE
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: