Rich Lander

@jaredpar - I suspect that's right. After using git all the time, the dashes are starting to feel quite natural.

Will ask for help for this to be routed.

It could be useful to do perf tests for this with big and small projects. I assume `--no-restore` and `--no-build` are up to that task. We'd want to do that...

@DamianEdwards was telling me that this "container experience" exactly maps to "CI experience". The patterns and needs are identical. I can see that.

Yes. That scenario exactly matches what I'm hoping to improve.

> insufficient to get accurate package information This is true but also the state of the art, to some degree. With `docker build`, you have a few choices (most to...

> That doesn't seem worth the cost of increasing the likelihood of an inconsistency failure in a later step, to me. Avoiding a failure due to inconsistency is a motivator...

All true. Perhaps we need to find some better samples to point to that add additional MSBuild assets. @glennc and I have been talking about this exact issue for 5+...

With `docker build`, the need for a separate restore step is pretty inherent.

That seems complementary. Even if we generate a Dockerfile, we want it to be pretty, understandable and easily editable. I'm proposing making the SDK work well for immutable environments. That...