WinUI Community Call: March 6, 2024 #9361
Replies: 16 comments 37 replies
-
|
What's the expected ETA/release schedule for InkCanvas and InkToolbar? |
Beta Was this translation helpful? Give feedback.
-
|
they aren't likely to fully land in the 1.5 timeline at this time. |
Beta Was this translation helpful? Give feedback.
-
|
Is segmented control coming in version 1.5? |
Beta Was this translation helpful? Give feedback.
-
|
@Gaoyifei1011 Yes. https://learn.microsoft.com/en-us/windows/apps/windows-app-sdk/stable-channel#new-selectorbar-control |
Beta Was this translation helpful? Give feedback.
-
|
@roxk Thank you very much. I've already seen it in the WinUI 3 Gallery |
Beta Was this translation helpful? Give feedback.
-
|
Can we expect General Improvements to Xaml going forward? Xaml been same and never had any innovation for long time now |
Beta Was this translation helpful? Give feedback.
-
|
Many modern platforms are going for coded UIs - like MVU pattern. |
Beta Was this translation helpful? Give feedback.
-
|
Yeah MVU because our software isn't already slow enough. |
Beta Was this translation helpful? Give feedback.
-
|
How often can we expect community calls in the future? Will we have long gaps like this going forward or was this a rare occurrence while you worked on a plan to engage with us better in the future? |
Beta Was this translation helpful? Give feedback.
-
|
Any plans for supporting WinUI development outside visual studio? Maybe it's technically possible but it's very tied to VS atm with debugging and project templates etc... |
Beta Was this translation helpful? Give feedback.
-
|
As @DarranRowe mentions, all activities can be performed on the command line. Windows App SDK has no intrinsic dependencies on Visual Studio, but it does have on MSBuild. So, for example, a cmake project in VS isn't supported. But any development environment that supports MSBuild invocation, such as VS Code, should be fine. |
Beta Was this translation helpful? Give feedback.
-
We have to set |
Beta Was this translation helpful? Give feedback.
-
|
@Scottj1s Thanks for acknowledging this. While technically possible, it is unnecessarily complicated to figure out all the different flags of the different compilers (msbuild, xaml) we have to use to compile a WinUI application thus forcing most developers to use VisualStudio. |
Beta Was this translation helpful? Give feedback.
-
|
To give a more concrete comment, I would really love to see official support for Jetbrains Rider. |
Beta Was this translation helpful? Give feedback.
-
|
@christosk92 |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
|
For 1, isn't that a VS thing? As far as 3 is concerned, the biggest issue was that the .NET RID change happened right in the middle of the 1.4 development cycle, and .NET 8 was due to be released after 1.4. The team chose to not support .NET 8 in 1.4 because of this.
That should be most of the build fixes, and I'm sure that if there are any remaining issues, they will be in place by 1.5. |
Beta Was this translation helpful? Give feedback.
-
|
Regarding 1 and 3 (templates): Regarding 7 (NativeAOT): |
Beta Was this translation helpful? Give feedback.
-
|
I think on the website there should have been a large red & yellow banner "WARNING - .Net 8 is not supported". I upgraded to .Net as soon as it was released, but a message on WASDK saying it wasn't supported must have been buried somewhere. |
Beta Was this translation helpful? Give feedback.
-
|
It is supported in 1.5. |
Beta Was this translation helpful? Give feedback.
-
|
What can you say about the following:
|
Beta Was this translation helpful? Give feedback.
-
|
@MEK3DK Our Xelion Windows App is a WinUI 3 app and is widely used. Currently our app has a very low crash rate. Last time I checked I received quite some money for adding features to this app, so no it's not a hobby. ;) |
Beta Was this translation helpful? Give feedback.
-
|
I don't believe that WinUI3 isn't ready for production use. It's just deficient compared with the existing functionality of WPF. The reality is that WinUI3 is mostly an "upgrade" path for UWP based applications (if you can work around the various missing pieces of functionality). We moved to it because it provided multi-window support, removed the sandboxing, and gave full access to the Win32 and other C based APIs. This allowed us to combine our UWP app with a WPF application into a single application. The transition from WPF to WinUI3 was very painful (things like min/max window size and owner drawn windows were very painful) and required a great deal of interfacing with the underlying win32 APIs to recreate things that we base properties in WPF. If our UWP based application wasn't an order of magnitude larger and more complex than our WPF app we would have migrated it to WPF instead of WinUI3. Until they reduce the number of deficiencies between WPF window support and the current state of WinUI3 windows it's going to be very hard to convince any team currently using WPF to port the app or start new development in WinUI3. It's simply too difficult to replicate functionality that were simple properties of the Window in WPF. In my opinion they should be focusing on improving this and working on bug fixes rather than new functionality and feature. What is currently available in WinUI3 is already pretty rich feature wise, but it simply isn't bulletproof in all scenarios and requires custom workarounds to get around issues. |
Beta Was this translation helpful? Give feedback.
-
|
@NicholasChrzan Yes, you are right that a fair amount of low level win32 APIs are needed. For me that is not a deal-breaker, but I can imagine this is painful coming from a WPF background. Libraries (like WinUIEx) can be of great help. I already had my own windowing code in place, before WinUIEx existed, but I don't mind fiddling with win32. |
Beta Was this translation helpful? Give feedback.
-
|
If only WinUI3 was actually an upgrade, instead of a downgrade without tooling parity to the designer, .NET Native, C++/CX, and features years away, assuming Microsoft doesn't eventually replace everything with Blazor. |
Beta Was this translation helpful? Give feedback.
-
|
Well, you can found one at least, everything needs a start someday... (Coca-Cola) |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
|
Yes please! This functionality gap is something that is holding back the Terminal team from adding support for drag n drop re-ordering of the tabs in an elevated session. It works in the normal instance, but not elevated. Please fix this! |
Beta Was this translation helpful? Give feedback.
-
Not to mention that SetWindowLongPtr using GWLP_HWNDPARENT is undocumented and completely unsupported in Windows itself. |
Beta Was this translation helpful? Give feedback.
-
|
Yes, modal window support would be much appreciated. Using SetWindowLongPtr feels as a terrible hack to me. |
Beta Was this translation helpful? Give feedback.
-
|
Any updates on going open source? |
Beta Was this translation helpful? Give feedback.
-
|
Isn't it already? |
Beta Was this translation helpful? Give feedback.
-
|
We've been careful to use the term "source available", which, with public debug symbols, enables debugging the Windows App SDK binaries. Full "open source", with the expectation of buildability, testability, accepting PRs, and so on, is still work in progress. No updates on that. |
Beta Was this translation helpful? Give feedback.
-
That's good enough for most use cases I bet. |
Beta Was this translation helpful? Give feedback.
-
|
Any news about Creating a Windows 11 context menu without using C++ and IExplorerCommand? |
Beta Was this translation helpful? Give feedback.
-
|
There was good progress with the last few releases in respect of bug fixes. The Are there any plans to improve the Here is a long list of issues still open on |
Beta Was this translation helpful? Give feedback.
-
|
Yes, there are plans to look at top issues of TreeView during 1.6. I'm not sure the set of issues has been selected yet, but I added your comment to the internal task. |
Beta Was this translation helpful? Give feedback.
-
I'd like to know when WinUI team will WinUI 3 UIElement. ProtectedCursor properties change from protected into public? |
Beta Was this translation helpful? Give feedback.
-
|
There a quite a few APIs that have been in the experimental releases for a long time but have not been promoted to the stable release. These includes the dpi related functionality in the DisplayInformation class (currently win32 interop code is required here) and ContentExternalOutputLink class (for blending additional content with swap chains which is otherwise not possible at all). When can we expect these APIs to be available in a stable release? Alternatively, maybe some functionality could be introduced that let you enable experimental APIs in stable releases. |
Beta Was this translation helpful? Give feedback.
-
|
Not tried it, but shouldn't you be able to look at sources of Experimental release and try to do the same thing as they do with |
Beta Was this translation helpful? Give feedback.
-
|
The source code for these APIs is not public |
Beta Was this translation helpful? Give feedback.
-
|
A Visual XAML editor inside VS is the in the Top 5 voted for things, any thoughts on this ? bringing it on-par with WinForms, WPF, and UWP. |
Beta Was this translation helpful? Give feedback.
-
|
WPF Team is introducing WinUI 3 styles and controls for WPF, isn't this a threat to WinUI3? |
Beta Was this translation helpful? Give feedback.
-
|
I think not, Windowsappsdk will soon support native aot, in the binary distribution volume, Windowsappsdk will have more advantages |
Beta Was this translation helpful? Give feedback.
-
|
WPF can run on Windows 7+, I think many developers prefer to use it. |
Beta Was this translation helpful? Give feedback.
-
|
WindowsAppSDK works on WPF (it's a promoted feature) - so won't that capability come to WPF as well ? I have to admit, with WPF using .net 8 & WASDK 1.5, it compiles faster, has an in-VS visual editor, property lists, and looks the same (with WPF-UI, which is an add-on, but then you need things like WinUIEx for WinUI). Don't get me wrong, my apps are 100% WinUI 3 Desktop, but I wouldn't disregard WPF. |
Beta Was this translation helpful? Give feedback.
-
|
Currently I still prefer WinUI as it has the features of x:bind and SwapChainPanel. That being said, if WPF got those features, I will choice WPF, as WPF has a designer. |
Beta Was this translation helpful? Give feedback.
-
|
Was the blog post/documentation regarding "Improved debugging tools" that @Scottj1s presented on the calll already published? I was not able to find it, but I think it would highly benefit devs. |
Beta Was this translation helpful? Give feedback.
-
|
@lolametro thanks for the suggestion - we'll consider adding that content to the Windows App SDK docs. |
Beta Was this translation helpful? Give feedback.
-
|
In WinUI, can we use a C# library/component in C++ Application? |
Beta Was this translation helpful? Give feedback.
and others
-
Please join us for the March 2024 edition of the WinUI Community Call. This event will be live-streamed to YouTube: https://www.youtube.com/watch?v=uFgGhNGlPm4
Details
Date: Mar 06, 2024
Time: 17:00-18:00 UTC (9:00-10:00am Pacific)
Anyone and everyone is welcome - no pre-registration is required.
This will be an informal interactive live stream directly with members of our engineering team.
Format
The community call is a call among the WinUI team that is live-streamed onto YouTube. We present on new updates, share information, welcome guests, and answer your questions.
The WinUI and WindowsAppSDK team are back! Sorry we've been quiet; we've heard you're all excited for a call! We've been working on a more sustainable plan to engage with the developer community long term, and we're excited to share more with you all soon over the coming months!
Agenda
Q&A Code of Conduct
Leave us your questions in the comments on this issue or live in the YouTube chat during the stream!
Beta Was this translation helpful? Give feedback.
All reactions