Desktop Bridge: best practices and common issues

This post has been written by the TAppEx and CMCO teams, in collaboration with Windows AppConsult Below are common Desktop Bridge Microsoft Store Policy failures. By familiarizing yourself with these policies and making any necessary changes to your app, you can help ensure that your app gets into the Store in a timely manner.  We’ve…

0

Handling Visual C++ dependencies in a Desktop Bridge app in the Fall Creators Update

One of the requirements for packaging a desktop application with the Desktop Bridge is to embed inside the package all the required dependencies (libraries, frameworks, etc.) which are required by the app to run. The main goals are to provide a seamless user experience (the app should work out of the box once downloaded from…

0

Preparing a Desktop Bridge application for the Store submission

If you follow this blog regularly, you’ll know that currently the submissions of Desktop Bridge apps on the Store requires an extra vetting other than the standard certification process. Desktop Bridge applications, in fact, make use of a special capability called runFullTrust, which is restricted. If you try to submit an application that declares it…

0

Chaining multiple installers with the Desktop App Converter

One of the key requirements of an app package deployed from the Store is that it must be self-contained: the application must run without asking to the user to manually install a set of libraries, a framework or a runtime. If this requirement is easy to satisfy with a regular UWP application, since they fully…

6

Package a .NET desktop application using the Desktop Bridge and Visual Studio Preview

09/04/2017: post updated to include a reference to desktop applications developed with C++, since CPP projects are supported as well by the Desktop Bridge Packaging Project. In one of the previous posts I’ve written on this blog we’ve seen how, thanks to a combination of a JavaScript project for the Universal Windows Platform and a…

7

Unpackage, modify, repackage, sign an APPX

Desktop Bridge
Desktop Bridge

If you are working on a desktop application that you want to release on the Windows Store by packaging it with the Desktop Bridge, you’ll know that one of the requirements is that your application should work fine also on Windows 10 S, the new Windows edition that was introduced on 2nd May 2017. We…

0

Desktop App Converter fails on Windows 10 15063.483 and later: how to solve it

Update on 04/12/2017: the image BaseImage-15063-UPDATE.wim has been deprecated. If you’re using the Fall Creators Update and you need to setup the Desktop App Converter, you just have to download the standard image for build 15063 from the following website: https://www.microsoft.com/en-us/software-download/dac If you’re working with the Desktop Bridge and, as a good practice, you always keep your Windows…

2

Accessing to the files in the installation folder in a Desktop Bridge application

We already had the chance to discuss this scenario previously on this blog, specifically when we have talked about the option to include multiple Win32 processes in the same app package or how to handle data in a converted desktop application. If you open the documentation with the guidelines on how to prepare a classic…

0

Porting and testing your classic desktop applications on Windows 10 S with the Desktop Bridge

On 2nd May Microsoft has announced Windows 10 S, a new Windows 10 edition (based on the same Creators Update version, which means build 15063) designed specifically for scenarios where the customer wants to put safety and security first above all when they use their devices. The main differences, in fact, compared to a standard…

1