# The Most Exciting Promise of .NET 5 **URL:** \ **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:** 7\ **Page:** 3
**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 24, 2020, 3:41am UTC](https://devforum.okta.com/t/the-most-exciting-promise-of-net-5/17236/41 "2020-04-24T03:41:08Z")
**Xileer** Aaah, I was unaware of the bundled native exe. Is there any specific reason for the disproportionate file-size of what is effectively a loader, and is there any way to specify these options manually upon compilation to avoid using it (Or to use a lighter version of it, or have it shared between multiple applications)? It seems odd that there’s a way to offload this common instruction set to a external location in .NET Framework (mscoree.dll in Windows, something included in Mono on Linux) with no obvious way (That I am aware of) to do so with .NET Core. If you’re already installing a type of “.NET Core Framework” to the operating system (The .NET Core Runtime), should this not include some form of native handling? ---
**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 24, 2020, 5:30am UTC](https://devforum.okta.com/t/the-most-exciting-promise-of-net-5/17236/42 "2020-04-24T05:30:43Z")
**akshay2000** Regardless of whether you’re developing for low spec systems or not, I think it is always good to go against unnecessary bloat. ---
**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 24, 2020, 7:27am UTC](https://devforum.okta.com/t/the-most-exciting-promise-of-net-5/17236/43 "2020-04-24T07:27:10Z")
**sadashiv** Yes, great explanation. Perfect. But, still I personally feel, when you name it as again .Net 5.0, I feel like Microsoft is coming back to previous editions naming. Because I don’t think like as it was .Net 4.5 much before .Net Core release, now if Microsoft names it as .Net 5.0, I think most of .Net framework users may feel like, .Net 5.0 is not that brand new, as they were very much familiar with previous .Net 4.5 versions. Considering only 0.5 difference between versioning of .Net 4.5 and .Net 5.0. When Microsoft released with name .Net Core, I think everybody felt, it is brand new framework and excited about its modern nature of platform independence and open source. It is just my personal opinion that, already .Net Core is branded as futuristic .Net framework, if I am not wrong, the feeling wouldn’t be same when you are again back to .Net 4.5 or higher like .Net 5.0. I would suggest to go with .Net Core versions as Microsoft going currently like .Net Core 2.0/3.0 and may be .Net Core 4.0/5.0 and so on. ---
**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:** [May 9, 2020, 2:38pm UTC](https://devforum.okta.com/t/the-most-exciting-promise-of-net-5/17236/44 "2020-05-09T14:38:11Z")
**Frédéric Forjan** are you considering all engineering apps are going to be move to web? Visual Studio first ? ---
**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:** [October 1, 2020, 2:01pm UTC](https://devforum.okta.com/t/the-most-exciting-promise-of-net-5/17236/45 "2020-10-01T14:01:57Z")
**Homero Lara** What about UWP? Is it not making it into .Net 5? or did I missing something? ---
**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:** [October 1, 2020, 2:07pm UTC](https://devforum.okta.com/t/the-most-exciting-promise-of-net-5/17236/46 "2020-10-01T14:07:38Z")
**Homero Lara** oops…never mind, I see it in the graphic above…my mistake. ---
**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:** [July 20, 2021, 7:48am UTC](https://devforum.okta.com/t/the-most-exciting-promise-of-net-5/17236/47 "2021-07-20T07:48:42Z")
**TechAffinity Consulting** Great blog about .Net. Its very informative and full of knowledge. [Previous page](https://devforum.okta.com/t/the-most-exciting-promise-of-net-5/17236.md?page=2)