I'm trying out the new .NET MAUI Blazor App template that comes with VS 2022 17.2.0 Preview 2.0. The app runs fine when debugging, but when I try to publish the app to a folder, specifying net6.0-windows10.0.19041 as the target framework and win-x64 as the target runtime, I'm getting "Publish has encountered an error. We were unable to determine the cause of the error", and in the output window: "The RuntimeIdentifier 'win-x64' is invalid". Anyone else experiencing this, or is it just me?
I'm having the same issue. It looks like a bug in the preview.
See here for more details. https://github.com/dotnet/maui/issues/3493
Related
I try to upload my Windows Phone 8.1 app updated package (.appxupload) to the Windows Store and it tells me
"This submission failed with error code(s) 2001. More info about the error(s) can be found here." with a reference to this page: https://msdn.microsoft.com/en-us/windows/uwp/publish/resolve-submission-errors
I can sucessfully build and deploy my app with Visual Studio in both release and debug mode, and also pass the certification, but the Store stops me. Any ideas?
We had similar problem. The problem was finally solved by the following steps:
Clean the project
Rebuild the project
Upload *.appxupload manually via website from YOUR_APP/AppPackages instead of .appx from bin/ARM/Master
Hope this will help. If not, there is a similar topic on MSDN.
I am just starting learning "Build 2D games with HTML5" from MVA and in starting i had a problem to configure my visual studio
Here is the link of that package Cordova-Windows package
The instructor shows that the Cordova windows package 3.5.0 contains CreateTemplates.bat file but it didn't work for me
i came up with this problem i dont know how to overcome this,
when i clicked the createTemplates.bat file its popup and off nothing happends so i try to open it up using command prompt and i get this errors , How to overcome?
what should i do now , your help would be highly appreciable !
You should use be using the Cordova CLI for your command line workflow for building Cordova Apps. For Cordova, more information is available here. If you want to use VS, then I strongly urge you to install our VS 2015 RC build which enables you to build Cordova applications for iOS, Android and Windows. More information for VS, is available here.
I am developing an as3 application intended to be published with AIR.
I use the 4.6 version of Flex SDK with the flash builder plugin for eclipse.
I can launch/debug my app via eclipse without any problems. I export a valid version of the app and get my air installer. When I install and launch my app, I get a blank screen...
I don't know how to debug this. It seems that I miss something in the publication configuration but I don't know what.
I have been searching the web for hours and didn't find any solution, hope somebody can help me here !
Thanks for any help.
It simply was a real as3 error that didn't show up on debug mode...
When allowing the debug mode on the AIR application I learned that the property mouseChildren cannot be set on SimpleButton.
I got the same problem with my app and I finally found a way to display the error in the package app:
You just have to add a file named debug into your app/META-INF/AIR folder.
For detailed information see Adobe Cookbook.
Having a very strange issue on an inherited project. The developer who built the project (using fb 4.0 and flex 3.0.0.477) is able to compile it and the application works just fine, both locally and on the server. However, if I take the identical code and compile it using fb 4.6 and the same flex sdk, the application works locally, but starts failing to load modules on the server, giving a "SWF is not a loadable module" error. There are no other errors from the debug sessions.
All crossdomain policy files appear to be in place. The module even begins loading, but receives the error after 5 - 10% downloaded.
I also tried setting the application domain using modLoader.applicationDomain = ApplicationDomain.currentDomain;, with no results.
Thanks!
So after long hours of troubleshooting, it turns out that the main application widget was being loaded over https, while the modules were being referenced at http. I guess flash builder 4.6 enforces stricter security settings. I now reference both the widget and the modules at https, and the application is working again.
Thanks, Shaun, for the help!
I have downloaded the javafx 2 samples and want to run in from its HMTL. For example there is one javafx application called BrickBreaker. For the specific sample the following files exist : BrickBreaker.jar, BrickBreaker.jnlp and BrickBreaker.html
When double clicking on jar or jnlp the application runs as expected but when i click on the html the application does not run. Instead i get the message "View the conectes of the page. Please install javaFX"
Why is that happening ? ( i have the javafx installed as the application runs when choosing the jar and jnlp files). My guess is that the html should be called from within the context of a webserver meaning that i should deploy my application first to a server and call the url from my explorer. For example if using glassfish i should call the url http://localhost:8080/Brickbraker
The problem is that i don't know how to deploy the javafx application in the server.
i tried to copy paste all the above three files in the autodeploy folder but it didnt worked...
Could you please help me?
Thanks in advance
EDIT: some more info - I have installed JDK 7 and JavaFX SDK 2.0.2
No, JavaFX is client technology, you don't need Glassfish to run it. JavaFX should run in browser the same way as Java plugins do.
If you can't run an application directly from html file it means your browser doesn't recognize you have runtime installed.
There can be next reasons for that:
JavaFX runtime is actually not installed (check in Windows Control Panel)
pure java plugin is not installed (you can check on java.com)
javafx runtime is 32bit and you are using 64bit browser (or vice versa)
you are using not supported browser (e.g. Safari)
you are using not supported system (at this moment, January 2012, only Windows supports runtime)