Windows 10: Microsoft announces release of Project Reunion 0.5

Brink · Mar 29, 2021

Today is an exciting day â the release of Project Reunion 0.5 is the starting point for your ability to build and ship Windows apps at a much faster pace without waiting for the Windows OS to update with new features. In 0.5, our focus is very much on what weâve heard from our developer community around making Desktop apps easy to build again. Thatâs why youâll find downâlevel support to Windows 10 version 1809, the ability to use Project Reunion with a .NET 5 app, as well as WinUI 3 and WebView2 for modern, compatible UI development â all with production level support when using packaged apps! Project Reunion 0.5 is one of many important steps weâll have on our journey to 1.0 this year and we canât wait to work with all of you.

What does it mean to ship with Project Reunion?

When you build an app that uses Project Reunion, you get access to modern Windows technologies and new features, plus the best of existing Desktop (aka Win32) features. You will also be able to incrementally adopt these technologies and at a much faster pace since they are decoupled from the OS â thatâs a big deal! Youâve told us that typically you have to wait for your users to update to the latest Windows OS before you can consider adopting the latest features and integrating them into your app. For some of you that could mean a 1-2 year delay in a new feature being available, you being able to adopt it, and users seeing it in apps. Now, you can take the latest Project Reunion release whenever you want to get the latest features and can feel confident that theyâll work for all your users on Windows 10 version 1809 â which is the current Enterprise LTSC â and newer.

In the 0.5 release, these features include MRTCore and DWriteCore â first shipped in our 0.1 preview release â but now with updates and full support. In addition, the 0.5 release brings the muchâanticipated production version of WinUI 3 for Desktop apps, which also includes the WebView2 control.

The features we are releasing today ship as part of the Project Reunion framework package. You can think of this framework package as how we bring together all the parts of the Project Reunion family â like WinUI 3 for example, which is not directly in the Project Reunion GitHub repo â into one place for developers to use seamlessly.

When building an app with Project Reunion, youâll start by downloading the Project Reunion Visual Studio Extension (VSIX). This provides WinUI 3 project and item templates and sets up your app to reference the Project Reunion package and any needed dependencies. Once youâve created your new project, youâre back in the Windows development zone youâre used to.

Whatâs supported in Project Reunion 0.5

Project Reunion 0.5 supports packaged apps, which uses MSIX as a deployment method. We know there is a lot of demand for unpackaged support as well, and we have that on the roadmap for preview releases that will be coming soon.
The most notable inclusion for the Project Reunion 0.5 release is WinUI 3, which is the dramatic expansion of the WinUI 2 controls library into a full-fledged, end-to-end, standalone UX framework. If youâre not already familiar with WinUI, you can learn all about it in our Overview documentation, along with our website.

The version of WinUI 3 thatâs shipping with this release is the first version thatâs suitable for production apps and is forward-compatible. With WinUI 3, you can now build Desktop apps that can be published to the Microsoft Store. There are currently two supported methods for creating a WinUI 3 app:

Creating a brand new WinUI 3 Desktop app from scratch

Migrating your existing Desktop apps to WinUI 3 by adding a new WinUI 3 project to your solution, and adjusting or refactoring your logic

Keep in mind that some of you may currently be using the WinUI 3 â Project Reunion 0.5 Preview, which has several additional features including support for building WinUI 3 UWP apps, and multi-window support in Desktop apps. You wonât be able to use these preview features or call any of their associated APIs in this new, stable version of WinUI 3. If youâd like to experiment with these features, you can still continue to use that preview release by staying with the preview VSIX. And, coming soon, you can use our 0.8 preview release as weâll have release and preview builds side by side.

The team aims to put out regular previews (in between and alongside stable releases) for those of you who would like to be on the very cutting edge of our progress. Preview features will continuously be stabilized to ship as a part of future stable releases.

How to use Project Reunion 0.5

To start using Project Reunion, see Get started with Project Reunion to set up your development environment and learn more about the components included in this release. If youâre just looking for info on building a WinUI 3 app, start with the WinUI Overview and release notes article. Once youâre set up to start building your WinUI 3 app, take a look at our docs on Get started for WinUI 3 with Desktop apps and Building a basic WinUI 3 Desktop app.

If you find issues specific to developing with WinUI 3, please file an issue on the WinUI repo â and if you find any issues with other parts of Project Reunion 0.5, please file an issue on the Project Reunion repo â your feedback is incredibly valuable to us.

