-
Notifications
You must be signed in to change notification settings - Fork 10.5k
Closed
Copy link
Labels
area-infrastructureIncludes: MSBuild projects/targets, build scripts, CI, Installers and shared frameworkIncludes: MSBuild projects/targets, build scripts, CI, Installers and shared framework
Milestone
Description
Potentially regressed with #58721
C:\git\dotnet\src\aspnetcore\src\Assets\Microsoft.AspNetCore.App.Internal.Assets.csproj(46,5): error : 'C:\git\dotnet\src\aspnetcore\src\Components\Web.JS\dist\Rel
ease\blazor.web.js' does not exist. Run 'npm run build' in the repo root to generate the file.
C:\git\dotnet\src\aspnetcore\src\Components\WebView\WebView\src\Microsoft.AspNetCore.Components.WebView.csproj(68,5): error : '..\..\..\Web.JS\dist\Release\blazor.
webview.js' does not exist. Falling back to checked-in copy.
CSC : error CS1566: Error reading resource '_framework/blazor.webview.js' -- 'Could not find a part of the path 'C:\git\dotnet\src\aspnetcore\src\Components\Web.JS
\dist\Release\blazor.webview.js'.' [C:\git\dotnet\src\aspnetcore\src\Components\WebView\WebView\src\Microsoft.AspNetCore.Components.WebView.csproj]
Also note that this logic doesn't work anymore:
aspnetcore/src/Components/WebView/WebView/src/Microsoft.AspNetCore.Components.WebView.csproj
Line 68 in 3ba179a
<Warning Text="'$(BlazorWebViewJSFile)' does not exist. Falling back to checked-in copy." /> |
CI triggers a dev workflow job that validates certain dev scenario but building the managed part with --no-build-nodejs
unfortunately isn't validated.
Metadata
Metadata
Assignees
Labels
area-infrastructureIncludes: MSBuild projects/targets, build scripts, CI, Installers and shared frameworkIncludes: MSBuild projects/targets, build scripts, CI, Installers and shared framework