It's never been a more exciting time to be a .NET developer. With .NET (formerly known as .NET Core) approaching its 10-year anniversary this November, the platform has evolved into a powerful, cross-platform ecosystem, embracing modern development practices and powering a vast array of applications.

Today, we're thrilled to announce that .NET support on Heroku, previously in beta, is now Generally Available (GA), marking a significant milestone for .NET developers on our platform. We want to thank our beta users for their invaluable feedback, which has helped us to refine and enhance the .NET experience on Heroku.

Heroku's commitment to developer productivity shines through in its powerful buildpack system. They handle the heavy lifting of building your app, letting you focus on what matters most: writing code. A prime example is the Heroku Java buildpack, a versatile tool that simplifies deploying Java applications, especially those built with popular frameworks like Spring Boot, Quarkus, and Micronaut.

One of the core strengths of Heroku buildpacks is their automatic nature. They intelligently detect your application's language and framework, fetching the necessary build tools and configuring the Heroku platform to run your app seamlessly. This means no more wrestling with server...

We’re excited to announce that official support for .NET on Heroku is entering public beta starting today. Developers can now build and deploy applications in C#, F#, and Visual Basic, using frameworks like ASP.NET Core and Blazor, all with the simplicity and flexibility of the Heroku platform.

.NET has long been one of the most requested frameworks to join Heroku’s lineup, and for good reason. Known for its power and versatility .NET enables developers to build everything from high-performance APIs to complex, full-stack web applications and scalable microservices. Now, developers can combine .NET’s capabilities with Heroku’s streamlined platform for a first-class developer experience.

At Heroku, we believe the best choices are the ones you don't have to make. That’s why we’re thrilled to announce the preview release of Heroku Cloud Native Buildpacks. Our Cloud Native Buildpack (CNB) offering brings the beloved Heroku language and framework experience to your local machine and beyond. Whether you're coding in Ruby, Node.js, Python, PHP, Go, Java, or Scala, Heroku’s set of opinionated CNBs streamline the process of building and managing containerized applications as OCI-compliant images. Developed and maintained by our language experts, these buildpacks ensure a native experience for each supported language ecosystem and frees you up to focus on what matters:...

YAML files dominate configuration in the cloud native ecosystem. They’re used by Kuberentes, Helm, Tekton, and many other projects to define custom configuration and workflows. But YAML has its oddities, which is why the Cloud Native Buildpacks project chose TOML as its primary configuration format.

What is a TOML File?

The TOML file format is a simple and human-readable configuration file format used to define key-value pairs. TOML, which stands for “Tom’s Obvious, Minimal Language,” was designed to be easily understood by humans and computers. You can learn more about TOML from the official documentation, but a simple buildpack TOML file looks like this: