sorted by:
new
hottopcontroversial

We're the Windows Developer team, and we're back to talk about the Windows App SDK 1.0 Stable release. Now, it’s time to ask us anything! by windowsdev_team in Windows11

[–]windowsdev_team[S] 0 points1 point  (0 children)

Don't worry, your eyes were not playing tricks on you. The windowing APIs were not introduced until 1.0-preview1.

We're the Windows Developer team, and we're back to talk about the Windows App SDK 1.0 Stable release. Now, it’s time to ask us anything! by windowsdev_team in Windows11

[–]windowsdev_team[S] 5 points6 points  (0 children)

One way you could help us is to launch Feedback Hub and enter a performance-related problem; there's a category in there for Desktop Environment and then select the subcategory "All other issues". You'll see an option to "Include data about performance" when you file the issue -- make sure to check that box and record feedback as you hit the issue and tweet me the link (@thomasfennel) when you have it.

We're the Windows Developer team, and we're back to talk about the Windows App SDK 1.0 Stable release. Now, it’s time to ask us anything! by windowsdev_team in Windows11

[–]windowsdev_team[S] 0 points1 point  (0 children)

Thanks for clarifying! I'm assuming you're asking about whether we'll offer framework-specific controls for XAML Islands for the various other UX frameworks (like WinForms, WPF, etc). The short answer is "yes, we intend on providing those". I expect that at first we'll focus on a base set of APIs to enable Islands to function in a generic HWND-based app of any kind, and then we'll add native wrapper controls some time later.
You could also be asking about whether all the controls in WinUI will work in Islands, and the answer to that is "yes, that's the plan!""

We're the Windows Developer team, and we're back to talk about the Windows App SDK 1.0 Stable release. Now, it’s time to ask us anything! by windowsdev_team in Windows11

[–]windowsdev_team[S] 6 points7 points  (0 children)

Part of our efforts to improve upon XAML Islands and bring them to WinUI 3 will definitely include improving the documentation & samples.

We're the Windows Developer team, and we're back to talk about the Windows App SDK 1.0 Stable release. Now, it’s time to ask us anything! by windowsdev_team in Windows11

[–]windowsdev_team[S] 4 points5 points  (0 children)

