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.
Related
New to Azure : I am using azure free service to host react website using vs code extension Azure App Service.
While deploying I am getting following error with no specific details
Using Node version:
v14.18.3
Using Npm version:
6.14.15
Running 'npm install --unsafe-perm'...
> react-scripts build
Creating an optimized production build...
An unknown error has occurred. Check the diagnostic log for details.
Deployment failed.
Inside Azure All Service :- microsoft.alertsmanagement/smartdetectoralertrules
Failure Anomalies notifies you of an unusual rise in the rate of failed HTTP requests or dependency calls.
Steps to reproduce
First deployment worked for me
After adding new dependancy in package.json it is not working (previously worked adding same dependancy)
Adding new png assets to project is failed, every time reason is different of failing
Trials to solve
Deleted projects and re created
Updated project dependancy
New project created but its fails after some changes to project
Please help to solve this problem
My NPM install step is configured to use registries in .npmrc,
My .npmrc is as follows
registry=https://pkgs.dev.azure.com/xxx/xxxx-xxxx-xxxx/_packaging/design-system/npm/registry/
always-auth=true
The Azure Artifacts feed is set-up, and a local npm install from my dev machine works completely fine.
However the pipeline's npm install job always fails with error 403.
What am I doing wrong here? I've also tried changing the npm install task to use Registry I select here, and linking it to my "design-system" feed directly, but it results in the same error. I've followed all the steps here https://learn.microsoft.com/en-us/azure/devops/artifacts/npm/npmrc?view=azure-devops&tabs=windows, but it just doesn't work. Thanks
Problem solved. What I had to do was go under into the feed -> settings -> permissions, and add the ...Build Service... as a Contributor.
Microsoft should really add this as part of their documentation. Took me several hours of random attempts before I found it..
This is a different solution for the same message, although, in this case it will fail from any location.
Trying to publish a package version previous to the last one published on the feed will return the 403 Forbidden error to, even if it's not a permissions issue.
Updating the package version to one increment after the current version will solve the problem.
My jhipster project was working fine before. Past two days it is acting funny. There is some version changes causing these issues.
Initially I got the following error in console, when I tried navigating to different page :
NavigationError(id: 2, url: '/ext-task-group-list', error:
InvalidCharacterError: String contains an invalid character)
In an effort to try to fix this problem, I ran
jphister upgrade
the upgrade is successful. However, mvnw command is not starting the server. Instead it is compiling the project and comes out successfully.
Couldnt find any resource in the net.
Anyone have fix for these two issues, pls share.
Start by doing a mvnw -X to see all the debug errors. That will give you more detail that you can go by
Some time my project in MyEclipse show me the following error on compilation. Sometime by restarting MyEclipse the error message disappear.
Can you please tell me why this error occurs ?
Error message :
The container 'Struts 1.1 Libraries' references non existing library 'C:\MyEclipse\.......\org.eclipse.osgi\bundles\16\1\.cp\data\1.1\lib\commons-beanutils.jar' ROMO_ETD Build path Build Path Problem
Thanks a lot.
Looks like you might be using an old unsupported release of MyEclipse, so one option would be to upgrade to the latest release. Another would be to run MyEclipse with the -clean argument, once. The argument is mentioned here (for the eclipse Juno release, but it's similar for earlier releases): http://help.eclipse.org/juno/topic/org.eclipse.platform.doc.user/tasks/running_eclipse.htm?cp=0_3_0
Basically, the argument is added to the command line or to the top of the myeclipse.ini file, in the folder containing the myeclipse.exe file. The argument can be removed after the first launch, as it slows down the launch.
I created a new Windows Universal App. I get the following error when I run it. What should I do to fix this error?
Severity Code Description Project File Line
Error Error : DEP0700 : Registration of the app failed. error 0x80080204: App manifest validation error: The document root element m:Package must be defined in the http://schemas.microsoft.com/appx/2010/manifest namespace. (0x80080204) App1
It should be the same issue mentioned in Can't build JavaScript universal Windows app
But I will suggest you make your windows 10 and VS 2015 up to date, since above question was asked about 1 month ago.
To find following steps to solve the Error/problem.
1) Close visual studio and simulator .
2)Then go to My Computer--C:\Users\EliteBook\AppData\Local\Packages----
where EditBook is your PC Name
3)delete all folder/files included in the Packages folder, try again to clean and rebuild Solution.
Also find following link for that:-
https://msdn.microsoft.com/en-us/library/windows/desktop/hh973484%28v=vs.85%29.aspx?f=255&MSPPError=-2147217396
https://msdn.microsoft.com/en-us/library/windows/desktop/jj835835(v=vs.85).aspx