A growing ecosystem

Weâre excited that the following ecosystem technologies are either already supporting or working on supporting Project Reunion 0.5. These technologies provide unique features and controls to supplement WinUI 3, and you can read more about each of them below.

Actipro Software is migrating their vast UI control offerings over to WinUI 3, including their SyntaxEditor code editor, propertygrid, native type edit boxes, docking/MDI, charts, and more.

DevExpress: DevExpress has released 20 new WinUI controls with Project Reunion 0.5 support, including the Data Grid, Scheduler, Charts, Ribbon Toolbar, and more. All 20 UI components are available free-of-charge.

GrapeCity plans to bring their popular desktop UI controls to WinUI later this year! Learn more about their data connection service components for WinUI.

Infragistics: Ultimate UI for WinUI brings business critical, high performing, and feature rich line of business controls to your apps that target any platform that runs Windows (including Windows on ARM64).

Syncfusion: Updated their projects to Microsoft.ProjectReunion from Microsoft.WinUI following upgrade instructions. All their controls are working fine.

Telerik UI for WinUI: the market first UI controls suite for crafting Win32 and UWP apps with WinUI 3, comes with feature-rich controls like Ribbon, DataGrid, Charts, Gauges, Barcode, and more.

Uno Platform: Use WinUI 3 â Reunion 0.5, XAML and C# to build pixel-perfect, single-codebase, native applications that can run on Web, Desktop and Mobile. It is free, open-source and available today.

Windows Community Toolkit (Microsoft): The WCT is currently working on supporting Project Reunion 0.5 in the near future. It provides tons of new controls and capabilities for use in your WinUI app. Check out their open source repo here.

Whatâs next

Throughout the rest of this calendar year, more technologies will be coming to Project Reunion, such as: App Lifecycle for improved system performance and battery life, a modern Windowing system that combines the power of Win32 windowing with the ease of UWP, notifications support for both local and push scenarios, unpackaged app support and much more.

In the near term, we plan to release Project Reunion 0.8 in the next few months and Project Reunion 1.0 later this year, with a series of preview releases that will ship alongside these stable releases. WinUI 3 and other highly requested features â so get your issues and specs filed on the repo! â will be updated in each of these releases. For more details, check out the Project Reunion feature roadmap.

Staying in the loop

You can stay up to date with the team on the WinUI GitHub repo and the Project Reunion GitHub repo, and through our monthly https://www.youtube.com/playlist?list=PLI_J2v67C23ZqsolUDaHoFkF1GKvGrttB, and coming soon our Project Reunion community calls, where we often share roadmap updates and other exciting news.

You can also connect with us on Twitter using #ProjectReunion and @WindowsUI!

We look forward to seeing the beautiful apps you create with Project Reunion 0.5 & WinUI 3!

Andrew Clinick on behalf of the Project Reunion Team
Click to expand...

Source: https://blogs.windows.com/windowsdev...t-reunion-0-5/

Tweet

— Twitter API (@user) View on Twitter
Click to expand...

:)

Brink · Mar 29, 2021

Microsoft explains what is Project Reunion to fix Win32 and UWP apps

What is Project Reunion?

Project Reunion is a set of libraries, frameworks, components, and tools that you can use in your apps to access powerful Windows platform functionality from all kinds of apps on many versions of Windows. Project Reunion combines the powers of Win32 native applications alongside modern API usage techniques, so your apps light up everywhere your users are.

Your app can use the parts of Project Reunion that are most interesting to you without having to rewrite it into a new app model or deployment system. Project Reunion provides a single consistent API surface for both new and existing functionality that automatically adapts to your preferred app model and deployment mechanism. Project Reunion helps you move towards a modern API and app style without requiring you to make a hard choice to rewrite it or re-implement it across versions of Windows.

This repo contains the Project Reunion components that are common for all applications. Look for the "Project Reunion Family" badge in other repos showing that their code is using Project Reunion techniques and tooling. Your own components can be part of the "Project Reunion Family" by following the same principles and practices as Project Reunion itself – support all forms of apps with a single API surface and meet developers where they are with the tools they need to build great apps on Windows.

Using Project Reunion will be as simple as adding a reference to our NuGet packages in your build.

What Project Reunion Brings

Project Reunion functionality comes in three main categories – new APIs, converged APIs, and API subsets. Your apps can pick up each different level of functionality at your own pace.

