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
Seem to always see this on first run, sometimes more often. We should ensure we update or see if there's a resolution or workaround for this somewhere...
Steps to reproduce
Build WASM head (not the IIS one) in an experiment, get this issue sometimes (usually on first run, sometimes more frequently):
5>C:\Users\mhawker\.nuget\packages\uno.wasm.bootstrap\3.3.1\build\Uno.Wasm.Bootstrap.targets(175,5): error : System.ApplicationException: Unable to move PACKAGE DIST H:\code\CommunityToolkitWindows\components\Converters\heads\Wasm\obj\Debug\net5.0\dist_work to H:\code\CommunityToolkitWindows\components\Converters\heads\Wasm\bin\Debug\net5.0\dist\package_153e6e3933bc5d07d488f97e23bf3e5b69d0c95a: System.IO.IOException: Access to the path 'H:\code\CommunityToolkitWindows\components\Converters\heads\Wasm\obj\Debug\net5.0\dist_work' is denied.
5>C:\Users\mhawker\.nuget\packages\uno.wasm.bootstrap\3.3.1\build\Uno.Wasm.Bootstrap.targets(175,5): error : at System.IO.Directory.InternalMove(String sourceDirName, String destDirName, Boolean checkHost)
5>C:\Users\mhawker\.nuget\packages\uno.wasm.bootstrap\3.3.1\build\Uno.Wasm.Bootstrap.targets(175,5): error : at Uno.Wasm.Bootstrap.ShellTask_vfc89b40db92a14b8f04d4c5c9c72690bdcd7b878.PrepareFinalDist() in D:\a\1\s\src\Uno.Wasm.Bootstrap\ShellTask.cs:line 1282 ---> System.IO.IOException: Access to the path 'H:\code\CommunityToolkitWindows\components\Converters\heads\Wasm\obj\Debug\net5.0\dist_work' is denied.
5>C:\Users\mhawker\.nuget\packages\uno.wasm.bootstrap\3.3.1\build\Uno.Wasm.Bootstrap.targets(175,5): error : at System.IO.Directory.InternalMove(String sourceDirName, String destDirName, Boolean checkHost)
5>C:\Users\mhawker\.nuget\packages\uno.wasm.bootstrap\3.3.1\build\Uno.Wasm.Bootstrap.targets(175,5): error : at Uno.Wasm.Bootstrap.ShellTask_vfc89b40db92a14b8f04d4c5c9c72690bdcd7b878.PrepareFinalDist() in D:\a\1\s\src\Uno.Wasm.Bootstrap\ShellTask.cs:line 1282
5>C:\Users\mhawker\.nuget\packages\uno.wasm.bootstrap\3.3.1\build\Uno.Wasm.Bootstrap.targets(175,5): error : --- End of inner exception stack trace ---
5>C:\Users\mhawker\.nuget\packages\uno.wasm.bootstrap\3.3.1\build\Uno.Wasm.Bootstrap.targets(175,5): error : at Uno.Wasm.Bootstrap.ShellTask_vfc89b40db92a14b8f04d4c5c9c72690bdcd7b878.PrepareFinalDist() in D:\a\1\s\src\Uno.Wasm.Bootstrap\ShellTask.cs:line 1287
5>C:\Users\mhawker\.nuget\packages\uno.wasm.bootstrap\3.3.1\build\Uno.Wasm.Bootstrap.targets(175,5): error : at Uno.Wasm.Bootstrap.ShellTask_vfc89b40db92a14b8f04d4c5c9c72690bdcd7b878.Execute() in D:\a\1\s\src\Uno.Wasm.Bootstrap\ShellTask.cs:line 234
### Expected behavior
Builds and deploys without issue
### Screenshots
_No response_
### Code Platform
- [ ] UWP
- [ ] WinAppSDK / WinUI 3
- [X] Web Assembly (WASM)
- [ ] Android
- [ ] iOS
- [ ] MacOS
- [ ] Linux / GTK
### Windows Build Number
- [ ] Windows 10 1809 (Build 17763)
- [ ] Windows 10 1903 (Build 18362)
- [ ] Windows 10 1909 (Build 18363)
- [ ] Windows 10 2004 (Build 19041)
- [ ] Windows 10 20H2 (Build 19042)
- [ ] Windows 10 21H1 (Build 19043)
- [ ] Windows 11 21H2 (Build 22000)
- [ ] Other (specify)
### Other Windows Build number
_No response_
### App minimum and target SDK version
- [ ] Windows 10, version 1809 (Build 17763)
- [ ] Windows 10, version 1903 (Build 18362)
- [ ] Windows 10, version 1909 (Build 18363)
- [ ] Windows 10, version 2004 (Build 19041)
- [ ] Other (specify)
### Other SDK version
_No response_
### Visual Studio Version
_No response_
### Visual Studio Build Number
_No response_
### Device form factor
_No response_
### Additional context
_No response_
### Help us help you
No, I'm unable to contribute a solution.
The text was updated successfully, but these errors were encountered:
Describe the bug
Seem to always see this on first run, sometimes more often. We should ensure we update or see if there's a resolution or workaround for this somewhere...
Steps to reproduce
The text was updated successfully, but these errors were encountered: