# The Most Exciting Promise of .NET 5

**URL:** <https://devforum.okta.com/t/the-most-exciting-promise-of-net-5/17236>\
**Category:** Developer Blog Comments\
**Created:** [April 17, 2020, 3:20pm UTC](https://devforum.okta.com/t/the-most-exciting-promise-of-net-5/17236 "2020-04-17T15:20:39Z")\
**Posts on this page:** 20\
**Page:** 2

<div class="post-metadata">

**Author:** ![oktadev-blog](https://sea1.discourse-cdn.com/oktadev/user_avatar/devforum.okta.com/oktadev-blog/32/3422_2.png) [@oktadev-blog](https://devforum.okta.com/u/oktadev-blog)\
**Post date:** [April 21, 2020, 10:22am UTC](https://devforum.okta.com/t/the-most-exciting-promise-of-net-5/17236/21 "2020-04-21T10:22:55Z")

</div>

**odalet**

Winforms/WPF: I know it is - work in progress, kinda, supported with .NET Core 3.1, however on Windows only. Are you saying it will be supported on Linux/Mac as well with .NET 5?

---

<div class="post-metadata">

**Author:** ![oktadev-blog](https://sea1.discourse-cdn.com/oktadev/user_avatar/devforum.okta.com/oktadev-blog/32/3422_2.png) [@oktadev-blog](https://devforum.okta.com/u/oktadev-blog)\
**Post date:** [April 21, 2020, 10:30am UTC](https://devforum.okta.com/t/the-most-exciting-promise-of-net-5/17236/22 "2020-04-21T10:30:30Z")

</div>

**Alex Dresko**

Are you low on hard drive space? Please explain why file size is a problem, not why it’s different from what you’re used to.

---

<div class="post-metadata">

**Author:** ![oktadev-blog](https://sea1.discourse-cdn.com/oktadev/user_avatar/devforum.okta.com/oktadev-blog/32/3422_2.png) [@oktadev-blog](https://devforum.okta.com/u/oktadev-blog)\
**Post date:** [April 21, 2020, 10:40am UTC](https://devforum.okta.com/t/the-most-exciting-promise-of-net-5/17236/23 "2020-04-21T10:40:26Z")

</div>

**Xileer**

I do development on extremely low-spec systems (Think \<1GB total HD Space / \<128MB Linux Deployments) so every KB counts. The Mono installation on Linux gives us a large enough shared code repository that multiple .NET Framework applications remain viable (The entirety of Mono is \<5MB) and .NET development remains significantly faster than C++ development due to such.

---

<div class="post-metadata">

**Author:** ![oktadev-blog](https://sea1.discourse-cdn.com/oktadev/user_avatar/devforum.okta.com/oktadev-blog/32/3422_2.png) [@oktadev-blog](https://devforum.okta.com/u/oktadev-blog)\
**Post date:** [April 21, 2020, 10:40am UTC](https://devforum.okta.com/t/the-most-exciting-promise-of-net-5/17236/24 "2020-04-21T10:40:46Z")

</div>

**Peter Adam**

He spoke about SSD space, and yes, we are low on them.

---

<div class="post-metadata">

**Author:** ![oktadev-blog](https://sea1.discourse-cdn.com/oktadev/user_avatar/devforum.okta.com/oktadev-blog/32/3422_2.png) [@oktadev-blog](https://devforum.okta.com/u/oktadev-blog)\
**Post date:** [April 21, 2020, 10:41am UTC](https://devforum.okta.com/t/the-most-exciting-promise-of-net-5/17236/25 "2020-04-21T10:41:57Z")

</div>

**Xileer**

I made multiple edits post-submission so it’s understandable that that section was missed in the initial reading.

---

<div class="post-metadata">

**Author:** ![oktadev-blog](https://sea1.discourse-cdn.com/oktadev/user_avatar/devforum.okta.com/oktadev-blog/32/3422_2.png) [@oktadev-blog](https://devforum.okta.com/u/oktadev-blog)\
**Post date:** [April 21, 2020, 10:43am UTC](https://devforum.okta.com/t/the-most-exciting-promise-of-net-5/17236/26 "2020-04-21T10:43:28Z")

</div>

**Peter Adam**

But at least have mercy and do the GUI in something Windows-native.

---

<div class="post-metadata">

**Author:** ![oktadev-blog](https://sea1.discourse-cdn.com/oktadev/user_avatar/devforum.okta.com/oktadev-blog/32/3422_2.png) [@oktadev-blog](https://devforum.okta.com/u/oktadev-blog)\
**Post date:** [April 21, 2020, 10:43am UTC](https://devforum.okta.com/t/the-most-exciting-promise-of-net-5/17236/27 "2020-04-21T10:43:31Z")

</div>

**Xileer**

(Psst: Mono on Linux is a thing. Missing a few things - Sure - But it’s still definitely viable)

---

<div class="post-metadata">

**Author:** ![oktadev-blog](https://sea1.discourse-cdn.com/oktadev/user_avatar/devforum.okta.com/oktadev-blog/32/3422_2.png) [@oktadev-blog](https://devforum.okta.com/u/oktadev-blog)\
**Post date:** [April 21, 2020, 11:13am UTC](https://devforum.okta.com/t/the-most-exciting-promise-of-net-5/17236/28 "2020-04-21T11:13:14Z")

</div>

**José**

…or Mac-native. 🙂 The Windows interface next to the Mac is stupid! Microsoft can suck it, take a look the filename [https://www.youtube.com/wat…](https://www.youtube.com/watch?v=thc9iLZf0HQ "https://www.youtube.com/watch?v=thc9iLZf0HQ")

---

<div class="post-metadata">

**Author:** ![oktadev-blog](https://sea1.discourse-cdn.com/oktadev/user_avatar/devforum.okta.com/oktadev-blog/32/3422_2.png) [@oktadev-blog](https://devforum.okta.com/u/oktadev-blog)\
**Post date:** [April 21, 2020, 1:05pm UTC](https://devforum.okta.com/t/the-most-exciting-promise-of-net-5/17236/29 "2020-04-21T13:05:54Z")

</div>

**Joseph Adams**

Not to my knowledge. They are wrappers around GDI and DirectDraw respectively, and neither of these are being ported. This does leave a gaping hole IMO in terms of the cross-platform desktop app story. But, really, I think the logical direction is that even desktop apps are going to be built going forward using Web technologies. Winforms and WPF probably exist only to support legacy Windows desktop apps.

---

<div class="post-metadata">

**Author:** ![oktadev-blog](https://sea1.discourse-cdn.com/oktadev/user_avatar/devforum.okta.com/oktadev-blog/32/3422_2.png) [@oktadev-blog](https://devforum.okta.com/u/oktadev-blog)\
**Post date:** [April 21, 2020, 1:50pm UTC](https://devforum.okta.com/t/the-most-exciting-promise-of-net-5/17236/30 "2020-04-21T13:50:10Z")

</div>

**José**

Android is on its way… Bye Microsoft

---

<div class="post-metadata">

**Author:** ![oktadev-blog](https://sea1.discourse-cdn.com/oktadev/user_avatar/devforum.okta.com/oktadev-blog/32/3422_2.png) [@oktadev-blog](https://devforum.okta.com/u/oktadev-blog)\
**Post date:** [April 21, 2020, 1:50pm UTC](https://devforum.okta.com/t/the-most-exciting-promise-of-net-5/17236/31 "2020-04-21T13:50:51Z")

</div>

**odalet**

That’s exactly what I suspected. In a way the article is a bit misleading in not mentioning that.  
Concerning the trend toward web-based techs for desktop apps, sure there’s a trend: electron, blazor, webassembly… but I happened to play (only a bit) with Avalon UI. Seems something that could really replace WPF to me.

---

<div class="post-metadata">

**Author:** ![oktadev-blog](https://sea1.discourse-cdn.com/oktadev/user_avatar/devforum.okta.com/oktadev-blog/32/3422_2.png) [@oktadev-blog](https://devforum.okta.com/u/oktadev-blog)\
**Post date:** [April 21, 2020, 3:39pm UTC](https://devforum.okta.com/t/the-most-exciting-promise-of-net-5/17236/32 "2020-04-21T15:39:05Z")

</div>

**Mike**

LOL You must be kidding right? Until the Oracle and Google supreme court case is over, I don’t see anything like that even being possible. Even at that point I don’t see it happening.

---

<div class="post-metadata">

**Author:** ![oktadev-blog](https://sea1.discourse-cdn.com/oktadev/user_avatar/devforum.okta.com/oktadev-blog/32/3422_2.png) [@oktadev-blog](https://devforum.okta.com/u/oktadev-blog)\
**Post date:** [April 21, 2020, 6:24pm UTC](https://devforum.okta.com/t/the-most-exciting-promise-of-net-5/17236/33 "2020-04-21T18:24:14Z")

</div>

**StealthTech**

I agree with the legacy part of it. The move is to Xamerin or web technologies.

There is Xamerin.Forms GTK# (kind of)

[GTK# Platform Setup](https://docs.microsoft.com/en-us/xamarin/xamarin-forms/platform/other/gtk?tabs=windows "https://docs.microsoft.com/en-us/xamarin/xamarin-forms/platform/other/gtk?tabs=windows")

---

<div class="post-metadata">

**Author:** ![oktadev-blog](https://sea1.discourse-cdn.com/oktadev/user_avatar/devforum.okta.com/oktadev-blog/32/3422_2.png) [@oktadev-blog](https://devforum.okta.com/u/oktadev-blog)\
**Post date:** [April 22, 2020, 9:24am UTC](https://devforum.okta.com/t/the-most-exciting-promise-of-net-5/17236/34 "2020-04-22T09:24:24Z")

</div>

**WOBFIE**

"nullable reference"? Sorry, even don’t mention this sh\*\*t. We don’t need it. It made for indian monkeys to stop 'em making silly mistakes. We’re happy with C# 7.0 and have no plans to move on Core. Core is dead born child, born too late. MS had to think first when they made “Windows only .NET virtual machine” (I know, sounds like idiocity, but MS made it). Now we have tons of code and no any wish to port it to run… again on Windows. Sorry, MS but you’re morons who waste YEARS on a limited technology. Now we used to it and there is no reason to move on Core.

---

<div class="post-metadata">

**Author:** ![oktadev-blog](https://sea1.discourse-cdn.com/oktadev/user_avatar/devforum.okta.com/oktadev-blog/32/3422_2.png) [@oktadev-blog](https://devforum.okta.com/u/oktadev-blog)\
**Post date:** [April 22, 2020, 9:25am UTC](https://devforum.okta.com/t/the-most-exciting-promise-of-net-5/17236/35 "2020-04-22T09:25:35Z")

</div>

**WOBFIE**

Study at last how to spell it! XAMARIN.

---

<div class="post-metadata">

**Author:** ![oktadev-blog](https://sea1.discourse-cdn.com/oktadev/user_avatar/devforum.okta.com/oktadev-blog/32/3422_2.png) [@oktadev-blog](https://devforum.okta.com/u/oktadev-blog)\
**Post date:** [April 22, 2020, 9:27am UTC](https://devforum.okta.com/t/the-most-exciting-promise-of-net-5/17236/36 "2020-04-22T09:27:16Z")

</div>

**WOBFIE**

Android suxx for years. After WPF, development for Android looks like driving a horse after automatic car. I’m not surprised shmoogle has plans to abandon this “side library above the Linux”.

---

<div class="post-metadata">

**Author:** ![oktadev-blog](https://sea1.discourse-cdn.com/oktadev/user_avatar/devforum.okta.com/oktadev-blog/32/3422_2.png) [@oktadev-blog](https://devforum.okta.com/u/oktadev-blog)\
**Post date:** [April 22, 2020, 9:28am UTC](https://devforum.okta.com/t/the-most-exciting-promise-of-net-5/17236/37 "2020-04-22T09:28:22Z")

</div>

**WOBFIE**

Show me your “cross-platform” apps, dude! I promise not to laugh very long! :)))

---

<div class="post-metadata">

**Author:** ![oktadev-blog](https://sea1.discourse-cdn.com/oktadev/user_avatar/devforum.okta.com/oktadev-blog/32/3422_2.png) [@oktadev-blog](https://devforum.okta.com/u/oktadev-blog)\
**Post date:** [April 23, 2020, 11:49pm UTC](https://devforum.okta.com/t/the-most-exciting-promise-of-net-5/17236/38 "2020-04-23T23:49:23Z")

</div>

**Immo Landwerth**

TL;DR: it’s because Windows has no special handling for .NET Core.

On .NET Framework, your EXEs aren’t really EXEs. They are more like managed DLLs. When Windows starts a managed EXE, the OS finds & activates the correct .NET Framework runtime. The runtime then calls into your entry point (AFAIR this loader lives in C:\Windows\System32\mscoree.dll).

For .NET Core there is no OS provided loader. Instead, we deploy an EXE with native code which will find the correct .NET Core runtime, activates it, and then calls your entry point which sits in a class library next to it. The size of this native exe is ~180k, which is the fixed overhead you’re observing.

---

<div class="post-metadata">

**Author:** ![oktadev-blog](https://sea1.discourse-cdn.com/oktadev/user_avatar/devforum.okta.com/oktadev-blog/32/3422_2.png) [@oktadev-blog](https://devforum.okta.com/u/oktadev-blog)\
**Post date:** [April 23, 2020, 11:52pm UTC](https://devforum.okta.com/t/the-most-exciting-promise-of-net-5/17236/39 "2020-04-23T23:52:08Z")

</div>

**Immo Landwerth**

We’re closely working with Unity. They already adopted .NET Standard and they plan on moving to .NET 5++ eventually as well.

---

<div class="post-metadata">

**Author:** ![oktadev-blog](https://sea1.discourse-cdn.com/oktadev/user_avatar/devforum.okta.com/oktadev-blog/32/3422_2.png) [@oktadev-blog](https://devforum.okta.com/u/oktadev-blog)\
**Post date:** [April 23, 2020, 11:54pm UTC](https://devforum.okta.com/t/the-most-exciting-promise-of-net-5/17236/40 "2020-04-23T23:54:06Z")

</div>

**Immo Landwerth**

I’ve tried to explain our reasoning here: [https://github.com/dotnet/c…](https://github.com/dotnet/core/issues/2883#issuecomment-510302596 "https://github.com/dotnet/core/issues/2883#issuecomment-510302596")

[Previous page](https://devforum.okta.com/t/the-most-exciting-promise-of-net-5/17236.md?page=1)

[Next page](https://devforum.okta.com/t/the-most-exciting-promise-of-net-5/17236.md?page=3)
