Use Directory.Build.props/targets

[natemcmaster]

We've started using Directory.Build.props/targets across aspnet repos to reduce the duplication between csproj files, and reduce the amount of boilerplate code required to add new projects and tests.

[SteveSandersonMS]

Thanks Nate! Mostly this looks great.

As per my inline comment, could we go back to having each of the src projects declare its own values for the following independently?

 <ItemGroup> <None Remove="node_modules\**\*" /> <EmbeddedResource Include="Content\**\*" /> </ItemGroup> <Target Name="PrepublishScript" BeforeTargets="PrepareForPublish" Condition=" '$(IsCrossTargetingBuild)' != 'true' "> <Exec Command="npm install" /> <Exec Command="node node_modules/webpack/bin/webpack.js" /> </Target> 

Apart from that this looks good to me!

[SteveSandersonMS]

I'm not keen on this or any of the following lines in this csproj being moved out into Directory.Build.props, because:

1. It's hard to reason about which node_modules or Content files are being included/excluded when the paths aren't even relative to the file that's referencing them
2. It makes an assumption about conventions for inclusion/exclusion and prepublishing always being the same across every project in src, which isn't guaranteed. Although they might all happen to follow the same conventions today, there's no reason to believe that should always be so. Not all of them should necessarily have a Content directory, use node_modules, etc.

So I would prefer not to deduplicate these values, but rather keep the src projects equivalently decoupled as they were before.

[natemcmaster]

Sounds good. I'll revert this piece of the change.

[natemcmaster]

🆙 📅

[natemcmaster]

I think I address your feedback, so I'm going to merge this so I can get #1236 in too. If there was anything I missed, let me know and I'll fix it.