i just wanted to publish my changes to my .Net6 blazor wasm app to azure to update it like i did a dozen times. Since yesterday that does not work anymore. I can build and run it locally with no problem but when I try to publish it, I get a window telling me:
Publish has encountered an error. Build failed. Check the Output
window for more details.
A diagnostic log has been written to the following location:
"C:\Users\user\AppData\Local\Temp\tmpE865.tmp"
Content of that file:
16.06.2022 08:20:08 System.AggregateException: One or more errors occurred. ---> Microsoft.WebTools.Shared.Exceptions.WebToolsException:
Build failed. Check the Output window for more details. --- End of
inner exception stack trace ---
---> (Inner Exception #0) Microsoft.WebTools.Shared.Exceptions.WebToolsException: Build failed.
Check the Output window for more details.<---
Microsoft.WebTools.Shared.Exceptions.WebToolsException: Build failed.
Check the Output window for more details.
===================
Console Output:
C:\Program Files\dotnet\sdk\6.0.400-preview.22301.10\Sdks\Microsoft.NET.Sdk.BlazorWebAssembly\targets\Microsoft.NET.Sdk.BlazorWebAssembly.6_0.targets(614,5): Error MSB6006: "dotnet.exe" exited with code 1.
Tried fetching older versions of the code that I successfully published a few days ago. Still does not work. My coworker can still publish the same code.
But I can publish my API Backend...so this error seems to be related to blazor wasm.
Tried this with the latest release of VS 2022 and just gave the preview version a try - no luck.
I've also done a repair installation of the .Net 6 SDK.
Edit: I've tried to publish my project to a folder and got the same error. So no relation to azure. Then I've created a new blank Blazor app...I can publish this one to a folder with no error. So my project is somehow broken...but even older code can't be published. This is so odd...
Same issue for me. Publish stopped working after the latest VS update.
Removing blanks in path resolved it
#XSharp is correct.
We had same issue started occurring yesterday.
We were using version '6.0.x' of DotNet which seems to have started using version '6.0.301' that seems to be causing this issue. Force it to use the previous version '6.0.106' instead
Just add the following at the top of your tasks in your YAML
- task: UseDotNet#2
inputs:
packageType: 'sdk'
version: '6.0.106'
Looks like someone has reported it as an issue when having a blank space in your project path: https://github.com/dotnet/core/issues/7548
I kept getting error "Microsoft.NET.Sdk.Blazor WebAssembly.6_0.targets(614,5): error MSB6006".
I can confirm once I removed spaces (my directory to mydirectory) on the build environment, the blazor build was successful.
In my case, changing the SDK in the YAML of the pipeline fixed the issue for us.
In UseDotNet#2 task:
Changed : version: '6.0.x'
To : version: '6.0.106'
It was working before so it seems like something has changed in the hosts.
I've had this problem off-and-on for more than a year. Sometimes it seems to be caused by a Visual Studio update and sometimes a dependency (nuget) update, but sometimes it seems spontaneous; I can't seem to figure out the real cause. This time I tried removing spaces from the path, but that did not work.
I got it to publish again after (1) removing spaces from the path, (2) deleting the publish profiles, (3) deleting the hidden ".vs" folder from the solution directory, (4) running "Clean Solution" in VS, (5) deleting all "bin" and "obj" folders from the solution tree, (6) re-importing the publish profile, building, and publishing. I wish I knew which of those really affected the problem, or better yet, I wish MS would fix this bug.
I have been studying azure devops in the past weeek and i have been trying to deoploy my first node app on azure but i keep running on an error of build failed. and the error is
Error Cannot find module './routes/hostelRoutes' so i have checked and confirmed that the module is available because everything runs on my local machine. Below is a pic where i get the error
According to the error message：
Error Cannot find module './routes/hostelRoutes'
The ‘node_modules’ folder could have some issues.
You could try to remove the directory ‘/node_modules/’ and re-install the folder.
Please refer to the following command line script about removing and re-installing.
cd Project_folder
rm -rf node_modules
npm install
You could check this ticket How do I resolve “Cannot find module” error using Node.js? for some information
When I run jest test locally I see all my tests as passed.
PASS apps/web/customers/src/components/TelephoneDial/tests/TelephoneDialButton.test.tsx
When I run jest test in my build on Azure I get the following:
'##[error]PASS apps/web/customers/src/components/TelephoneDial/tests/TelephoneDialButton.test.tsx (8.186s)
During the actual build step on azure I also see this:
'##[error]lerna notice cli v3.13.4
While locally it shows:
lerna notice cli v3.13.4
Why is Azure showing this output as errors?
I haven't found what's causing this issue, but switching from Windows 2019 with VS2019 agent to vs2017-win2016 has fixed the issue, now the output doesn't report errors.
I have followed the tutorial to integrate LUIS and QnA Maker to create a LUIS app. When I got to the final step and tried to build the app, I got the error message
\> \build.cmd
Installing Kudu Sync
An error has occurred during web
site deployment. 'npm' is not recognized as an internal or external
command, operable program or batch file.
Apparently, npm is missing on the build server. How can that be and how can I fix it?
Let's try running build from the console to see if that resolves this issue.
First, from your App Service Editor click on your bot name at the top and select Open Kudu Console:
this will open the diagnostic console in a new tab. Enter cd site\wwwroot && build.cmd
Hopefully that works!
I'm trying to get a pre-build event setup in visual studio 2012 for compressing my Durandaljs app using Gulp. After much frustration with the pre/post build command line I have it working if I build the project. It runs node/gulp as expected.
My issue now is when I goto publish my project using the publish dialog (web deploy) the command fails with "exited with code 255." along with first alerting "Server was unexpected at this time." I'm having trouble finding much information on this error combination and I don't know what else to try.
if $(ConfigurationName) == Release (
"C:\Program Files\nodejs\node.exe" "$(ProjectDir)node_modules\gulp\bin\gulp.js" --gulpfile "$(ProjectDir)gulpfile.js" --cwd "$(SolutionDir)ProjectName" --no-color durandal
)
Edit: I've reduced the issue down further. It has nothing to do with Gulp, rather it is something with node running from the build command line. I am running a simple helloworld.js file piped into node and it is the same behavior. It works fine on build, however, on publish it gives the same errors.