Typical MS again

[davecamp]

Why does MS insist on showing source code examples without any images of what you should expect to see in your app. It's typical that MS describe a UI system using text only - you people must live in a bubble where you are all just bonkers crazy.

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: f5034d06-ef99-ace2-0b91-0272b74c4a79
• Version Independent ID: 698b4146-ccf0-21d2-8994-0f7fd22c40a6
• Content: Update existing projects to the latest release of the Windows App SDK - Windows apps
• Content Source: hub/apps/windows-app-sdk/update-existing-projects-to-the-latest-release.md
• Product: reunion
• Technology: ****
• GitHub Login: @mcleanbyron
• Microsoft Alias: mcleans

[mcleanbyron]

Hi @davecamp - Thank you for your feedback. The specific article you commented on provides instructions for the Visual Studio project configurations needed to update a Windows App SDK project to the latest release. Can you confirm that this is the article in which you would like to see screenshots, and if so, which portions of the guidance in particular do you think would benefit from screenshots? Or do your comments apply to other articles - for example, articles about WinUI? The more details you can provide, the better we can take action on your feedback. Thank you!

[mdtauk]

I think visuals alongside the sample code is a good idea, to help connect what you type in Xaml with what you see in your UI.

[mcleanbyron]

We do strive to include visuals wherever possible and where it makes sense to do so. For example, most of the articles under the Design and UI node have visuals to help explain patterns/concepts, and the Controls section tries to do this for every control. Relatively new tutorials such as Build a basic WinUI 3 desktop app also use screenshots to try to help guide you through the process.

That said, I'm sure there are other areas of the docs that could use more visuals, and I'd love to gather that feedback if you have it. The Update existing projects to the latest release of the Windows App SDK article called out in this issue is primarily about command line operations and project file (XML) updates to migrate an existing project to the latest Windows App SDK, and we generally don't include screenshots for these sorts of instructions because they usually don't add any benefit. If you feel that this article could benefit from some specific screenshots, or if you have feedback about other areas of the docs that could use visuals, please let us know. Or even better, use the feedback control at the bottom of those other articles.

Thank you!

[Mancerrss]

Here's a workflow suggestion to you guys :

Have a seperate team that will handle Docs illustrations, screenshots and animations, and work closely beside them, regrading the demands, contexts or requirements of the specific Docs. Try to use GIF or Movie animations, screen captures as much as possible, as those are much better on getting the point of the implementation across.

So there's consistency, quality standard on the Docs images too. Literally, I feel like those that written the Docs too, are the ones that attached the images too. It's even not in good standards, some are literally just small snippets, some screenshots, some are screenshots even back then on Windows XP, some are even on Windows 7 (on the same article), some are even dead links for the images, and most doesn't even have the ClearType on. It's so unprofessional.

Images, illustrations and animations are a good long term investment to not only the understanding of your developers, but also for its ecosystem designers.

Let's ride this new era of reinvigorated, clean and modern Windows 11, with a renewed eye for quality, structured and standardized Docs on the platform as well.