Skip to content

Microsoft.Bcl.Async nags about missing "The type 'AnnouncementClient' is required here and is unavailable." #1117

Closed
Closed
Microsoft.Bcl.Async nags about missing "The type 'AnnouncementClient' is required here and is unavailable."#1117

Description

@albertjan
albertjan
opened on Oct 7, 2015

The project is built to .net 4.6 so it should not do anything. At least I was under the impression it shouldn't do anything.

But to my suprise this ended up in my project file:

<When Condition="$(TargetFrameworkIdentifier) == '.NETFramework' And
 ($(TargetFrameworkVersion) == 'v4.0' Or $(TargetFrameworkVersion) == 'v4.5' Or 
  $(TargetFrameworkVersion) == 'v4.5.1' Or $(TargetFrameworkVersion) == 'v4.5.2' Or
  $(TargetFrameworkVersion) == 'v4.5.3' Or $(TargetFrameworkVersion) == 'v4.6')">
  <ItemGroup>
    <Reference Include="Microsoft.Threading.Tasks.Extensions.Desktop">
      <HintPath>..\..\packages\Microsoft.Bcl.Async\lib\net40\Microsoft.Threading.Tasks.Extensions.Desktop.dll</HintPath>
      <Private>True</Private>
      <Paket>True</Paket>
    </Reference>
      yadda yadda yadda
  </itemGroup>
</when>

why does this reference get added to the project for 4.6 when the package is obviously meant for .net4.

I don't know if this is a paket issue, but I thought I'd ask here anyway.

ps. I'm so fed up with these Bcl packages...

Activity

  1. forki commented on Oct 7, 2015

    @forki
    forki
    on Oct 7, 2015
    Member

    net40 means .NET 4.0 and above. at least if there is no other net folder.

    Try with Nuget - it will install the same dlls.

  2. albertjan commented on Oct 7, 2015

    @albertjan
    albertjan
    on Oct 7, 2015
    MemberAuthor

    Alright I believe you. 😄 I have to manually remove this ref from the project to get it to build.

  3. albertjan
    closed this as completedon Oct 7, 2015

  4. eiriktsarpalis commented on May 19, 2016

    @eiriktsarpalis
    eiriktsarpalis
    on May 19, 2016
    Member

    I've recently started getting the same error message actually. For example this project currently builds as expected, but it will fail as soon as I paket update.

  5. eiriktsarpalis commented on May 19, 2016

    @eiriktsarpalis
    eiriktsarpalis
    on May 19, 2016
    Member

    For the record, and reproducing our private discussion with @forki, the problem more likely has to do with a bug in paket when resolving the dependency graph for AWSSDK.Core, which has the following dependency tree

        <dependencies>
      <group targetFramework=".NETFramework4.5" />
      <group targetFramework=".NETPortable0.0-net45+netcore45+wpa81+wp8+MonoAndroid10+xamarinios10+MonoTouch10">
        <dependency id="Microsoft.Net.Http" version="2.2.29" />
        <dependency id="PCLStorage" version="1.0.2" />
        <dependency id="PCLCrypto" version="1.0.2.15130" />
      </group>
    </dependencies>

    which however is resolved to the following paket.lock:

     AWSSDK.Core (3.1.5.3)
      Microsoft.Net.Http (>= 2.2.29) - framework: >= net45, portable-net45+win8+wp8+wpa81
      PCLCrypto (>= 1.0.2.15130) - framework: >= net45, portable-net45+win8+wp8+wpa81
      PCLStorage (>= 1.0.2) - framework: >= net45, portable-net45+win8+wp8+wpa81
  6. forki
    added 2 commits that reference this issue on May 19, 2016

    Fallback from portable to net45 must be conversative - #1117

    a85c16d

    Fallback from portable to net45 must be conversative - fixes #1117

    69e178a
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions