Customers want to be able to run dotnet publish themselves within their CI/CD pipeline and use the artifacts from that for testing etc, and then deploy those artifacts to Google Cloud Functions (etc) without having to upload the source code and rebuild it.
This is a little like the Java support for deploying existing jar files.
The buildpack could check for the presence of Xyz.deps.json and Xyz.runtimeconfig.json files to detect this situation. (Along with a lack of csproj/vbproj/fsproj files.)
Customers want to be able to run
dotnet publish
themselves within their CI/CD pipeline and use the artifacts from that for testing etc, and then deploy those artifacts to Google Cloud Functions (etc) without having to upload the source code and rebuild it.This is a little like the Java support for deploying existing jar files.
The buildpack could check for the presence of
Xyz.deps.json
andXyz.runtimeconfig.json
files to detect this situation. (Along with a lack of csproj/vbproj/fsproj files.)