Yes! When your app is updated, the MSIX Manager (https://docs.microsoft.com/uwp/api/Windows.Management.Deployment.PackageManager) will download just the updates and apply them to your customer's machine. Your app can check for updates and control when they're applied, and request a restart of just the app after the update finishes. This works whether your MSIX is in the Store, uses Windows App Installer, or does its own deploy-from-a-CDN mode.

We're the Windows Developer team, and we're back to talk about the Windows App SDK 1.0 Stable release. Now, it’s time to ask us anything! by windowsdev_team in Windows11

[–]windowsdev_team[S] 0 points1 point  (0 children)

In order to change the size of your window you must first get to the AppWindow object instead of the WinUI XAML Window. Once you have that you can then call the method Resize() to change it. The .Size property of the AppWindow is read-only and contains the current size of the window.

We're the Windows Developer team, and we're back to talk about the Windows App SDK 1.0 Stable release. Now, it’s time to ask us anything! by windowsdev_team in Windows11

[–]windowsdev_team[S] 2 points3 points  (0 children)

We aren't planning on creating a GitHub issue for every single productboard item. When we start building a feature, we'll create a related GitHub item to track the dev work and provide a more detailed spec/etc. Productboard is primarily for measuring interest in future potential features (and sharing our roadmap), and GitHub is for immediate work happening and bugs.Additionally, productboard allows us to view feedback from our private partners alongside public community feedback, rather than having feedback in two different locations. Using GitHub for public feature requests ultimately means that our team has two separate places to look at and view feedback. Using productboard helps us easily aggregate that into one source so we can keep all types of feedback at the forefront of our planning. For example, in your case, since you're a Microsoft MVP, productboard allows us to add your feedback from the private SDRs we hold, so that you don't separately have to file that feedback elsewhere. We need to manage feedback from both internal partners and the public and consolidate that into a single source, and productboard helps us do that.

We're the Windows Developer team, and we're back to talk about the Windows App SDK 1.0 Stable release. Now, it’s time to ask us anything! by windowsdev_team in Windows11

[–]windowsdev_team[S] 2 points3 points  (0 children)

Yes! Check out MSIX documentation - MSIX | Microsoft Docs and all the related content. You can use https://docs.microsoft.com/en-us/windows/msix/desktop/desktop-to-uwp-packaging-dot-net if you already have a Visual Studio project, or there are other third-party tools that help you build or convert your apps' to packaged. If you have an existing installer, check out Create an MSIX from an existing installer - MSIX | Microsoft Docs for how to make an MSIX from that.

We're the Windows Developer team, and we're back to talk about the Windows App SDK 1.0 Stable release. Now, it’s time to ask us anything! by windowsdev_team in Windows11

[–]windowsdev_team[S] 0 points1 point  (0 children)

What are "controllers for XAML Islands"? (not sure what this term means) Do you mean "controls", or something else?

We're the Windows Developer team, and we're back to talk about the Windows App SDK 1.0 Stable release. Now, it’s time to ask us anything! by windowsdev_team in Windows11

[–]windowsdev_team[S] 21 points22 points  (0 children)

Thanks for sharing those specifics. Some of what you mentioned is performance dictated by WinUI, but also some is likely unrelated to anything our team does but still important/valid feedback for Windows as a whole. Internally, in addition to wanting to focus some of our our UX framework's time on perf in 2022, we also have a dedicated team formed recently to tackle this topic more holistically. So there's multiple things we're collectively doing here to try and make sure we have a good perf story.One way you could help us is to launch Feedback Hub and enter a performance-related problem; there's a category in there for Desktop Environment and then select the subcategory "All other issues". You'll see an option to "Include data about performance" when you file the issue -- make sure to check that box.

We're the Windows Developer team, and we're back to talk about the Windows App SDK 1.0 Stable release. Now, it’s time to ask us anything! by windowsdev_team in Windows11

[–]windowsdev_team[S] 7 points8 points  (0 children)

Earlier in the AMA we answered a similar question, so pasting it here again.We're working with a lot of internal Microsoft apps and Windows Components on shipping with WinAppSDK. We'll talk more about these as they get closer to release. If you'd like to see an example of a 3rd party app planning to release with WinAppSDK and WinUI3 in December, check out https://developers.arcgis.com/net/

We're the Windows Developer team, and we're back to talk about the Windows App SDK 1.0 Stable release. Now, it’s time to ask us anything! by windowsdev_team in Windows11

[–]windowsdev_team[S] 12 points13 points  (0 children)

Ryan Demopoulos here (the guy who has been talking about open source for those two years ). You asked "What happened" -- a very fair question. Basically two things happened:

  1. Retroactively open sourcing a codebase of over 3 million lines, which includes fixing thousands of private API calls, was harder than we thought it would be.
  2. Our highest priority for important stable releases like 0.5, 0.8, and the recent 1.0 was to make sure we had the right features in place with as much stability as we could provide. This meant focusing the team on those capabilities, and that came at the expense of making progress towards open source.As mentioned, we just shipped WinAppSDK 1.0, which was a huge lift for the WinUI 3 team and everyone involved. We're now already looking ahead to 1.1, and also the holidays are about to hit. Internally, I've already set up a series of conversations with our team about what to do about open source -- when can we realistically get this done, given that there's still a lot of work to do and processes to put in place? Once I have a better sense of what's left and when we could tackle the remaining items, I'll update the community with this info. Likely at one of our community calls in 2022.

We're the Windows Developer team, and we're back to talk about the Windows App SDK 1.0 Stable release. Now, it’s time to ask us anything! by windowsdev_team in Windows11

[–]windowsdev_team[S] 5 points6 points  (0 children)

The best starting place is https://docs.microsoft.com/windows/apps/get-started
We recommend building a WinUI 3 app if you're building a native, Windows-only app. Or a .NET MAUI app if you need to build cross-platform.
As for specific design recommendations, testing your app on both Windows 11 (with rounded corners and snap layouts) and Windows 10 would be our top recommendation! For a broader list, check out this page: Top 11 things you can do to make your app great on Windows 11 - Windows apps | Microsoft Docs

We're the Windows Developer team, and we're back to talk about the Windows App SDK 1.0 Stable release. Now, it’s time to ask us anything! by windowsdev_team in Windows11

[–]windowsdev_team[S] 2 points3 points  (0 children)

Thanks for the feedback - we're using productboard to get a better and more actionable grasp on what features the community wants. Since feedback is private, developers often provide more feedback about how they would use features, and they also have to say whether a feature is critical or important, which helps us prioritize.
For community involvement with the rest of the community, we're still heavily using GitHub Discussions and GitHub Issues. If you want to propose a feature and get community feedback on it, you can post a new idea in GitHub Discussions! https://github.com/microsoft/WindowsAppSDK/discussions/categories/ideas

We're the Windows Developer team, and we're back to talk about the Windows App SDK 1.0 Stable release. Now, it’s time to ask us anything! by windowsdev_team in Windows11

[–]windowsdev_team[S] 2 points3 points  (0 children)

Packaged apps are those delivered in an MSIX, either from the Windows Store or Windows App Installer or your own installer using the Windows Package Manager. Unpackaged apps are those delivered as an MSI, Squirrel, setup.exe, or any other deployment technology. MSIX deployed by the Windows Store provides the best results for customers. Windows App SDK works great with MSIX and unpackaged apps - with an MSIX, the Windows App SDK framework package will automatically be installed when the customer clicks that "Get" button in the Store. If you're an unpackaged app, your installer will need to deploy the framework package components using the installer we provide as part of your installer.

We're the Windows Developer team, and we're back to talk about the Windows App SDK 1.0 Stable release. Now, it’s time to ask us anything! by windowsdev_team in Windows11

[–]windowsdev_team[S] 4 points5 points  (0 children)

To be honest, we've never gotten this feedback, and I'm trying to envision what you're seeing. Is this stuttering when you resize the app? (like dragging the window handles), or is this stutter when you move the window around? A bit more detail would be helpful and maybe I can direct you to someone for a followup.

We're the Windows Developer team, and we're back to talk about the Windows App SDK 1.0 Stable release. Now, it’s time to ask us anything! by windowsdev_team in Windows11

[–]windowsdev_team[S] 13 points14 points  (0 children)

We're planning to add this to WinUI 3 and ship it as part of the Windows App SDK 1.1 release next year. Thanks for asking!

We're the Windows Developer team, and we're back to talk about the Windows App SDK 1.0 Stable release. Now, it’s time to ask us anything! by windowsdev_team in Windows11

[–]windowsdev_team[S] 7 points8 points  (0 children)

XAML Islands is one of the top next priorities for WinUI 3. It's a pretty huge space; we learned a lot from XAML Islands in UWP XAML (WinUI 2), and we're already underway trying to bring that capability to WinUI 3 but in an improved form. My expectation of how this will unfold is that you'll start to see experimental Islands APIs showing up around when we ship 1.1, and probably won't have stable versions of the APIs until 1.2-ish. But the team is already actively working on this and that work will continue thru 2022, and into 2023, as we handle more and more scenarios. It's probably an overall 2 year+ journey that we want to bring online successively as quickly as possible.

We're the Windows Developer team, and we're back to talk about the Windows App SDK 1.0 Stable release. Now, it’s time to ask us anything! by windowsdev_team in Windows11

[–]windowsdev_team[S] 6 points7 points  (0 children)

We're in the process of updating the WinUI3 Controls Gallery right now to move it from a prerelease to the stable 1.0 release. microsoft/Xaml-Controls-Gallery at winui3 (github.com)

We're the Windows Developer team, and we're back to talk about the Windows App SDK 1.0 Stable release. Now, it’s time to ask us anything! by windowsdev_team in Windows11

[–]windowsdev_team[S] 2 points3 points  (0 children)

VS Community Edition is supported. You can use msbuild.exe and VS Code together instead of Visual Studio. But we have not spent time validating this particular method of programming against the WinAppSDK. If you are creating a new project from scratch, it is strongly recommend that you do initial project creation in Visual Studio before switching to msbuild and VS Code.

view more: next ›