Changing UWP export options #5364
sweethoneycode
started this conversation in
Platforms
Replies: 1 comment 3 replies
-
The UWP export gets very little maintenance, as Microsoft themselves is no essentially no longer caring about UWP. There are very few contributors who are knowledgable with UWP. Even then, most of them would rather spend their time improving the Win32 platform port which has far more users and has a brighter future. PS: It's "Godot", not "GADOT" 🙂 |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I have been looking into GADOT with the ability to export to UWP and it is very broken. It attempts to export to .appx format and tends to be empty. This is more or less due to the package manifest not formatted correctly. I am wondering if this is not the best approach.
Before trying GADOT I have been using Unity for over 10 years. It's UWP export takes a different approach. It packages a Visual Studio Solution for UWP and it does this with C++. It essentially packages it to have the current manifests and directories needed to build the correct files for Windows UWP format which is still needed for the Windows Store. (My games have high installs on this store).
Through Visual Studio the APP can be associated to the correct store listing or create a new one and more. Updates can be done to the app manifest without making an error in the XML. In short the heavy lifting of meeting the requirements for the Windows Store is handed off to Visual Studio which is available on Windows or MAC.
I understand this may not be a good option for Linux users, but with my experience with using Unity it just works overall.
I don't know what it would take to build such a solution for GADOT. However GADOT is easier to develop in and I would be able to transition to this fully if it were available.
Thanks!
Beta Was this translation helpful? Give feedback.
All reactions