New APIs

Whenever possible, new Windows functionality will be delivered as part of the Project Reunion Family. APIs and functionality delivered as "New" are identity-, packaging-, and isolation- transparent to your application. New functionality will share a common interface for you to use whether your app is MSIX, MSI, setup.exe, Desktop Bridge, or AppContainer.

Some of the APIs and functionality listed will come over time; they are listed as examples of the category rather than fully supported on day 1.

These APIs are self-consistent and solve specific application problems or help you build additional functionality into your application. Potential categories of APIs here might be:

Application data storage and management to keep your data in one place and the user's system tidy

Cloud app support for identity and connectivity management to use the power of Azure

Packaging and system integration so Windows understands what your app is doing

App-to-app inter-process communication helpers so your apps can work with other app easily

Privacy-aware resource access APIs for camera, microphone, location, and more

You'll start using these APIs by adding a reference to the Project Reunion NuGet package and then adding uses of the APIs in your app code. Use as much or as little of Project Reunion as helps your application. New Project Reunion APIs will be available on all supported versions of Windows and for all apps. Where certain APIs behave differently (such as due to identity, isolation, or lifecycle differences) your app can detect it with clear "TheType.IsSupported" checks.

Converged APIs

Project Reunion provides API surfaces that bridge the gap between Win32 and UWP/AppContainer functionality already within the platform. Authors of shared code (like frameworks) can use a single method and avoid their own "if (AppContainer) { x } else { y }" checks.

Project Reunion APIs provide "polyfill" implementations of APIs when necessary so your app can run on more versions of Windows without additional "is this Windows 10 Creator's Release?" checks.

Converged API documentation also includes ways to find uses of the "un converged" code in your project, along with guidance on how to move from common code patterns to the new Project Reunion converged APIs. Examples of converged APIs include:

Window Content Frame abstraction over Win32 and UWP windowing

Application lifecycle behaviors like start, logoff, restart manager integration, restart-for-update

Startup and Background Task support to reduce your app's power and performance footprint

Application resource management for strings, images, display resolutions, and locales

Advanced clipboard access

Once your app adds a reference to the Project Reunion codebase your app can start migrating blocks of functionality to using these fully-supported converged APIs. You can move as much of your application to Project Reunion functionality as necessary, keeping your existing application style and behaviors. Whenever possible these APIs will be similar to their existing Windows SDK namespaced APIs, easing the transition to Project Reunion for your existing code. For existing "flat C" Win32 APIs, an equivalent converged API will be added and then projected to your language and runtime. If you prefer a "flat C" style – or the APIs you want already have a "flat C" expression – we're working on building out a projection of those APIs for you.

As your app migrates to Project Reunion functionality it'll be easier to move between deployment and isolation technologies. Project Reunion handles the brokering of resource access from a low integrity-level (low-IL) or AppContainer process so your app can reference user resources while respecting user choice & privacy controls.

Subset API Family

Project Reunion helps you stay within the set of APIs that Windows supports on all editions and all endpoints. Like the Windows Kit API partitions, Project Reunion defines a subset of supported Windows Platform APIs that work across all versions of Windows. If your code targets this subset - and uses Project Reunion New + Project Reunion Converged functionality whenever possible - it'll work everywhere Windows works, without needing additional support work.

Project Reunion Subset APIs for your apps also let you start using Project Reunion's functionality with minimal changes to your existing code by using an updated and streamlined set of headers and implementations. Feature areas supported by the Project Reunion Subset include subsets of:

Windowing, Input, Messaging, GDI, and GUI subsystem functionality

Filesystem and storage access

Networking

Printing

Process, threading, memory management, basic application services

DirectX, D3D, DirectML

Migrate your app to the Project Reunion Subset API set by first removing all references to Windows Kit headers (windows.h, kernel32.lib, user32.lib, winsock.h, etc) and then adding references to the core Project Reunion Subset header and import libraries.

While many existing Windows Kit APIs are part of the Project Reunion Subset, you may have some minimal changes to make to your application's code or behavior. Recompile & relink your application then ship it with our support packages.

Is this "subset" model interesting for you and your apps? This feature of Project Reunion is still in planning for a future release. Let us know by filing an issue with the "subset" tag on it and list the APIs and functionality you'd like to see.

Project Reunion Family Components

Available Now

