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
Related
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 am facing PhaseScriptExecution error
when i try to build IOS then project not build this give the following error
the following build commands failed:
PhaseScriptExecution Bundle\ React\ Native\ code\ and\ images /Users/ali/Library/Developer/Xcode/DerivedData/NassauTennisMobileApp-akwowvjtagvlxbalhbsvukoitagy/Build/Intermediates.noindex/NassauTennisMobileApp.build/Debug-iphonesimulator/NassauTennisMobileApp.build/Script-00DD1BFF1BD5951E006B06BC.sh
For me: It seems that react native doesn't like spaces in the directory. I was able to build my ios after removing all of the spaces in my directory.
Potential solution to your problem, didn't fix mine but it might help you: The author suggests there is a mismatch between the node version that you're using and the one that xcode is calling/using. The author provides a way to check the versions installed as well as a way to symlink between the two versions => https://dev.to/glocore/react-native-command-phasescriptexecution-failed-of9
I'm working on updating my project from using electron version 1.2.5
to the newest electron at this time which is 1.7.7 (atleast it was when I downloaded it). My node version 6.9.1.
I've encountered a problem when I start my project with this new electron version,
the error in general is about "could not locate the binding files. and it mostly regards the async module.
There is also some part of the exception regarding node-etcd module which I use in my project (version 5.0.3)
I found some information about this type of exception online but most of them says stuffs about rebuilding some node module using some npm commands which I didn't quiet understand. I tried to install async module again in a new folder and replace it (with its deps) in the node modules folder im currently using for my project, but I still got the same error.
I'm working in an offline enviorment where I can't take my project "out" to a computer with internet access, I can only bring things from the web to my project (like installing in some folder and then copying that into my project) so any npm or other commands that require web connection are not available to me directly on my work computer. (I can only use them in a different computer and copy the results to a flash drive and bring them to th
Here's 2 pictures of the error (sorry about the quality, its the best I could get):
First part of error
Second part of error
The solution that fixed the problem in my case was going into node_modules - > deasync - > index.js
Before line 31 I added a newline (next to the binding line)
and wrote:
modPath = __dirname;
This solution is hacky, it was accually ly found by an associate a while back, so I am not sure why it works, it might be an issue in deasync, but it fixed the problem.
Trying to learn nodejs following a few articles. I'm able to download and make sure its working using a video from youtube. But now I'm trying to incorporate that in Visual Studio .net 4.5.2. I've tried to added it via new get package manager and the PM console each come back to same error.
"Install-Package: The specified path, file or both are to long. Less than 260 and directory name less than 248" Self explanatory, found this article
So I tried:
npm-flatten
npm-dedupe
also Enable Win32 long paths
It starts adding package npm 3.5.2 files and folders then bombs out and spits the same error. What else am I missing in order to get this package installed?
Thanks for any help
I am going to create the app that shows google map and required social login with facebook.
I decided to use:
https://github.com/Wizcorp/phonegap-facebook-plugin
and
https://github.com/wf9a5m75/phonegap-googlemaps-plugin
I don't know what is a reason, but these plugins perfectly work alone, but when I installed them together I got next error:
BUILD FAILED
C:\Users\{USER_NAME}\AppData\Local\Android\sdk\tools\ant\build.xml:577: Jar mismatch! Fix your dependencies
Total time: 1 second
{APP_PATH}\platforms\android\cordova\node_modules\q\q.js: 126
throw e;
^
Error code 1 for command: cmd with args: /s /c "ant debug -f {APP_PATH}\platforms\android\build.xml -Dout.dir=ant-build -Dgen.absolute.dir=ant-gen"
ERROR running one or more of the platforms: Error: {APP_PATH}\platforms\android\cordova\run.bat: Command failed with exit code 8
You may not have the required environment or OS to run this project
I am not experienced in PhoneGap development, but I guess that both plugins are doing some changes in platform dependencies (and rewriting changes of another plugin).
Could anybody help me with this?
I got the answer of google-maps plugin creator:
The facebook plugin contains android-support-v4.jar, and the map
plugin installs another android-support-v4.jar.
Remove one of them.
I took off android-support-v4.jar from com.phonegap.plugins.facebookconnect folder and left it in libs folder. It was solved my issue (fb and g-maps work together).
So I can mark this question as closed now.
I leave this answer for anybody who meets this issue like me.