Readit News logoReadit News
runesoerensen commented on Heroku Support for .NET 10   heroku.com/blog/support-f... · Posted by u/runesoerensen
oaiey · 3 months ago
.NET Framework was always called .NET Framework and not renamed from NET 4 to .NET Framework. There was a time where .NET was applied as a prefix/suffix to everything Microsoft released. Microsoft Windows Server .NET. that had nothing to do with the framework/CLR/programming platform but with Internet connected features.
runesoerensen · 3 months ago
Fair enough - I meant that, at least in Microsoft's own communication, they started more consistently referring to .NET Framework 4.x to differentiate it from first .NET Core and later .NET.

While it was always called .NET Framework, it was very commonly referred to simply as .NET (e.g. .NET 4.5) - and the "Microsoft .NET" logo was widely used in .NET Framework branding/marketing.

runesoerensen commented on Heroku Support for .NET 10   heroku.com/blog/support-f... · Posted by u/runesoerensen
jf · 3 months ago
I came here to see if AppHarbor was still running and was pleased to see this post :D
runesoerensen · 3 months ago
Hi Joel! I guess you could say AppHarbor's spirit lives on - ".NET on Heroku" feels like a pretty fitting successor to "Heroku for .NET", right?

Also, the AppHarbor blog is technically still running, so there's that :)

Hope you're doing well!

runesoerensen commented on Heroku Support for .NET 10   heroku.com/blog/support-f... · Posted by u/runesoerensen
runesoerensen · 3 months ago
I wrote this post - for anyone curious, Heroku's .NET support is built on our open source .NET Cloud Native Buildpack (CNB), which is written in Rust and produces standard OCI images.

You can use it anywhere, even locally, for free. The example in the post uses the .NET 10 file-based app feature we added support for today, so if you want to try the same functionality locally, you can do something like this:

  # Create a minimal .NET 10 file-based app
  echo 'Console.WriteLine("Hello HN");' > Hello.cs

  # Build an OCI image using the .NET CNB
  pack build hello-hn --builder heroku/builder:24

  # Run it with Docker
  docker run --rm -it --entrypoint hello hello-hn

  # Output:
  Hello HN
The "classic" Heroku buildpack shown in the demo video is just a thin wrapper around the CNB implementation: https://github.com/heroku/buildpacks-dotnet

runesoerensen commented on Heroku Support for .NET 10   heroku.com/blog/support-f... · Posted by u/runesoerensen
rk06 · 3 months ago
No, you are not alone.for non-tech population, it may make sense that .NET 5 is continuation of .NET 4. But the tech crowd knows .net 5 is to .net 4 is what angular 2 is to angular 1.

With .net 4 still in active use, the naming makes it harder

runesoerensen · 3 months ago
Might be more confusing when you consider that ".NET 5" is actually the continuation of ".NET Core 3.1", not ".NET Framework 4.x"[0].

Microsoft has historically been pretty bad at naming stuff (sometimes hilariously so, see Microsoft PlaysForSure[1] for an example - spoiler: it surely didn't play for long).

The rebranding from .NET Core 3.1 to .NET 5, and from .NET 4.x to .NET Framework, did make sense to me though - and increasingly so as development continues on ".NET > 5" with yearly releases, while ".NET Framework 4.x" is in maintenance mode.

[0]:https://learn.microsoft.com/en-us/dotnet/core/whats-new/dotn...

[1]:https://en.wikipedia.org/wiki/Microsoft_PlaysForSure

Deleted Comment

u/runesoerensen

KarmaCake day27294October 17, 2010
About
.NET at Heroku. Co-founder of AppHarbor. Hacker
View Original