These components are available for you to use now and adhere to the "Project Reunion Family Promise" that they have a single API for use in all kinds of applications.

WinUI 3 for XAML helps you build fluent UX for all kinds of applications with the power of XAML. This component {link to repo} is part of the Project Reunion Family of functionality, building on the identity + packaging + deployment transparent ideas that Project Reunion supports for your app as well.

C++/WinRT, RUST/WinRT, and C#/WinRT provide language-native projections of Windows, Project Reunion, and your own custom types defined in metadata. Consume APIs from the Windows Kit, produce them for use by other supported projections, and create your own new language projections.

MSIX-Core lets you package your application for distribution to Windows Desktop machines via the store or your own delivery pipeline. MSIX-Core lets you use the reuse parts of the MSIX packaging story on older versions of Windows.

Coming Soon

While we think these are interesting for applications, you tell us! Part of working in the open is that we learn together about the needs of application developers. Below are a set of functionality that seems interesting to make available through a Converged or New model, but you tell us! Some are linked to an issue thread proposing the functionality. +1 the ones you like, comment on the detailed design & direction, and help us shape where we're going.

Edge/Chromium backed WebView2 brings the ease of authoring your app in HTML+JS once and reusing it on all platforms. WebView2's use of Project Reunion technologies like WinUI3 as a hosting frame lets you run modern web-based UX on all editions of Windows.

Modern Lifecycle helpers help your app be power-sensitive and reactive to changes in the runtime system's power management and user state. They also help your app restart after the user reboots, register your app so it can be restarted, and reduce update-related reboots.

Startup Tasks make your app come alive as the user logs in to reconnect, start working while not over-using resources, or be ready for fast use. User choice and power management features let you reduce your impact on the critical logon path.

Update Scan Integration help keep your app up to date automatically while running at the same time as other system maintenance tasks are happening.

Access to user resources even from AppContainer and isolated applications. Your AppContainer apps can access powerful Win32 technologies like the clipboard, inter-process communication, and the Windows Shell Namespace with user consent through brokering.

Modern Resource Tooling so you can use the power of ResX/ResW in your Win32 applications instead of MUI.

Future Direction

We aim to grow Project Reunion to provide a modern, simple, and accessible version of much of the power of the Windows Application Platform. Working in the open with our development community ensures we're doing the right things first to solve problems your apps are facing on current and future versions of Windows.

Some functionality will be delivered first as Project Reunion components. As we think about evolving the platform it's important to make sure new functionality & features are available to our developer community just as soon as they're ready to go. Where there's newer in-platform functionality to use Project Reunion will help you adopt that as soon as it's widely available, without you having to retarget or rewrite – the same Project Reunion API surface will continue to work.

As your app uses more Project Reunion functionality it'll be ready for additional targets such as packaging, identity, AppContainer, and other future Windows Editions. Depending on Project Reunion APIs means we take on the work to keep these APIs working as Windows evolves forward. Staying within the Project Reunion API surface ensures your app can address the widest range of Windows editions and releases while using up-to-date functionality.

How we are doing this

Working in the open

Project Reunion relies on the power of open-source and the features of GitHub to deliver code to you as fast as we can dream it up. You should feel free to fork, create pull requests, open issues, propose resolutions to issues. You can see and influence all our features via the issue tracker. You should expect that we listen and provide constructive feedback.

Build & Artifacts

Code within the Project Reunion GitHub repo builds on a CI/CD loop and produces freshly built DLLs and metadata on each pull request. The output includes a NuGet package containing metadata for Project Reunion and a ready-to-deliver MSIX for inclusion in your application as a redistributable or as a package reference. Add a reference to the Project Reunion package and start building. To help deploy your apps we'll include both a Framework Package MSIX as well as instructions on how to deploy that MSIX from your existing installer.

Versioning

Project Reunion will use strongly-typed metadata-based API definitions on which your apps can take a long-term dependency following our published support lifecycle. We'll use SemVer 2 to clearly identify breaking API shape levels that let those APIs evolve forward towards new functionality while not compromising existing apps. Project Reunion helps keep apps up to date through Framework Packages that are updated with non-breaking changes as appropriate.

Extending APIs

Some of what Project Reunion provides is access to functionality that is inside Windows, but for which there is no public API. We're working on the details, but our plan is to deliver a secondary package of code that provides a public API over those previously unexposed components. While those components will be implemented as closed-source they'll come with a metadata-based publicly callable & supported API surface and be included in the Project Reunion framework packages for use by apps.

