runesoerensen

2 saat öncediscuss

They're using/testing a few different versions. I used the front page title at the time I shared the link (which has now been changed to the first title you mentioned)

runesoerensen

8 ay öncediscuss

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

8 ay öncediscuss

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

8 ay öncediscuss

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

8 ay öncediscuss

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

runesoerensen

7 yıl öncediscuss

More info in the press release https://www.apple.com/newsroom/2019/06/the-new-ipados-powers...

runesoerensen

9 yıl öncediscuss

Intel response https://newsroom.intel.com/news/intel-responds-to-security-r...

runesoerensen

9 yıl öncediscuss