xcopy-msbuild is an artifact of the past. It was created to update msbuild outside of the VS schedule. Now that VS releases on a predictable monthly schedule there's no need for it anymore. Additionally, Arcade now targets .NETCoreApp for msbuild tasks only. Previously, xcopy-msbuild had to be updated for SigningValidation to work. That dependency is now gone and none of the tasks need a newer msbuild or VS version anymore.
xcopy-msbuild is a broken component. It doesn't work in certain scenarios as pieces are missing (i.e. fsharp or vcxproj targets). Updating it is a mundane, manual process and was handled by dnceng. Though, dnceng shouldn't be responsible for deploying msbuild.
Using it has resulted in more problems than the benefits that it brings. As part of the msbuild team, I absolutely want to see it gone.
There aren't many hits: https://github.com/search?q=repo%3Adotnet%2Farcade+xcopy&type=code
xcopy-msbuild is an artifact of the past. It was created to update msbuild outside of the VS schedule. Now that VS releases on a predictable monthly schedule there's no need for it anymore. Additionally, Arcade now targets .NETCoreApp for msbuild tasks only. Previously, xcopy-msbuild had to be updated for SigningValidation to work. That dependency is now gone and none of the tasks need a newer msbuild or VS version anymore.
xcopy-msbuild is a broken component. It doesn't work in certain scenarios as pieces are missing (i.e. fsharp or vcxproj targets). Updating it is a mundane, manual process and was handled by dnceng. Though, dnceng shouldn't be responsible for deploying msbuild.
Using it has resulted in more problems than the benefits that it brings. As part of the msbuild team, I absolutely want to see it gone.
There aren't many hits: https://github.com/search?q=repo%3Adotnet%2Farcade+xcopy&type=code