Chet Husk

PATH looks good from those screenshots, but `dotnet --info` from both the terminal as well as VSCode's built-in terminal would be useful info to have.

Thanks @jrdodds, this is the definitive summary of the MacOS issues. I agree that we should not set any paths on /etc/paths.d that are user-specific. If we want to maintain...

> You might consider the example of HomeBrew. The brew command has a shellenv argument. A dotnet shellenv that is eval'd could return an export line to add the tools...

I agree with @jrdodds - the multi-user aspect is _why_ we haven't done this very simple change this entire time. I still maintain that the correct thing to do is...

I've got some code changes that check for recursive schemas in arrays by investigating the keys present on the `schema.['items']` compared to the current `schema`, but would love a better...

Can you provide the output of running `dotnet --info`? That will help diagnose the setup of your current .NET SDK installation.

There's also prior art for nunit/mstest/etc to accept a small DSL for test case selection in the 'filter' parameter. There are docs on this here: https://learn.microsoft.com/en-us/dotnet/core/testing/selective-unit-tests?pivots=mstest

This _may_ be a point in time problem - the 7 SDK on the distro feeds matches to the latest release (7.0.17 from 3 days ago) but the 6 SDK...

@AraHaan / @ProVega - are you able to try the change that @rokonec mentioned above and take a binlog to compare/contract the time spent in `GetCopyToOutputDirectoryItems` across your projects?

is the `dotnet --info` you've provided from the host that's failing? How have you installed .NET on this host? Which packages and feeds specifically?