Closed joefitzgerald closed 8 years ago
Why couldn't this also run console apps?
By not supplying core you run the risk of someone thinking this might apply to legacy .NET, or some kind of legacy mono app.
Using that line of reasoning we should have a java-8-buildpack to avoid confusion that it does not run 1.4 apps.
Apps can be started with --no-route and work against a message broker (e.g. RabbitMQ).
I vote for dotnet-core-buildpack
I vote for dotnet-core-buildpack
Technically the buildpack does pass a parameter to kestrel through the command-line right now giving it a server-urls parameter, this is something specific to a web app. Even with that parameter being passed, console apps could still run but they would receive those parameters from the command-line.
@degrim noted. I suppose the question isn't so much the current state, but what the buildpack aspires to be? I think it should allow apps to start with or without a (HTTP/S) route, particularly given future TCP routing capabilities.
@joefitzgerald I think before the changes in RC2 to use the .Net CLI, it didn't make sense for this buildpack to also try to support console apps. But now that ASP.Net Core runs on top of the same CLI as .Net Core console apps, it makes a little more sense to accommodate this scenario as well.
Using that line of reasoning we should have a java-8-buildpack to avoid confusion that it does not run 1.4 apps.
That's not entirely true, this buildpack supports ASP.Net Core (and now .Net Core console apps?) which is a different product than ASP.Net and Classic ASP. ASP.Net 1.0 released in 2002, ASP.Net Core 1.0 releases later this year.
@degrim yes, @autodidaddict and I hashed it out via Slack and I agree - core
should be part of the name.
Console apps do indeed work with --no-route, so my vote would be for dotnet-core-buildpack.
buildpack renamed
🎉
Because ASP.NET 5 !== what this is anymore...
Potential name options:
(:+1: for my vote)