.NET Core 3.0

[wriedmann]

Hi,

finally Microsoft has announced to support GUI with .NET Core 3.0.

I had expected they would do some enhanced WPF GUI and port it also to MacOS and Linux, but they have announced to make available WinForms and WPF windows on .NET Core 3.0, and only for Windows. The good notice is that they will make available also controls from UWP to WPF and WinForms.

That means that contrarily to what I expected WinForms has a future too, saving a lot of investments.
That makes a WinForms based VO GUI classes compatible library more important than ever, and we can expect to have a long live for our ported VO applications.

Wolfgang

[robert]

Wolfgang,

That means that contrarily to what I expected WinForms has a future too, saving a lot of investments.
That makes a WinForms based VO GUI classes compatible library more important than ever, and we can expect to have a long live for our ported VO applications.

Exactly what I thought when I heard this !

Robert

[rjpajaron]

Take note also of XAML Islands.
In later Channel 9 talks, Scott Hunter clarifies that WinForms/WPF support for .NET Core 3 may branded as desktop package or something. WinForms uses a lot of Windows API; and WPF also users DX9. Both are missing on .NET Core as of this moment. So, when this got ported.


I love it and keep me up all night just to watch everything on .NET, C#, ASP.NET.


.NET Core 3 support for Desktop Apps may be the beginning of the end of Windows only desktop .NET apps.

Take a peek on both videos. Scott Hunter mention something about I mention above.

https://www.youtube.com/watch?v=KAIJ3ezQb3c

https://www.youtube.com/watch?v=tkiPcCHGngY


--

Rene

[rjpajaron]

Take note also of XAML Islands.
In later Channel 9 talks, Scott Hunter clarifies that WinForms/WPF support for .NET Core 3 may branded as desktop package or something. WinForms uses a lot of Windows API; and WPF also users DX9. Both are missing on .NET Core as of this moment. So, when this got ported.


I love it and keep me up all night just to watch everything on .NET, C#, ASP.NET.


.NET Core 3 support for Desktop Apps may be the beginning of the end of Windows only desktop .NET apps.

Take a peek on both videos. Scott Hunter mention something about I mention above.

https://www.youtube.com/watch?v=KAIJ3ezQb3c

https://www.youtube.com/watch?v=tkiPcCHGngY


--

If I heard it right, it is subject for .NET and C# management team to decide whether to support .NET Core 3 desktop apps for Mac and Linux. There are possibilities, regardless, at least, .NET Core desktop apps is really possible outside of UWP. At this point, what is clearer that it will remain within Windows ecosystem which I believe is notch below than being great.

Rene

[wriedmann]

Hi Rene,

IMHO the most important notice for us that we have tons of legacy code is that our applications can continue to live under the .NET Framework.

If you need a cross platform GUI framework, look at Avalonia:

http://avaloniaui.net/

Wolfgang

[rjpajaron]

Hi Rene,

IMHO the most important notice for us that we have tons of legacy code is that our applications can continue to live under the .NET Framework.

If you need a cross platform GUI framework, look at Avalonia:

http://avaloniaui.net/

Wolfgang

Hi Wolfgang,

Not interested right now on anything outside .NET Framework and/or Core.

I am happy where my team are. Xamarin much covered our cross platform apps (iOS, Android and UWP).

But, I am really interested on the .NET Core port of WinForms/WPF. That is for our newer apps.
For now, best bet is WinForms/WPF for .NET Framework and put some stuff on UWP. However, with XAML Islands, I think there are lots of possibilities such as web controls that uses Edge instead of IE, putting UWP controls on WinForms/WPF. Very excited on the last build 2018. Best ever, for me!

-

Rene

[wriedmann]

Hi Rene,

if you are interested in an Edge control, please look at this post:

https://blogs.windows.com/msedgedev/2018/05/09/modern-webview-winforms-wpf-apps/

I'm already planning to check it out and post a sample here when it works.

Wolfgang

P.S. was awaiting this for some time now....

[rjpajaron]

Hi Rene,

if you are interested in an Edge control, please look at this post:

https://blogs.windows.com/msedgedev/2018/05/09/modern-webview-winforms-wpf-apps/

I'm already planning to check it out and post a sample here when it works.

Wolfgang

P.S. was awaiting this for some time now....

Hi Wolfgang,

Thanks for link. I did watch Kevin Gallo's presentation on this but the content is so dense, got no time to digest. I even tried to follow Ginny (one of the Build's principal MVP to follow, but I cannot hold of any of her presentation). I got drown for hundreds of contents to follow. I'd limit myself to some fun stuff of Mark Russinovich's piece on Azure and Blockchain and most on ASP.NET, C# and .NET (core 3.0).

Right now, I am waiting for X# runtime beta. Happily coding X# middle-ware assembly for my C# sync projects.


Regards,

Rene

[ic2]

Unfortunately I don't have time to watch hours of Build conference material but what I understand is that you draw a conclusion from something someone from Microsoft said about the future of Winforms.

I would like to warn you is that once Microsoft declares it is committed to something the end is nearby. Did they tell this about Winforms? Then it will disappear. Or did they tell it about WPF? Same.

Examples: "Microsoft is very much committed to WinPhone"
End last year: "Microsoft is very much committed to Cortana and a lot happened last year". In reality Cortana can't do less than last year (music recognition stopped working when they retired Groove music, to which BTW they were very much committed as they were to its predecessor Zune). If you like to read more about it see:
http://webwereld.nl/software/104562-hoe ... e-toekomst (Dutch only).

Just be careful with anything Microsoft promises to support.

Dick

[wriedmann]

Hi Dick,

sometimes you seem to take the rule of "advocatus diaboli" <g>....

When it comes to commitments (for any company) you have to look if this commitment makes sense to them.
The commitment to Windows Phone made no sense to Microsoft - it was the last try to save the platform. But that was evident at that time.

The commitment (or in this case better: the announcement) to make WinForms and WPF available in .NET Core 3.0 makes a lot of sense. Both are affirmed and widely used tecnologies, and many companies have made huge investments in them.
It makes sense to Microsoft because the adaption of them (not a rewrite!) takes much, much less effort than rewriting another new GUI library for .NET Core.

The first step was already made: the Edge control for both WinForms and WPF.

Wolfgang