VS2017 Not Copying Satellite Assemblies to Proper Output Location

From @thefringeninja on March 16, 2017 17:21

I’ve been porting a project over to the new .csproj format. This project has a dependency on FluentValidation, which uses satellite assemblies. In VS2015, on compilation, these would be placed in their correct subfolders. VS2017 places all the satellite assemblies in the root build output folder. Since they all have the same filename, only one remains.

Minimal repro project file:

<Project Sdk="Microsoft.NET.Sdk">

  <PropertyGroup>
    <OutputType>Exe</OutputType>
    <TargetFramework>net46</TargetFramework>
  </PropertyGroup>

  <ItemGroup>
    <PackageReference Include="FluentValidation" Version="5.5.0" />
  </ItemGroup>

</Project>

Copied from original issue: Microsoft/msbuild#1877

[pharring]

[Just making a note for search engines to pick up the following error messages.] If you see the following error while running unit tests in VSTS:

Warning: Test Run deployment issue: an error occurred while getting satellite assemblies for deployment item System.ArgumentOutOfRangeException: startIndex cannot be larger than length of string. Parameter name: startIndex

then it may be caused by this issue. The workaround at https://github.com/dotnet/sdk/issues/1360#issuecomment-310157372 should fix it.

[nguerrera]

I agree. I have not looked for a workaround. I plan to fix this soon.