Insider Dev Tour Taipei 2019 - Future proof your desktop apps with .net core
1 like670 views
The document outlines a presentation on future-proofing desktop applications using .NET Core 3, presented by Alan Tsai, a backend engineer and Microsoft Certified Trainer. Key topics include platform options, packaging with MSIX, and the features of .NET Core 3. It also provides links to resources for environment preparation, migration, and sample code used in the session.
Insider Dev Tour Taipei 2019 - Future proof your desktop apps with .net core
- 1. #insiderDevTour Future-proof your Desktop Apps with .NET Core 3 Alan Tsai
- 2. #insiderDevTour About Me Alan Tsai 蔡孟玹 • .NET 技術爲主後端工程師 • 喜歡學習不同東西 • DevOps, AI, Container, Azure • Blogger • Microsoft Certified Trainer • Stud4.TW 成員 • 翻譯OSS • 看小説
- 3. #insiderDevTour WinUI .NET Core 3 MSIX XAML Islands What we’ll cover today
- 4. #insiderDevTour Platform Options Windows Forms Windows Presentation Foundation Universal Windows Platform (UWP)
- 5. #insiderDevTour Platform Options Windows Forms Windows Presentation Foundation Universal Windows Platform (UWP)
- 6. #insiderDevTour Platform Options Windows Forms Windows Presentation Foundation Universal Windows Platform (UWP)
- 7. #insiderDevTour UI Framework Options Windows Presentation Foundation: https://github.com/dotnet/wpf Windows Forms: https://github.com/dotnet/winforms Windows 10 XAML: https://github.com/Microsoft/microsoft-ui-xaml
- 8. #insiderDevTour .NET Core 3. Why? Faster Side-by-Side installation Better packaging options (MSIX) Open Source .NET Standard 2.1 New Features
- 9. #insiderDevTour .NET Schedule July 2019 .NET Core 3.0 RC Sept 2019 .NET Core 3.0 GA Nov 2019 .NET Core 3.1 LTS Nov 2020 .NET 5.0 GA Nov 2021 .NET 6.0 LTS Nov 2022 .NET 7.0 GA Nov 2023 .NET 8.0 LTS
- 10. #insiderDevTour Migrating • .NET Portability Analyzer • https://aka.ms/portabilityAnalyzer • Migrate to PackageReference • Manual process, but done by VS • Blog Post with all steps • https://aka.ms/porting-to-netcore3
- 12. #insiderDevTour Environment Preparation - .NET Core 3 • https://dotnet.microsoft.com/download/dotnet-core/3.0
- 13. #insiderDevTour Environment Preparation – VS 2019 • https://visualstudio.microsoft.com/zh-hant/vs
- 14. #insiderDevTour Environment Preparation – Enable Preview
- 15. #insiderDevTour Develop like using .NET Framework Version
- 17. #insiderDevTour Windows shipped App developer code Xaml Hosting API Inbox Xaml Controls WPF app WinForms app WPF XAML Host WinForms XAML Host WPF Control Wrappers WinForms Control Wrappers C++ Win32 app HWnd App code UWP Custom Controls WinUI 2.x Windows 10 Subsystems: DirectX, Kernel, drivers, device access, … 1507 1511 1607 1703 1709 1803 1809 1903 Xaml Framework Composition, Animation, Input OS code XAML Islands Components Recap
- 18. #insiderDevTour Windows shipped App developer code WPF app WinForms app WPF XAML Host WinForms XAML Host WPF Control Wrappers WinForms Control Wrappers C++ Win32 app UWP Custom Controls WinUI 3.0 Windows 10 Subsystems: Presentation platform, DirectX, Kernel, drivers, device access, … 1507 1511 1607 1703 1709 1803 1809 1903 Xaml Controls Xaml Framework & Xaml Host Composition, Animation, Input HWnd App code OS code XAML Islands Components Future
- 20. #insiderDevTour Try at home - Turn on Developer Mode
- 21. #insiderDevTour MSIX – New Packaging Format Never regret installing an app No machine rot! Auto updates Out of the box Easier distribution Store Network or Local file share HTTPS public URL Container based on Win10 Access to Windows 10 APIs that requires an App Id. MSIX Core Win7 support
- 22. #insiderDevTour Windows Platform Think Windows10, not UI Framework .NET Core 3 Open-source, faster, latest features MSIX New packaging format XAML Islands New UWP UI Controls on Win32 Recap
- 23. #insiderDevTour Some Resource • 「.net core 與 .net standard 實戰教學」 • https://blog.alantsai.net/tags/「net-core-與-net-standard-實戰教學」 • Sample code used for this session • https://github.com/microsoft/InsiderDevTourDemos19/tree/master/Sessions/desktopApps • Modernize your desktop apps • https://docs.microsoft.com/en-us/windows/apps/desktop/modernize/
- 24. #insiderDevTour You’ll learn: Learn more! Check out the lab for this session! • Sample code used in this session and more aka.ms/insiderdevtour-labs
- 25. #insiderDevTour Next up… Thanks! Please don’t forget to complete the survey! The Future is Now with ASP.NET Core 3.0 Edward Kuo
Editor's Notes
- #5: If you ever built a Windows App, you probably had to choose over one of these three platforms
- #6: But in fact, what you really want to target is Windows. Windows is the platforms. These options are just different UI framework options you have, when targeting Windows.
- #7: And even more, when you optimize your App to target Windows 10, you get even more innovations, APIs and benefits that the Windows 10 OS provides you. Think of Windows as the platform. The UI framework is just a preference
- #8: And again, all these options of UI frameworks are now open-source.
- #9: Open-Source More performant Great adoption and love More frequent updates
- #10: Every even numbered release is an LTS version. .NET 5 will unify all flavors of .NET (.NET Framework, .NET Core and Mono) in one, and Microsoft ship the first version of it in November 2020.
- #11: .Net Portability Analyzer helps you identify parts of your code that are or are not portable to .NET Core, giving you a full Excel report. First step is to migrate from package.json to PackageReference. Easiest way is to create an empty csproj running “dotnet new wpf” or “dotnet new winforms”. You can use the generated csproj as a starting point, migrating your PackageReferences from your old csproj, and going from there. Most projects should be pretty strait forward. If you need more information, follow the steps on the blog post. It is very complete.
- #12: 8 minutes 3:38 After demo 5 minutes 4:43
- #17: In 1993 Microsoft shipped Win32. WinForms came 9 years later, in 2002. In 2006 we shipped WPF, and in 2015, UWP. All the innovations we have on input, like inking, touch, and Pen, inside Windows, were only available if you used UWP. So Modern apps can only be developed with UWP? No! That’s what XAML Islands improves. It is the technology that enables developers to modernize their apps at their own pace, using the newest UWP controls in Win32, WinForms or WPF. Just as one example, the new Terminal you just saw uses XAML Island.
- #18: WinUI provides official native Windows UI controls and features for UWP apps. It is the easiest way to build great Fluent Design experiences for Windows, and it’s open-source! This is the Presentation Framework and the XAML Islands architecture. While WinUI 2 works on multiple version of the OS, XAML Islands works only on the newest version of Windows, the May 2019 Update. We heard the feedback that you wanted to use the greatest and latest controls, and even XAML Islands, on older version of Windows.
- #19: I’m happy to share that when we ship WinUI 3.0, you’ll be able to use controls that were shipped on newer version of Windows on older versions of Windows, all the way back to the version we released on July/2016, meaning you’ll be able to build your apps with the latest and greatest SDK and ship it without having to wait for your customers to update their Windows version. And that includes XAML Islands! WinUI 3.0 will greatly expand the scope of WinUI to include the full native Windows UI platform.
- #20: App Manifest to set the MaxTestedVersion property 4 minutes 4:47 After demo 6 minutest 4:52
- #22: New packaging format that replaces MSI and APPX.