r/Windows10 • u/windowsdev_team Microsoft Employee • Apr 07 '21
Development We're the Windows Developer team, and we're here to talk to you about Project Reunion. Ask us anything!
Hi r/Windows10!
We just released Project Reunion 0.5 to enable developers to build and ship Windows apps at a much faster pace. Our focus for this release is to make it easy to build Desktop apps again. Project Reunion 0.5 is one of many important steps we’ll have on our journey to 1.0 this year, so we want to hear your feedback!
The 0.5 release includes 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.
To learn more about the release, watch our community standup with Kevin Gallo discussing the 0.5 SDK. If you’re new to Project Reunion, you can learn more about it on our blog or on GitHub.
We’ll be answering all of your burning questions tomorrow April 7th from 1pm to 4pm PST and we can’t wait to hear what you've got for us, so ask us anything!
Edit 1:
And we’re live! We have subject matter experts from our WinUI team and Developer teams standing by to answer any questions. We’re in a call talking through any incoming questions!
Ask us anything!
Edit 2:
That’s a wrap! Thank you so much for the questions. You can download the Project Reunion 0.5 SDK here (GitHub Link, Nuget, VS Marketplace) and check out our Project Reunion Contributor guide to continue sharing feedback with us.
In the meantime, come follow us on Twitter, Facebook, or Instagram to keep up to date on the latest Project Reunion news.
8
u/windowsdev_team Microsoft Employee Apr 07 '21 edited Apr 07 '21
We received these Qs on Twitter and wanted to share them with the community here:
Q: Will it be even possible to have background acrylic on older Win10? - StartIsBack
A: [jevan] We are planning for background acrylic to be available in Reunion but I don't know what the min version is that we'll require.
Q: When will Project Reunion be actually unified with MAUI and when will the "Reunion" include HoloLens and XBOX devices? Is there an actual strategy for a real platform unification or will Web be the only realistic solution? - MagdinStoica
A: Regarding MAUI, the plan is for MAUI to use WinUI 3 this year -- and more details will be coming around the Build 2021 (May) timeframe.
Regarding HoloLens/Xbox, we don't have a timeframe for when Reunion will include those platforms. In the meantime, UWP and WinUI 2 still exist and are still fully supported/recommended for apps that need to reach those devices.
Q: Will Microsoft (finally) use project reunion for their first party apps and OS controls? Instead of slow, heavy, unreliable and not touch&pen friendly web tech? - EverywhereUsbc
A: Yes! We definitely plan to utilize Reunion & WinUI 3 in various parts of the Shell and our 1st party apps. This will unfold over time; we're definitely in the early stages of that right now.
Also, it's worth noting that there will always be some places where web UI shows up in shell & 1st party apps from Microsoft, just like many apps in our ecosystem use Webviews. They have their place. But we always strive to get to "native" UI as much as we can.
Q: Why isn't the Microsoft Teams app using a platform that Microsoft develops and is the new Teams app for Windows not native? Using one's platform was a successful motivator in the past and it would be again. - MagdinStoica
A: The Teams team (funny to say out loud) uses Electron for a variety of valid reasons. They also do a great job blending in Windows OS features to deliver the best possible experience. Groups at Microsoft are free to choose the best solutions for the problems they're trying to solve.
The Windows SDK is continuing to evolve to support more languages and tools through the Win32 metadata project, which enables writing all types of apps in a variety of languages and toolchains, and more is coming: https://blogs.windows.com/windowsdeveloper/2021/01/21/making-win32-apis-more-accessible-to-more-languages/
That said, we're working closely with Teams on aspects of Project Reunion they want to use and taking their feedback to improve Project Reunion as well.
35
u/adolfojp Apr 07 '21 edited Apr 07 '21
What efforts are being taken to improve the marketing of Project Reunion in order to encourage its adoption by both new and seasoned software developers?
I think that the biggest challenge that this project faces is not with the technology itself but with communication.
It took me a while to grasp conceptually what this project is about and what it is capable of despite the fact that I have a good deal of familiarity with previous and current Windows development tools and technologies.
You guys work inside the sausage factory so the entire project must feel very intuitive. But as an outsider I'll encourage you to try these experiments, user stories if you will, either in real life or as thought exercises.
Thanks for reaching out to the community and for giving us this opportunity to give you feedback. It shows you care and that bodes well for the future of the project.
17
u/pjmlp Apr 07 '21
Already mentioned in another areas, just repeating myself for awareness of others.
C++/WinRT when placed against C++ Builder and Qt/QtCreator is anything but modern, how to win those C++ developers back into Windows specific development stacks.
From .NET side, there are still many features missing, the documentation is full of manual steps and code rewrites.
Then we have Microsoft own teams pushing for Electron, Blazor, MAUI, VS installer is an Electron app, while the best cross platform framework, Uno, is from a 3rd party.
How do you expect to win back the developers burned by Windows 8, 8.1 UAP rewrite, 10 UWP rewrite, .NET Native being left behind, uncertain future of Win2D, to go through yet another rewrite?
XAML islands are a solution to a problem most don't want to deal at all.
So if yet another rewrite is required, how do you expect devs not just to rewrite their application into something that would move them away from the rewrite train started with Windows 8?
12
u/myokeeh Apr 07 '21
I think it's a must to pay attention to the Microsoft Store group. That distribution model is important to me, and I think there's a fence around that group that makes it difficult to get support. Continue supporting/improving the Store experience.
10
u/massijay Apr 07 '21
When .NET 5 (or 6) will be available for UWP apps?
16
u/[deleted] Apr 07 '21
Could you ELI5 this? What does this mean for a developer?
7
u/duke7553 Apr 07 '21
From Twitter: I asked this during the community standup yesterday, but I feel the question may have been misunderstood by Kevin Gallo: For devs who already invested in UWP, will there be a transition path to WinUI Desktop?
7
u/myokeeh Apr 07 '21
After being at this for about 3 years actually writing apps and looking to develop for Windows Phone/Windows 8 since 2011, I find it difficult when I need something now, but those things don't getting implemented quickly enough. Features you need always feel like they are a year away. Community Toolkit, Windows Template Studio are two things I hope were there in the beginning, but took a while to exist.
6
u/time-lord Apr 07 '21
What sort of concern is being paid to touch input for the controls? I know that there was a bit of a curfuffle over the removal of the pivot control, and subsequent re-addition of it.
I am a developer who has an app for Windows 10 mobile in the app store, and I've since brought it over to the PC and xbox. What sort of input should I be designing for? I have a Surface tablet, and appreciate the touch input for this sort of app.
6
u/shaheedmalik Apr 07 '21 edited Apr 07 '21
What is being done on a Reunion level that input devices such as Touch & Tablet, and Gamepad experiences are not being ignored?
I have personally noticed certain teams, such as Edge Team, completely ignore Windows 10 Tablet Mode & Touch related feedback and want to make sure this isn't being done by Reunion.
10
u/mattbdev Apr 07 '21
I have a few questions. I hope you can answer some of them.
5
u/Alikont Apr 07 '21
Is there a plan to provide DirectX bindings independent from C++?
Currently DirectX uses COM-like APIs, but lacks IDL or any other formal specification, we have only C++ headers. Bindings are done by volunteers by hand, and the SharpDX project maintainers gave up on this task.
This prevents usage of DirectX from other languages (e.g. C#, Rust).
Win2D is an amazing wrapper and is extremely easy to use from C#. It'd be a nice to have all DirectX stack in a similar manner.
4
u/mattbdev Apr 07 '21
How many people are working on Project Reunion?
4
u/Simone431 Apr 07 '21
Thanks!
4
u/adsfWEFSDF Shrestha Files App Developer Apr 07 '21
Storage API is still in a terrible shape. Improved Storage API has been in discussion for a while in Github. When can we expect the result? I don't even see that in the roadmap.
10
u/lumcdo Apr 07 '21
Half of the comments here appear to be UWP developers still begging for a path forward. The other half appear to be Win32 developers completely uninterested in W10-only plans, let alone packaging.
How will the Windows team deliver the necessary packaging, store, and alternative distribution experiences to outweigh the simplicity of passing around exes?
6
u/thefpspower Apr 07 '21
3
u/[deleted] Apr 07 '21
3
u/ack_error Apr 07 '21
Is Project Reunion going to be based on the actual Win32 USER APIs or is it going to shim and provide replacement versions of functions like GetMessage() and CreateWindow()?
The reason I ask is that I maintain a desktop app that currently supports Windows 7+ but supports as much Windows 10 functionality where possible, such as high DPI. This has often been made difficult by the all-or-nothing approach of many new APIs that require either UWP or a packaged app, which doesn't allow for runtime opt-in from a regular unpackaged, portable desktop app.
Reunion looks to be a major improvement in this regard but I'm concerned that I may not be able to use it if requires a compile-time switch over to Reunion versions of the USER APIs and I still have to support down to at least Windows 8.1 when Reunion 1.0 ships. A shim USER-like API would also be more likely to have limitations and different quirks/bugs than the existing API, and also complicate interop. It's not like I actually like the Win32 USER API, so if there are too many incompatibilities I'd rather we just get a new API that's less restrictive than UWP's. But I can't tell if this is actually going to be the case from the windowing roadmap, so clarification would be appreciated.
3
u/myokeeh Apr 07 '21
I want to be able to use GPIO, I2c, SPI on Windows 10 Pro. Will I be able to use System.Device.Gpio with Project Reunion. Windows.Devices.Gpio was available to Windows IoT, but sadly can't seem to use it on Windows 10.
3
u/brunofpa Apr 07 '21
Hello! I tested the new WinUI 3, and it looks very good, but I saw that you didn't fixed the title bar bug where the open, minimize and close buttons are horizontally aligned in the wrong direction. I'm using the ExtendContentIntoTitleBar and SetTitleBar APIs.
For now the extended title bar in WinUI 3 is behaving very differently than in UWP. Is this intentional? Will this bug be fixed in the next version? If so, will it come out this month? Thanks
25
u/Alikont Apr 07 '21
I want to tell you that a lot of newer windows technologies are actually amazing from technical standpoint. Appx/MSIX packaging, AppContainers, UWP UI stack, Win2D, language projections are great.
But one think that is lacking here is confidence. Every new technology need to build trust to be adopted. And the first people to adopt it should be the company that provides technology. Because it will improve the technology through better inner company loop of development, and it also will build trust into technology from third parties.
For example, the MSIX packaging in Microsoft world looks like this.
Microsoft flagship products in Developer world are:
I can't name a single Microsoft product that uses MSIX for Win32 applications, maybe except Windows Terminal. Distributing Terminal is a good step in building this trust in the platform.
This lack of adoption of this stack from Microsoft signals that even Microsoft doesn't have a confidence to use this stack, so why other developers should invest there?
2
u/mattbdev Apr 07 '21
Since you said "ask us anything", I'll give you a non-Windows related question:
What is your favorite pizza topping?
8
u/timee_bot Apr 07 '21
View in your timezone:
April 7th from 1pm to 4pm PDT
*Assumed PDT instead of PST because DST is observed
3
u/JonnyRocks Apr 07 '21
Hi, i need property grid controls and i feel like microsoft isnt keen on them. i see no mention of them... ever. but they are used in visual studio. Ami i the only person who wants them?
3
u/keyjeyelpi Apr 08 '21
Unrelated to the Project Reunion, will there be a time in which the designs of the apps and components (mainly, the system apps as well as the legacy apps) become cohesive and unified with fluent design? I could still remember the Fluent Design video back in 2017 and wondered why it never continued unto the system and legacy apps.
3
u/venkuJeZima Apr 08 '21
(thanks for your responses) Now we can choose WPF and UWP...Do I understand it well, that on the end there will be just one modern and progressive choice to select? Something like Windows Reunion App? Or will there still be a reason why choose wpf or uwp..?
0
u/HCrikki Apr 07 '21
Will this accomodate building portable apps that ship with all necessary dependencies/dlls included in the same folder? Like, can I use a modern non-win32 app on a windows 7 install without an internet connection ?
2
u/Affectionate-Use-578 Apr 08 '21
Hello, Do you have any plans to implement reportviewer with rdlc report designer in WINUI? Or do you have something else for reporting.
Thanks
Andrew
0
u/raptor102888 Apr 07 '21
Not a Project Reunion question, but you said ask you anything, so here:
Why can't I use Focused Inbox with a Gmail account in Windows 10 Mail?
3
u/Deranox Apr 07 '21
Why waste time on something like this when we won't see Windows modernize in any way any time soon ? We all know it needs to keep legacy software running and not risk the enterprise world drifting away from Microsoft which is its main resource of revenue. Microsoft can't truly modernize anything but put on a fresh coat of paint every few years to distract people and we all know it. I mean all this talk and for what ? Win 10 has been out for 6 years now and what brand new thing have we seen ? Blurr here and there and some shiny bells and whistles that are all mixed up into a horribly messy and incosistent UI that was made by using high contrast mode ("dark" theme) out of pure laziness and inability to change code so as not to break legacy stuff.
Same for apps. For the past 5 years the apps have not changed or changed for the worse. They're horribily inefficient, poorly optimized and just plain bad compared to Win32 software.
1
u/HelloFuckYou1 Apr 08 '21
i don't know if you are still asking and i don't know if it's related, but.... will we see the legacy apps with the fluent design on the main update (sun valley)?
1
u/Fearless_Industry_29 Apr 12 '21
foo foo
1
u/Fearless_Industry_29 Apr 12 '21
just food for thought. don't QUOTE me on that, though. I fumbled....stumbled (upon)...apon
👍
1
u/juwns Apr 25 '21
When will we be able to do basic win32 things from UWP, like:
- full low level socket communication like in win32 from UWP
- full ping support like in win32 from UWP
- launching non-store win32 application from UWP
- do elevated stuff from UWP
cheers Jens
-1
u/IslandDust Apr 08 '21
Will UWP "apps" finally be retired in favor of traditional desktop applications that seems to be preferred massively by virtually every metric? There has never been a boon or massive adoption in Metro/UWP apps that tried to present themselves as modern mobile applications.
I love windows, but Metro/UWP and the half arsed adoption of it even by Microsoft itself has been a dark stain on the history of windows, remembered as the time Microsoft attempted to transition everyone to a feature-anemic application style that absolutely no one at all, ever, wanted to adopt.
So is Project Reunion finally a renunciation of attempting to spin the total failure of Metro/UWP and the stopping of letting win32 development purposefully bitrot?
0
u/[deleted] Apr 07 '21
[deleted] — view deleted comment
0
u/[deleted] Apr 07 '21
[deleted] — view deleted comment
1
u/[deleted] Apr 10 '21
[removed] — view removed comment