Issue Details (XML | Word | Printable)

Key: DNET-762
Type: Improvement Improvement
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: Jiri Cincura
Reporter: André Ziegler
Votes: 0
Watchers: 1

If you were logged in you would be able to see more operations.
.NET Data provider

Update the referenced Microsoft.BCL packages to latest version for NET40 projects

Created: 09/May/17 10:49 AM   Updated: 23/Aug/17 06:17 AM
Component/s: ADO.NET Provider
Affects Version/s:
Fix Version/s:

Issue Links:

 Description  « Hide
Please update the referenced Microsoft.BCL packages to latest version for NET40 projects because I use newer versions and here I get conflict.

You use

  <package id="Microsoft.Bcl" version="1.1.8" targetFramework="net40-client" />
  <package id="Microsoft.Bcl.Async" version="1.0.168" targetFramework="net40-client" />
  <package id="Microsoft.Bcl.Build" version="1.0.14" targetFramework="net40-client" />

but there are 2 updates:

  <package id="Microsoft.Bcl" version="1.1.10"
  <package id="Microsoft.Bcl.Build" version="1.0.21"

I have no idea why you added old versions when there are already newer ones available for years.

I've added assemblyBinding entriy in app.config to redirect the referenced System.Runtime to the newer (Microsoft.Bcl" version="1.1.10" ) but when I capture a trace with WPR.exe and analyze the ETL I still see "System.IO.FileLoadException" entry when .net tries to load System.Runtime in version

 All   Comments   Change History   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order
Jiri Cincura added a comment - 10/May/17 08:33 AM
It's known issue in NuGet on new csproj: . Looks like I'd have to specify the dependencies manually to force it to new versions.

Jiri Cincura added a comment - 25/Jul/17 08:16 AM
Superseded by DNET-774.

André Ziegler added a comment - 30/Jul/17 12:55 PM

André Ziegler added a comment - 30/Jul/17 01:01 PM
you can force version on your own in NuGet package file :

<group targetFramework="net40-client">
        <dependency id="Microsoft.Bcl" version="1.1.10" />

<group targetFramework="net40-client">
        <dependency id="Microsoft.Bcl.Build" version="1.0.21" />

as you did for Microsoft.Bcl.Async

<group targetFramework="net40-client">
        <dependency id="Microsoft.Bcl.Async" version="1.0.168" />