Brokering

UWPs (AppContainer, Low-IL) processes are meant to protect both the user and the application itself from other applications. Access to user & system resources is limited to the supported set of brokers for those resources. Project Reunion also includes a main package that runs at the user's integrity level (medium-IL, sometimes called "full trust") and can provide user-approved access to resources previously unavailable to AppContainer and low-IL processes.

This pattern is available to AppContainer apps today as a "full trust component" - Project Reunion aims to provide a common pattern & platform for these custom components.

What Project Reunion isn't

Project Reunion isn't a new application model or platform from Windows. There won't be a "new Project Reunion App" template for Visual Studio, VSCode, or other development environments.

You'll still have full access to the Windows SDK and associated kits. Over time the features that Project Reunion provides will grow beyond just merging the existing Win32 and UWP models and provide additional functionality for all apps to use.

Project Reunion isn't a new packaging or isolation model for applications. There won't be required changes to your application in order to access Project Reunion functionality other than using the new functionality itself. If the APIs you use need identity or packaging these requirements will be indicated.

Project Reunion isn't a new security or privacy model for applications. Your app's existing security, privacy, reliability, and identity stories continue to work with Project Reunion. There may be places that Project Reunion helps your app be more aware of customer security or privacy concerns. Project Reunion helps you use modern security & privacy functionality that evolves alongside your application's needs.

Project Reunion isn't a way to run your app in the cloud. Using Project Reunion technology will help get your app on modern API families that are cloud ready. Key components like modern lifecycle and state isolation help get your app ready to run wherever your customers are.

More Documentation

High level overview - Why we're doing this.

Roadmap - Where we're going. We're following a roadmap that gets us to building a first version of Project Reunion exploring some basic common features. You can help by filing issues for features you'd like to see!

Contributor guide - How to contribute to Project Reunion.

FAQ - frequently asked questions about Project Reunion.

Click to expand...

Source: https://github.com/microsoft/Project...docs/README.md

Brink · Mar 29, 2021

Announcing Project Rome SDK for Android and iOS version 1.0

We are pleased to announce the version 1.0 availability for the Project Rome SDK for Android and iOS.

Project Rome is a platform for enabling seamless cross-device and cross-platform experiences. The philosophy behind Project Rome is simple. App experiences shouldn’t be tied to a single device any more than data should be tied to a single device. Your apps, like your data, should travel with you.

Getting started

Here is a link to the Project Rome documentation to get started with the SDK.

Learn more about Project Rome

Documentation & API Reference

iOS/Android Samples

Click to expand...

Source: Announcing Project Rome SDK for Android and iOS version 1.0! - Windows Developer Blog

Tweet

— Twitter API (@User) View on Twiiter

Brink · Mar 29, 2021

Announcing Project Rome SDK for Android and iOS version 1.0

We are pleased to announce the version 1.0 availability for the Project Rome SDK for Android and iOS.

Project Rome is a platform for enabling seamless cross-device and cross-platform experiences. The philosophy behind Project Rome is simple. App experiences shouldn’t be tied to a single device any more than data should be tied to a single device. Your apps, like your data, should travel with you.

Getting started

Here is a link to the Project Rome documentation to get started with the SDK.

Learn more about Project Rome

Documentation & API Reference

iOS/Android Samples

Click to expand...

Source: Announcing Project Rome SDK for Android and iOS version 1.0! - Windows Developer Blog

Tweet

— Twitter API (@user) View on Twiiter
Click to expand...

Windows 10: Microsoft announces release of Project Reunion 0.5

Microsoft announces release of Project Reunion 0.5

Microsoft announces release of Project Reunion 0.5

Microsoft announces release of Project Reunion 0.5

Microsoft announces release of Project Reunion 0.5 - Similar Threads - Microsoft announces release

Windows 10 could see big changes with Project Reunion

Announcing Project and Roadmap apps for Microsoft Teams

Microsoft explains what is Project Reunion to fix Win32 and UWP apps

Microsoft wants to unify UWP and Win32 with Project Reunion

Microsoft announces generally available release of PowerShell 7.0

Microsoft announces official release of Babylon.js 4.1

Project xCloud game streaming service announced by Microsoft

Announcing Project Rome iOS SDK

Announcing Project Rome Android SDK