Michael Simons

@joeyaiello - Which of these scenarios require entry entrypoint script versus simply defining the ENTRYPOINT to be pwsh? In the long term, it feels like avoiding the entrypoint script would...

This is something the .NET project recently encountered as it has a dependency on Application Insights. Applications Insights is included in the .NET build dependency graph when "source building" for...

I can imagine scenarios in which you want to reference a layer via a name (e.g. a tag) rather than digest so that consumers can pick up the latest bits...

> IK that @MichaelSimons had some offline questions about the pipeline changes, so should I wait to merge this until we close out on that discussion? I don't think waiting...

I have a small proposal to the docker-tools namespace: `Microsoft.DotNet.Docker.Tools.FilePusher`. To me `DockerTools` should be one pascal cased word. Is it the source repo. It is a single concept much...

@T-Gro - This was something you are familiar with and could pick up? I had talked to Kevin about it and he asked me to log this issue.

I am not familiar with it either. It was a conversation I asked Kevin about because it has to be source-built because it is referenced by the SDK. It is...

I can help cleanup the source-build infra to support this. These are the references found in source-build-reference-packages. I wouldn't expect any references in dotnet/fsharp - this is an SDK thing....

This isn't a source-build issue. Transferring to installer.

This is not as straight forward as I initially thought. I don't think we want to add `ENV PATH="${PATH}:/root/.dotnet/tools"` as this will affect all users. Having `/root/.dotnet/tools` on the path...