Cross platform WPF


#123

Yeah @Ziriax Noesis is where it is at, ATM IMO (LOL). It has recently released v2.0 and has a pretty decent Xaml model. They have working markup extensions in their C++ version with managed C# support on the way. It is free for indie developers, as well.

Also, I think this is pretty big news, but it was recently announced that Mono is porting to WebAssembly. So that would essentially put everything back together again as far as a cross platform .NET solution goes. Since Noesis runs on Mono, then it would benefit from the port.

http://forums.dotnetfoundation.org/t/wasm-asm-js-plans-projects/1947/4

Additionally Avalonia continues to be in the mix and they will benefit from the Mono port to WebAssembly as well.


#124

Uno (Cross platform UWP) is probably one of the best single look across devices UI for C# / .NET there is as its building on top of work MS has already done. Wish MS could support this proj.


#125

We need an official port from Microsoft, not some reverse engineered solution.


#126

You will have to be patient as .NET Core is being prepared and WPF will be part of this version.
See .NET Core 3 and Support for Windows Desktop Applications
And yes, that would be the official port. There will be a Core 3 preview this year and a definite version in 2019. These things take time to be developed.
Unfortunately, WPF will stay Windows-dependant. Linux and Apple are not likely to be supported.


#127

.NET Core 3 disgusts me, as I gather Microsoft is divvying up .NET platforms into first and second class citizens. That more or less destroys the entire reason for having a multi-platform framework in the first place.


#128

WPF is not cross platform. .NET Core 3.0 isn’t really solving a problem other than getting everyone on a single runtime.


#129

May the porting begin!!
For anyone who does or is focused on C# UI dev like the Avalonia proj or the UNO proj, the projects below should maybe just be directly supported and ported. I did not see this coming.

WPF: https://github.com/dotnet/wpf
WinUI: https://github.com/Microsoft/microsoft-ui-xaml
WinForms: https://github.com/dotnet/winforms


#130

Also if someone makes a visual WPF editor for VS Code that would be epic.


#131

Everyone explains .NET Core as a multi-platform version of .NET. If you start breaking this paradigm by introducing stuff which are merely wrappers of closed proprietary Windows stuff you are effectively destroying this promise.

Also, the new stuff only works on the Windows platform, not on any other platform. This sucks.


#132

Not if its a folk of the project reworked to address the issues you said.
WPF needs to be replaced yes but it could just be replaced with a folk allowing large portions of existing code to just work. Just needs to be looked at and assessed.

I did get a little over excited knowing WPF was now open source…


#133

No, WPF is not being open-sourced. What’s open sourced is the .NET wrapper to access WPF from .NET Core 3.0, not WPF itself. Idem WinForms, it’s just a wrapper that’s being open-sourced.

Probably some PHB at Microsoft decided that open-sourcing WPF would be too much of a risk, as it could undermine Windows’ market share.


#135

No, WPF is actually being open sourced, there’s no “wrapper”.

The Windows technologies that are used by WPF (like DirectX) are not being open sourced, but those are not part of WPF itself.


#136

I’ll believe it when I see it.

Besides, why didn’t they make WPF cross-platform by replacing the DirectX calls with corresponding OpenGL / Vulkan calls? Now they’re making it someone else’s problem.

In addition, they shouldn’t have muddled the waters by releasing WinForms for .NET Core 3, which IS a wrapper. Cross platform WPF is the only thing anyone ever needs.


#137

You can see for yourself: https://github.com/dotnet/wpf/. It’s not all there yet, but is any of the code that is there the “wrapper” you mentioned?

Because they believe it would be vast amount of work that would not be worth it, because people don’t want Windows-style applications on other OSes.


#138

I still believe it’s a wrapper. Why? Because the code released so far is all C# and I’m pretty sure that WPF was written in C++, since it’s used in both Visual Studio and Microsoft Office (and I’m sure both of those are written in C++).

But we’ll see if I’m right next year when they release the bulk of the code. So far, they’ve only released boiler plate code.


#139

Good point, but AFAIK Silverlight is only a subset of WPF. And a different branch (think cousin) at that.


#140


They just haven’t released all the source code yet.


.NET Foundation Website | Blog | Projects | Code of Conduct