Andrew Stakhov

So I've built something that helps with this that was contributed to project SteelToe. It allows tasks to be bundled with app and launched via special command argument. Ef migration...

@RSuter want to bump this again, we're trying to use the library for integration with Kubernetes which currently doesn't support $refs. https://github.com/kubernetes/kubernetes/issues/54579

It's not ideal, but this might be a case for a new "advanced fat builder" that includes key tooling from each ecosystem available to buildpacks (latest .net core SDK, maven/gradle)....

This would tackle just one specific scenario and will continue to remain brittle. Here are scenarios where it wouldn't work: - `Directory.Build.props` may appear at multiple levels along the tree...

Instead of adding stuff to the builder, is there a reason why dotnet buildpacks cannot bundle and use `MSBuild` during `detect` phase? For example, Jetbrains free MSBuild redistributable is only...

BTW, I'll highlight that on TAS (v2), you already have dotnet sdk inside buildpack and what I'm proposing can be done for cloud foundry specific dotnet buildpack. For V3 (CNBs),...

I've started working on this and pretty much done, EXCEPT I'm blocked by the fact that `Docker.DotNet` doesn't expose the necessary argument to keep tarball's UID/GID. I've raised an issue...

If this issue is tackled, I recommend this be an option rather than the default behavior. There are existing demos that rely on the presence of SDK in a container...

Why do you need multiple version lines? We're simply talking consistency in incrementing major/minor/patch numbers based on the kind of changes that went into buildpack release On Tue, Mar 21,...

I would really love to see support for aggregates acting as command handlers, as frequently it just wants to modify itself in response to some command. Axon framework does this....