Build acceleration for deps.json and runtimeconfig.json

[KirillOsenkov]

I'm not sure if it's a bug or not, but if you have two projects, P1 and P2, P2 references P1, and P1 is an .exe project, should build acceleration copy P1.deps.json and P1.runtimeconfig.json to the P2 output directory when P2 is up-to-date?

I'm not seeing the deps.json and runtimeconfig.json files added in CollectCopyToOutputDirectoryItemDesignTime:

project-system/src/Microsoft.VisualStudio.ProjectSystem.Managed/ProjectSystem/DesignTimeTargets/Microsoft.Managed.DesignTime.targets

Line 509 in 9b28338

Name="CollectCopyToOutputDirectoryItemDesignTime"

Same question for .exe.config for .NET framework .exe projects I guess?

[KirillOsenkov]

Also for .dll file references that don't come from project references, the .pdb file doesn't seem to be included? MSBuild copies both the foo.dll and the foo.pdb if you use a , but I'm only seeing foo.dll in the CopyToOutputDirectoryItems.

Not sure if this is expected.

I'm trying to write a validator that checks that all files that were present in the output directory are accounted for by build acceleration. If there is a file that got there because it was previously copied by MSBuild, but build acceleration doesn't know about it, it means we have a gap in coverage.

I can imagine scenarios where the reference pdb is now stale and is no longer matching the .dll.

[KirillOsenkov]

Also .dll.config and .runtimeconfig.dev.json