slight issues with assembly-redirect-generation and VS2017.3

[0x53A]

Note: I have removed AutoGenerateBindingRedirects from my project file on purpose.

1. Install VS2017.3 and/or the standalone msi
2. build my repro: https://github.com/0x53A/net-quote-standard-paket-redirects
3. check the app.config:

  <dependentAssembly>
    <Paket>True</Paket>
    <assemblyIdentity name="System.Threading.Thread" publicKeyToken="b03f5f7f11d50a3a" culture="neutral" />
    <bindingRedirect oldVersion="0.0.0.0-65535.65535.65535.65535" newVersion="4.0.1.0" />
  </dependentAssembly>

4. check the actual file in the build output:
   

5. 4.0.1.0 != 4.0.2.0
   

6. check all files in the packages directory:
   
   

where does 4.0.2.0 come from?

7. check the build log

This means it is no longer possible to deduce what version will land in the build output by analyzing just target-framework + set of packages.

[matthid]

so it should be removed for new sdk?

[0x53A]

this is an old-sdk project

[0x53A]

Note: the new magic resolutions can be disabled by

    <PropertyGroup>
        <ImplicitlyExpandNETStandardFacades>false</ImplicitlyExpandNETStandardFacades>
        <DisableHandlePackageFileConflicts>true</DisableHandlePackageFileConflicts>
    </PropertyGroup>

[0x53A]

Second note: if AutoGenerateBindingRedirects doesn't work, try

<PropertyGroup>
  <AutoGenerateBindingRedirects>true</AutoGenerateBindingRedirects>
  <GenerateBindingRedirectsOutputType>true</GenerateBindingRedirectsOutputType>
</PropertyGroup>

(from dotnet/msbuild#1310)