u/NiveaGeForcein r/dotnet • Recommends
Modernizing Desktop Apps on Windows 10 with .NET Core 3.0 and much more
0:00 / 0:00
Modernizing Desktop Apps on Windows 10 with .NET Core 3.0 and much more : Build 2018
Microsoft Developer
700K subscribers • 17 videos on Hallway
- Recommended by 1 person: 1 in engineering communities.
- Made by the vendor. The company whose product it covers made or sponsored it.
- May be out of date. The tools, versions or practices it shows have likely moved on.
Intermediate. Assumes working knowledge.
31K views8 years ago1 recommendation
Systems programmingProgramming languagesC# and .NETOperating systems
A Microsoft Build 2018 session on modernizing WPF and Windows Forms applications using .NET Core 3.0 and Windows 10 features.
Come learn about the future of your WPF & Windows Forms applications. Windows, .NET and Visual Studio are making it easy to incrementally modernize your existing applications with Windows 10 features. Containerize your application for compatibility and installation isolation, take advantage of the new app local .NET Core 3.0 runtime and begin integrating new Windows 10 UI features with just a few clicks in Visual Studio. Modern applications are deeply connected to the people you work with and know which devices you’re using. We will cover the ways which M365 and the Microsoft Graph allow your existing application to connect users and help them complete tasks.Why it's here
1 person recommends thisu/pjmlpin r/dotnet • Mentions
On “What are you guys looking forward to at .NET Conf 2018?”
It was announced at BUILD 2018.
link to this video
https://blogs.msdn.microsoft.com/dotnet/2018/05/07/net-core-3-and-support-for-windows-desktop-applications/
The main items is to make possible to run Windows Forms, WPF, EF6 on .NET Core, on Windows, as those developers keep ignoring .NET Core due to lack of support.
Microsoft wants that in the very long run, .NET Core replaces .NET Framework in all possible scenarios.
.NET Framework is not going away anytime soon, as some of the changes required to bring to bring those stacks into .NET Core are not backwards compatible, additionally they don't plan to migrate deprecated or very Windows specific features.