Daniel Plaisted

Hi folks! I've made another update to the proposal: - Switch from using `bin` to `artifacts` - Put configurations in lower case in new output path format - Add details...

> > Switch from using bin to artifacts > > This will be a major breaking change and generate work for every other project out there. We should think twice...

Hi folks, Thanks for all the feedback so far. Based on some of the feedback, I think it would be a good idea to go back to using `bin` as...

> [#281 (comment)](https://github.com/dotnet/designs/pull/281#discussion_r1043982746) > > I hate to bring this up again, but I wonder if anyone has answered the questions I've brought up. Several of us have said "Personally"...

> I realize that `MAX_PATH` was a big issue in the past (I lived through it and hated every second of it lol), but at the same time I also...

Thanks for the feedback so far folks, it has been very helpful and I've updated the proposal accordingly. The main changes: - The new output format will for now not...

@dfederm Have a look at the updated proposal. It still puts everything in a root `.artifacts` folder by default, but also includes hooks that let you customize the output paths,...

Hi @Nirmal4G, Thanks for the feedback, and sorry for not responding earlier. I will try to do that now. As far as two top-level output paths, the design does not...

> Is there a mechanism to clean up pivot folders that are no longer relevant? For example, if you remove a target framework, there's a lingering folder that's no longer...

Hi folks, The artifacts path functionality will be in .NET 8 Preview 3. We're hoping that people will try it out and give us feeedback. The biggest question right now...