FSharp.Core 4.4.0.0 gets referenced when using Visual Studio 2015 Preview

[ctaggart]

I created an example FSharp.Data.SqlClient console app to isolate a problem I'm having using it with Visual Studio 2015 Preview. The app simple runs a query against a hosted AdventureWorks on Azure. It prints the top the first 10 people using select top 10 FirstName, LastName from person.person.

When running from Visual Studio 2013 it works.

When I use Visual Studio 2015 Preview, I get:

The build does give this warning:

For some reason, the PeopleData.dll is ending up with a reference to 4.4.0.0, but I'm not sure how.

Here are the steps to reproduce:

PS> git clone https://github.com/ctaggart/Paket09x.git -b PeopleSql
PS> .\Paket09x\PeopleSql.sln

Rebuild solution. (It is not using Paket.)

[ctaggart]

@dmitry-a-morozov and I were able to get it to run by redirecting back from 4.4.0.0 to 4.3.1.0 in the App.config. I'm thankful for backward compatibility in FSharp.Core. It still doesn't answer how 4.4.0.0 gets referenced in the first place.

<?xml version="1.0" encoding="utf-8"?>
<configuration>
  <runtime>
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
      <dependentAssembly>
        <assemblyIdentity name="FSharp.Core" publicKeyToken="b03f5f7f11d50a3a" culture="neutral" />
        <bindingRedirect oldVersion="0.0.0.0-4.4.0.0" newVersion="4.3.1.0" />
      </dependentAssembly>
    </assemblyBinding>
  </runtime>
</configuration>

[ctaggart]

Just in case, I notified Visual F# and logged this bug:
https://visualfsharp.codeplex.com/workitem/176

[ctaggart]

According to Kevin, it is something wrong with this Type Provider implementation.

[ctaggart]

Pretty still affects the latest Visual Studio 2015 build. I'm sure it will still affect VS 2015 RTM.
Work-a-round:

<bindingRedirect oldVersion="0.0.0.0-4.4.0.0" newVersion="4.3.1.0" />

[dmitry-a-morozov]

@ctaggart We're long way from resolving this issue.
See dotnet/fsharp#478

[lessismore1]

Same problem with creating and Web Api using
*VS 2015 Upd1
*ASP.NET5 RC1 Upd1
*SqlClient 1.8

[dmitry-a-morozov]

@lessismore1 As of now the only solution is to use binding redirect.

[dsevastianov]

@lessismore1 looks like it was fixed, are you still experiencing this?

[lessismore1]

@dsevastianov it is fixed! Sorry for the VERY late reply :)