Hi Thales 3D Team,
We were and are still focusing on mobile with our products. That's the simplest explanation why we don't support exporting to desktop/standalone. Although it would be technically possible, testing this as an additional supported platform would have brought a huge extra junk of QA tasks on our plate. That and the fact, that not many users asked for this feature in the first place, are an additional factor why we never supported standalone...
Hi Wikitude and Thales Team,
we also would prefer a Windows Standalone Build.
Our target device is a Windows Surface Tab.
And UWP really is a mess especially when the costumer is not allowed to activate developer mode in Windows 10.
To hide behind the "huge extra junk of QA Tasks" really should not be the argument in a professional team which want to sell products, right?
So please open the Windows Build as the Thales team said, it is running in Unity Editor. So it should not be a long way.
Thanks a lot.
While I totally agree with you, building for UWP adds some specific code to your app, as well as some issues with UWP from Wikitude :
However I can provide you a bit of help on the UWP build and deployment with your clients.
We are also building our application for Windows Surface Tab.
We purchased a code-signing certificate from a trusted public CA (digicert) and use it to sign the application when generating the application package from Visual Studio.
This way, you don't have to enable the "Developer mode" when installing the application on a Windows Surface and no warning will be triggered by Windows.
One of your customers uses the Microsoft Endpoint Configuration Manager as their application delivery platform. The Appx is imported direct and distributed to collection. MECM deals with the install.