Bring back PublishDotnetWatch

[tmat]

Revert parts of #47767, which broke inner dev loop for dotnet-watch tests.
dotnet-watch project build needs to deploy to redist directory, so that any updates to dotnet-watch are picked up by dotnet-watch tests.

[Copilot]

Copilot wasn't able to review any files in this pull request.

Files not reviewed (4)

• src/BuiltInTools/dotnet-watch/dotnet-watch.csproj: Language not supported
• src/Layout/redist/targets/Directory.Build.targets: Language not supported
• src/Layout/redist/targets/GenerateLayout.targets: Language not supported
• src/Layout/redist/targets/PublishDotnetWatch.targets: Language not supported

[tmat]

@ViktorHofer

[ViktorHofer]

Redist.csproj composes the SDK's sdk folder by pulling artifacts from all of the repo local sdk tools, not via a push model. Why is dotnet-watch different here?

To me this sounds like a test project setup issue. I.e. see dotnet.Tests.csproj:

sdk/test/dotnet.Tests/dotnet.Tests.csproj

Lines 19 to 22 in 7601b9c

	<!-- Use layout folder for the output folder, to support in-process tests which expect to be running
	on a valid layout. -->
	<OutputPath>$(ArtifactsBinDir)redist\$(Configuration)</OutputPath>
	<AppendTargetFrameworkToOutputPath>false</AppendTargetFrameworkToOutputPath>

That directly pushes into sdk's testhost folder so that the bits are always fresh. I don't see that happening in dotnet-watch.Tests.csproj: https://github.com/dotnet/sdk/blob/7601b9cae2f49701609df537fe81ae73425109ed/test/dotnet-watch.Tests/dotnet-watch.Tests.csproj