Stefan Wick

I agree this is not a useful error message. I am reaching out to our XAML folks to get an update on what investments we are doing to make debugging XAML issues easier and how we can share these with the community. We are planning to do a more dedicated On .NET session about XAML & Fluent in UWP, so hopefully we can address these topics there as well. Thanks for the feedback!

@dhruval1984:this has been fixed

@sirsroger: the first demo has now been published

Please see my blog post: https://stefanwick.com/2017/05/24/my-build2017-session-recap-and-next-steps/

Here is the direct link to the code on GitHub: https://github.com/Microsoft/DesktopBridgeToUWP-Samples/tree/master/Samples/SQLServer

@pnp0a033: The manifest extensions that we have shown in the session are not available in the current Creators Update. If you are in the Windows Insider program you will start seeing some of them become available for you to test in the next couple of weeks. Once they are in an insider build we will publish samples on GitHub to help you get started. If you want to keep in touch on this topic, follow me on Twitter (@StefanWickDev) to see timely updates when things become available publicly.

Thanks,
Stefan Wick

Suspending apps when they get minimized is a good default for the overall system health. Apps that need to keep running when minimized can definitely change that behavior as documented here:

https://docs.microsoft.com/en-us/windows/uwp/launch-resume/run-minimized-with-extended-execution

We are not asking developers to abandon their WPF or other existing investments. In fact with the Desktop Bridge project we are enabling them to take advantage of the full power of Windows 10 with their existing code investments. They can keep their current code running without restrictions, packaged as a Universal Windows app package, and gradually take advantage of new UWP features at their own pace. They do get the best of both worlds.

Microsoft apps are taking the same path: some go straight to pure UWP (like OneNote or Paint), while others are doing the Desktop Bridge migration (like the full desktop versions of Word, Excel, Powerpoint).

As we have stated in the BUILD2017 session, we know that UWP is not complete yet, we have gaps to plug in order to support certain types of applications. We are making big steps forward in the Fall Creators Update by aligning with NET Standard 2.0 and by adding support for more Win32 APIs as well. There is more work happening beyond that and I would like to invite everyone to help with the prioritization by posting/voting on UserVoice:

https://wpdev.uservoice.com/forums/110705-universal-windows-platform/

Thanks,
Stefan Wick

We are doing some final cosmetic touches on the code and will get it out on GitHub shortly. It will go into our Desktop Bridge Samples repo here.

Note that there is already an older Northwind sample up there, but that's not the one we demo'ed at BUILD2017. It does use some of the same concepts in regards to the Desktop Bridge though.

Thanks,
Stefan Wick

@jmbrq: If your app doesn't have an installer, you can follow this example:

https://github.com/Microsoft/DesktopBridgeToUWP-Samples/tree/master/Samples/HelloWorldSample

To use this with the Visual Studio extension for debugging Desktop Bridge apps, create a new "Desktop to UWP Packaging" project in your solution and add the 'CentennialPackage' folder from the sample as your Package Layout.

Let me know if you have more questions about this.

Thanks,
Stefan Wick

@Jonny Yu: the Desktop Bridge can handle complex installers (MSI and other types of installers). Please be sure to read this topic which lists a number of caveats you should be aware of before starting your conversion:

https://msdn.microsoft.com/en-us/windows/uwp/porting/desktop-to-uwp-prepare

Thanks,
Stefan Wick

@xochl: We have a code samples for the desktop bridge on GitHub, and are in the process of adding more:

https://github.com/Microsoft/DesktopBridgeToUWP-Samples/

Thanks!
Stefan

Hi Mathias,

I can confirm there is a known bug with file access in certain network share scenarios. We are actively testing a fix for this. I will follow up with you in the MSDN forum shortly.

Thanks,
Stefan

For single-proc background activation we will make samples available to the public soon (incl. the trigger I demonstrated).

For extended execution, you can start playing with the API on current bits. There is a sample up on GitHub: https://github.com/Microsoft/Windows-universal-samples/tree/master/Samples/ExtendedExecution

Thanks,
Stefan