At this point, no group in the Mono project has plans to implement Windows Presentation Foundation APIs as part of the project.
We do not have any plans because the project is too large and there has not been any serious interest from the community to make this effort move forward.
Introducing CrossOver Chrome OS! Run Windows programs that are not available in the Google Play store alongside mobile apps. Scrap remote sessions with multiple users. Run utility software like Quicken and Microsoft Office, or DirectX games, like Wizard101. And bonus: Games from your Steam library will run with CrossOver Chrome OS at native speeds. With 1 billion devices running Windows 10, and used in Microsoft's own industry applications, WinUI continually expands to meet the needs of every modern device. The Future of Windows Development It provides a way to gradually migrate existing apps written in familiar technologies like MFC, WinForms, and WPF, allowing you to move these.
Some bits were implemented for WindowsBase and they are distributed with Mono (mostly because System.IO.Packaging is part of WindowsBase). Various classes and stubs were developed and live in the Olive module.
At this point, we strongly suggest that users interested in WPF adopt Xamarin.Forms instead as it offers a rich set of cross platform APIs and features (and has a WPF driver too). What si the app ai on mac.
Currently AvaloniaUI is an initiative that is focused to mirror the WPF project but is multi-platform and a dialect.
Silverlight implemented a subset of the WPF APIs and was available on Windows, macOS; and through our own open source effort Moonlight it was available on Linux and other Unix systems. Silverlight does not have all the capabilities of WPF, but both technologies are converging API-wise. Silverlight could be used outside of the browser, and Moonlight can be configured to be used with the full .NET API outside of the browser. These days, there’s a project that is trying to resurrect Silverlight using WebAssembly: it’s called OpenSilver.
Maybe you already heard or read about the fact that Microsoft brings WinForms and WPF to .NET Core 3.0. Maybe you already saw the presentations on the Connect conference, or any other conference or recording when Scott Hanselman shows how to run a pretty old WPF application on .NET Core. I saw a demo where he run BabySmash on .NET Core.
Wpf App Template
BTW: My oldest sun really loved that BabySmash when he was a baby :-)
You did not hear, read or see about it?
![]() WPF and WinForms on .NET Core?
I was really wondering about this step, even because I wrote an article for a German .NET magazine some months before where I mentioned that Microsoft won't build a UI Stack for .NET Core. There where some other UI stacks built by the community. The most popular is Avalonia.
But this step makes sense anyway. Since the .NET Standards moves the API of .NET Core more to the same level of .NET Framework, it was a question of time when the APIs are almost equal. WPF and WinForms is based on .NET Libraries, it should basically also run on .NET Core.
Wpf On Mac OsDoes this mean it runs on Linux and Mac?
Nope! Since WinForms and WPF uses Windows only technology in the background, it cannot run on Linux or Mac. It is really depending on Windows. The sense of running it on .NET Core is performance and to be independent from any framework. .NET Core is optimized for performance, to run superfast web applications in the cloud. .NET Core is also independent from the installed framework on the machine. Just deploy the runtime together with your application.
You are now able to run fast and self-contained Windows desktop applications. That's awesome, isn't it?
![]()
Good I wrote that article some months before ;-)
Anyways..
The .NET CLI
Every time I install a new version of the .NET Core runtime I try
dotnet new and I was positively shocked about what I saw this time:
You are now able to create a Windows Forrms or a WPF application using the .NET CLI. This is cool. And for sure I needed to try it out:
Photo editor merge two photos. And yes, it is working as you can see here in Visual Studio Code:
And this is the WinForms project in VS Code
Running
dotnet run on the WPF project:
And again on the WinForms GUI:
IDE
Visual Studio Code isn't the right editor for this kind of projects. If you know XAML pretty well, it will work, but WinForms definitely won't work well. You need to write the designer code manually and you don't have any designer support yet. Maybe there will be some designer in the future, but I'm not sure.
The best choice to work with WinForms and WPF on .NET Core is Visual Studio 2017 or newer.
Last words
Disk diag mac app. I don't think I will now start to write desktop apps on .NET Core 3, because I'm a web guy. But it is a really nice option to build apps like this on .NET Core.
BTW: Even EF 6 will work in .NET Core 3, that means you also don't need to rewrite the database access part of your desktop application.
As I wrote, you can now use this super fast framework and the option to create self contained apps. I would suggest to try it out, to play around with it. Do you have an older desktop application based on WPF or WinForms? I would be curious about whether you can run it on .NET Core 3. Tell me how easy it was to get it running on .NET Core 3.
Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |