Up until now we were working under the assumption that UWP would be similar to Windows Phone in terms of
authorization and build process. This doesn’t seem to be the case.

UWP requires a certificate file to authorize a build similarly to iOS/Android builds, this is probably a good thing
as it might mean that sideloading over the air might finally be supported on Windows devices.

This means we will need to make some changes to all IDE plugins and to the build.xml file in order to support the
UWP target, these changes will allow us to make the migration process much smoother and phase out the old
Windows phone target gradually. This also means the Windows section in the IDE will also include more options
such as the certificate required for UWP. We’ll keep you posted on this process as we setup the build servers
and get the IDE plugin updates out of the door.

This is probably the main question here and we still don’t have a final answer.

Until we start seeing builds going thru it’s hard to say what would work and what wouldn’t. We had a big issue with
iKVM this past week and needed help from Microsoft to resolve that (they were quite helpful here). We have
no way of knowing if this is the “last issue” we will run into. Setting up a Windows build server is the equivalent
of a root canal without the pleasant bits or anesthesia!

We literally had to get Microsoft tech support to help with basic things and are still struggling to get the build
tools to run there.

We hope to have a beta version out for developers before the 3.6 release which is currently slated to August. However,
this is a tentative date and until we actually see everything working for elaborate apps we won’t commit to anything.