.NET buildpack process type naming convention updated
Change effective on 17 April 2025
The .NET buildpack now uses a new format for default process type names. When no Procfile is present, automatically detected process types will be lowercased with hyphens replacing spaces, dots, and underscores.
Apps that define process types with a Procfile are not affected by this change. Apps deployed to Heroku’s Fir generation already use the new naming convention.
For apps deployed to Heroku’s Cedar generation, this may cause (non-web) worker dynos to be removed if the process type changed. Here are some examples showing how process types derived from .NET project file names are changed:
| Project File | Previous Process Type | New Process Type | Notes |
|---|---|---|---|
EmailWorker.csproj |
EmailWorker |
emailworker |
All letters are lowercased |
Email.Worker.csproj |
Email.Worker |
email-worker |
Dots replaced with hyphens |
Email Worker.csproj |
EmailWorker |
email-worker |
Spaces replaced with hyphens |
Email_Worker.csproj |
Email_Worker |
email-worker |
Underscores replaced with hyphens |
A warning is written to the build log when deploying apps that may need to scale up worker dynos following this change. web processes will continue to run as expected.
See the Dev Center documentation for more information on automatic process type detection.