Jeff Kluge

Unfortunately, no. `CommonTargetsPath` is set by import `Microsoft.Common.props` and there's no single property that says you need to import the props at the top and the targets at the bottom....

Traversal projects don't really produce any output, do you think it would be okay to just disable the simplified output paths feature all together for them? ```xml false ```

Yes the only real output is the intermediate folder (obj) but the project itself doesn't output anything like an assembly (bin folder). The only other option I can think of...

@AndyGerlicher has assumed ownership of this repo

The original idea of dynamic skipping was for each project to indicate if it should be built. So obviously that works well if a target is run ahead of time...

Unfortunately, build ordering in a solution file is not a very good best practice. Since the ordering is only respected when building the solution file, this means that when you...

I believe what's happening is that when you run `dotnet test` against a solution file, it schedules the build differently. It appears that the `VSTest` target for `dotnet test` doesn't...

The Traversal logic is doing simple MSBuild scheduling by calling the `` task with the specified projects and indicating they should be built in parallel. MSBuild then takes over and...

The .NET SDK now disables itself if you're using Microsoft.Build.Artifacts: https://github.com/dotnet/sdk/pull/33470 I'm trying to get this pull request to work as well: https://github.com/microsoft/MSBuildSdks/pull/458

@dsplaisted can you answer @bording's question? https://github.com/microsoft/MSBuildSdks/issues/477#issuecomment-1734456952