Xamarin.iOS Can not resolve reference: System.Threading.Tasks.Extensions.dll












1















I am trying to build a Xamarin.iOS(runtime v4.0.30319) project but keep getting the following error




Severity Code Description Project File Line Suppression State
Error Can not resolve reference: /Library/Frameworks/Xamarin.iOS.framework/Versions/Current/lib/mono/Xamarin.iOS/Facades/System.Threading.Tasks.Extensions.dll myApp.iOS C:Program Files (x86)Microsoft Visual Studio2017ProfessionalMSBuildXamariniOSXamarin.iOS.Common.targets 795




When I look in C:Program Files (x86)Microsoft Visual Studio2017ProfessionalCommon7IDEReferenceAssembliesMicrosoftFrameworkXamarin.iOSv1.0Facades I can see System.Threading.Tasks.Extensions.dll exists.



and when I compare Xamarin.iOS.Common.targets on another machine that works, there are no differences



after extensive searching I have not been able find a solution. I have also tried:




  • manually adding the .dll to the iOS project

  • reinstalling the .netstandard framework which is used

  • deleting the solution and pulling from source control (I'm the only one affected by this issue)

  • compared my set up to other working set ups


Extra information (possibly irrelevant): This is a cross platform solution and when built in the android environment, everything works as expected.










share|improve this question























  • Because this error is provocated by many types of error or inconsistencies try all this steps, 1) delete de bin/obj folder in your project 2) delete the app of the simulator 3) change the simulator device, 4) close visual studio, 5) open again, 6)restore the nuget packages 7) clean and rebuild let me know if this solved your problem.

    – Marcos José Pérez Pérez
    Nov 22 '18 at 19:03


















1















I am trying to build a Xamarin.iOS(runtime v4.0.30319) project but keep getting the following error




Severity Code Description Project File Line Suppression State
Error Can not resolve reference: /Library/Frameworks/Xamarin.iOS.framework/Versions/Current/lib/mono/Xamarin.iOS/Facades/System.Threading.Tasks.Extensions.dll myApp.iOS C:Program Files (x86)Microsoft Visual Studio2017ProfessionalMSBuildXamariniOSXamarin.iOS.Common.targets 795




When I look in C:Program Files (x86)Microsoft Visual Studio2017ProfessionalCommon7IDEReferenceAssembliesMicrosoftFrameworkXamarin.iOSv1.0Facades I can see System.Threading.Tasks.Extensions.dll exists.



and when I compare Xamarin.iOS.Common.targets on another machine that works, there are no differences



after extensive searching I have not been able find a solution. I have also tried:




  • manually adding the .dll to the iOS project

  • reinstalling the .netstandard framework which is used

  • deleting the solution and pulling from source control (I'm the only one affected by this issue)

  • compared my set up to other working set ups


Extra information (possibly irrelevant): This is a cross platform solution and when built in the android environment, everything works as expected.










share|improve this question























  • Because this error is provocated by many types of error or inconsistencies try all this steps, 1) delete de bin/obj folder in your project 2) delete the app of the simulator 3) change the simulator device, 4) close visual studio, 5) open again, 6)restore the nuget packages 7) clean and rebuild let me know if this solved your problem.

    – Marcos José Pérez Pérez
    Nov 22 '18 at 19:03
















1












1








1








I am trying to build a Xamarin.iOS(runtime v4.0.30319) project but keep getting the following error




Severity Code Description Project File Line Suppression State
Error Can not resolve reference: /Library/Frameworks/Xamarin.iOS.framework/Versions/Current/lib/mono/Xamarin.iOS/Facades/System.Threading.Tasks.Extensions.dll myApp.iOS C:Program Files (x86)Microsoft Visual Studio2017ProfessionalMSBuildXamariniOSXamarin.iOS.Common.targets 795




When I look in C:Program Files (x86)Microsoft Visual Studio2017ProfessionalCommon7IDEReferenceAssembliesMicrosoftFrameworkXamarin.iOSv1.0Facades I can see System.Threading.Tasks.Extensions.dll exists.



and when I compare Xamarin.iOS.Common.targets on another machine that works, there are no differences



after extensive searching I have not been able find a solution. I have also tried:




  • manually adding the .dll to the iOS project

  • reinstalling the .netstandard framework which is used

  • deleting the solution and pulling from source control (I'm the only one affected by this issue)

  • compared my set up to other working set ups


Extra information (possibly irrelevant): This is a cross platform solution and when built in the android environment, everything works as expected.










share|improve this question














I am trying to build a Xamarin.iOS(runtime v4.0.30319) project but keep getting the following error




Severity Code Description Project File Line Suppression State
Error Can not resolve reference: /Library/Frameworks/Xamarin.iOS.framework/Versions/Current/lib/mono/Xamarin.iOS/Facades/System.Threading.Tasks.Extensions.dll myApp.iOS C:Program Files (x86)Microsoft Visual Studio2017ProfessionalMSBuildXamariniOSXamarin.iOS.Common.targets 795




When I look in C:Program Files (x86)Microsoft Visual Studio2017ProfessionalCommon7IDEReferenceAssembliesMicrosoftFrameworkXamarin.iOSv1.0Facades I can see System.Threading.Tasks.Extensions.dll exists.



and when I compare Xamarin.iOS.Common.targets on another machine that works, there are no differences



after extensive searching I have not been able find a solution. I have also tried:




  • manually adding the .dll to the iOS project

  • reinstalling the .netstandard framework which is used

  • deleting the solution and pulling from source control (I'm the only one affected by this issue)

  • compared my set up to other working set ups


Extra information (possibly irrelevant): This is a cross platform solution and when built in the android environment, everything works as expected.







xamarin.ios






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 22 '18 at 12:22









tony09uktony09uk

1,03332441




1,03332441













  • Because this error is provocated by many types of error or inconsistencies try all this steps, 1) delete de bin/obj folder in your project 2) delete the app of the simulator 3) change the simulator device, 4) close visual studio, 5) open again, 6)restore the nuget packages 7) clean and rebuild let me know if this solved your problem.

    – Marcos José Pérez Pérez
    Nov 22 '18 at 19:03





















  • Because this error is provocated by many types of error or inconsistencies try all this steps, 1) delete de bin/obj folder in your project 2) delete the app of the simulator 3) change the simulator device, 4) close visual studio, 5) open again, 6)restore the nuget packages 7) clean and rebuild let me know if this solved your problem.

    – Marcos José Pérez Pérez
    Nov 22 '18 at 19:03



















Because this error is provocated by many types of error or inconsistencies try all this steps, 1) delete de bin/obj folder in your project 2) delete the app of the simulator 3) change the simulator device, 4) close visual studio, 5) open again, 6)restore the nuget packages 7) clean and rebuild let me know if this solved your problem.

– Marcos José Pérez Pérez
Nov 22 '18 at 19:03







Because this error is provocated by many types of error or inconsistencies try all this steps, 1) delete de bin/obj folder in your project 2) delete the app of the simulator 3) change the simulator device, 4) close visual studio, 5) open again, 6)restore the nuget packages 7) clean and rebuild let me know if this solved your problem.

– Marcos José Pérez Pérez
Nov 22 '18 at 19:03














3 Answers
3






active

oldest

votes


















2














I too had a similar problem but there was no System.Threading.Tasks.Extensions.dll on the Mac in the /Library/Frameworks/Xamarin.iOS.framework/Versions/Current/lib/mono/Xamarin.iOS/Facades folder. However on the Windows PC, this file exists in the C:Program Files (x86)Microsoft Visual Studio2017CommunityCommon7IDEReferenceAssembliesMicrosoftFrameworkXamarin.iOSv1.0Facades folder.



The solution for me was to copy the System.Threading.Tasks.Extensions.dll file from the Windows PC to the Mac.






share|improve this answer
























  • That file should be created on build. You may have a versioning problem too

    – tony09uk
    Dec 10 '18 at 10:09











  • How do you correct a versioning problem? Using the pair-to-Mac feature of VS, the only thing I do is keep the Mac XCode updated, and I'm running the current release of VS 2017 on the Windows PC.

    – Mike G
    Dec 11 '18 at 4:35



















2














I ran into this issue as well. My solution was to launch Visual Studio on the Mac (in my case a Mac Mini) and grab all updates for Visual Studio. One of the updates specifically mentioned the System.Threading.Tasks.Extensions.dll issue that I had been experiencing. After the updates I was able to build the project.



Release note of Visual Studio 15.9.4 :
"Error MT2002: Failed to resolve 'System.Runtime.CompilerServices.AsyncValueTaskMethodBuilder' reference from 'System.Threading.Tasks.Extensions...'" when building a Xamarin.iOS project."
https://docs.microsoft.com/fr-fr/visualstudio/releasenotes/vs2017-relnotes#-visual-studio-2017-version-1594visual-studio-2017-version-1594-






share|improve this answer

































    1














    This issue was caused by a versioning mismatch.



    I was running developing in on my windows machine and deploying to an iOS device via a mac on my local network.



    The iOS version held on the mac differed from the version in my xamarin iOS project (the mac had been updated by another dev).



    The resolution for me was to make sure both versions were the same






    share|improve this answer























      Your Answer






      StackExchange.ifUsing("editor", function () {
      StackExchange.using("externalEditor", function () {
      StackExchange.using("snippets", function () {
      StackExchange.snippets.init();
      });
      });
      }, "code-snippets");

      StackExchange.ready(function() {
      var channelOptions = {
      tags: "".split(" "),
      id: "1"
      };
      initTagRenderer("".split(" "), "".split(" "), channelOptions);

      StackExchange.using("externalEditor", function() {
      // Have to fire editor after snippets, if snippets enabled
      if (StackExchange.settings.snippets.snippetsEnabled) {
      StackExchange.using("snippets", function() {
      createEditor();
      });
      }
      else {
      createEditor();
      }
      });

      function createEditor() {
      StackExchange.prepareEditor({
      heartbeatType: 'answer',
      autoActivateHeartbeat: false,
      convertImagesToLinks: true,
      noModals: true,
      showLowRepImageUploadWarning: true,
      reputationToPostImages: 10,
      bindNavPrevention: true,
      postfix: "",
      imageUploader: {
      brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
      contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
      allowUrls: true
      },
      onDemand: true,
      discardSelector: ".discard-answer"
      ,immediatelyShowMarkdownHelp:true
      });


      }
      });














      draft saved

      draft discarded


















      StackExchange.ready(
      function () {
      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53430937%2fxamarin-ios-can-not-resolve-reference-system-threading-tasks-extensions-dll%23new-answer', 'question_page');
      }
      );

      Post as a guest















      Required, but never shown

























      3 Answers
      3






      active

      oldest

      votes








      3 Answers
      3






      active

      oldest

      votes









      active

      oldest

      votes






      active

      oldest

      votes









      2














      I too had a similar problem but there was no System.Threading.Tasks.Extensions.dll on the Mac in the /Library/Frameworks/Xamarin.iOS.framework/Versions/Current/lib/mono/Xamarin.iOS/Facades folder. However on the Windows PC, this file exists in the C:Program Files (x86)Microsoft Visual Studio2017CommunityCommon7IDEReferenceAssembliesMicrosoftFrameworkXamarin.iOSv1.0Facades folder.



      The solution for me was to copy the System.Threading.Tasks.Extensions.dll file from the Windows PC to the Mac.






      share|improve this answer
























      • That file should be created on build. You may have a versioning problem too

        – tony09uk
        Dec 10 '18 at 10:09











      • How do you correct a versioning problem? Using the pair-to-Mac feature of VS, the only thing I do is keep the Mac XCode updated, and I'm running the current release of VS 2017 on the Windows PC.

        – Mike G
        Dec 11 '18 at 4:35
















      2














      I too had a similar problem but there was no System.Threading.Tasks.Extensions.dll on the Mac in the /Library/Frameworks/Xamarin.iOS.framework/Versions/Current/lib/mono/Xamarin.iOS/Facades folder. However on the Windows PC, this file exists in the C:Program Files (x86)Microsoft Visual Studio2017CommunityCommon7IDEReferenceAssembliesMicrosoftFrameworkXamarin.iOSv1.0Facades folder.



      The solution for me was to copy the System.Threading.Tasks.Extensions.dll file from the Windows PC to the Mac.






      share|improve this answer
























      • That file should be created on build. You may have a versioning problem too

        – tony09uk
        Dec 10 '18 at 10:09











      • How do you correct a versioning problem? Using the pair-to-Mac feature of VS, the only thing I do is keep the Mac XCode updated, and I'm running the current release of VS 2017 on the Windows PC.

        – Mike G
        Dec 11 '18 at 4:35














      2












      2








      2







      I too had a similar problem but there was no System.Threading.Tasks.Extensions.dll on the Mac in the /Library/Frameworks/Xamarin.iOS.framework/Versions/Current/lib/mono/Xamarin.iOS/Facades folder. However on the Windows PC, this file exists in the C:Program Files (x86)Microsoft Visual Studio2017CommunityCommon7IDEReferenceAssembliesMicrosoftFrameworkXamarin.iOSv1.0Facades folder.



      The solution for me was to copy the System.Threading.Tasks.Extensions.dll file from the Windows PC to the Mac.






      share|improve this answer













      I too had a similar problem but there was no System.Threading.Tasks.Extensions.dll on the Mac in the /Library/Frameworks/Xamarin.iOS.framework/Versions/Current/lib/mono/Xamarin.iOS/Facades folder. However on the Windows PC, this file exists in the C:Program Files (x86)Microsoft Visual Studio2017CommunityCommon7IDEReferenceAssembliesMicrosoftFrameworkXamarin.iOSv1.0Facades folder.



      The solution for me was to copy the System.Threading.Tasks.Extensions.dll file from the Windows PC to the Mac.







      share|improve this answer












      share|improve this answer



      share|improve this answer










      answered Dec 10 '18 at 5:06









      Mike GMike G

      434




      434













      • That file should be created on build. You may have a versioning problem too

        – tony09uk
        Dec 10 '18 at 10:09











      • How do you correct a versioning problem? Using the pair-to-Mac feature of VS, the only thing I do is keep the Mac XCode updated, and I'm running the current release of VS 2017 on the Windows PC.

        – Mike G
        Dec 11 '18 at 4:35



















      • That file should be created on build. You may have a versioning problem too

        – tony09uk
        Dec 10 '18 at 10:09











      • How do you correct a versioning problem? Using the pair-to-Mac feature of VS, the only thing I do is keep the Mac XCode updated, and I'm running the current release of VS 2017 on the Windows PC.

        – Mike G
        Dec 11 '18 at 4:35

















      That file should be created on build. You may have a versioning problem too

      – tony09uk
      Dec 10 '18 at 10:09





      That file should be created on build. You may have a versioning problem too

      – tony09uk
      Dec 10 '18 at 10:09













      How do you correct a versioning problem? Using the pair-to-Mac feature of VS, the only thing I do is keep the Mac XCode updated, and I'm running the current release of VS 2017 on the Windows PC.

      – Mike G
      Dec 11 '18 at 4:35





      How do you correct a versioning problem? Using the pair-to-Mac feature of VS, the only thing I do is keep the Mac XCode updated, and I'm running the current release of VS 2017 on the Windows PC.

      – Mike G
      Dec 11 '18 at 4:35













      2














      I ran into this issue as well. My solution was to launch Visual Studio on the Mac (in my case a Mac Mini) and grab all updates for Visual Studio. One of the updates specifically mentioned the System.Threading.Tasks.Extensions.dll issue that I had been experiencing. After the updates I was able to build the project.



      Release note of Visual Studio 15.9.4 :
      "Error MT2002: Failed to resolve 'System.Runtime.CompilerServices.AsyncValueTaskMethodBuilder' reference from 'System.Threading.Tasks.Extensions...'" when building a Xamarin.iOS project."
      https://docs.microsoft.com/fr-fr/visualstudio/releasenotes/vs2017-relnotes#-visual-studio-2017-version-1594visual-studio-2017-version-1594-






      share|improve this answer






























        2














        I ran into this issue as well. My solution was to launch Visual Studio on the Mac (in my case a Mac Mini) and grab all updates for Visual Studio. One of the updates specifically mentioned the System.Threading.Tasks.Extensions.dll issue that I had been experiencing. After the updates I was able to build the project.



        Release note of Visual Studio 15.9.4 :
        "Error MT2002: Failed to resolve 'System.Runtime.CompilerServices.AsyncValueTaskMethodBuilder' reference from 'System.Threading.Tasks.Extensions...'" when building a Xamarin.iOS project."
        https://docs.microsoft.com/fr-fr/visualstudio/releasenotes/vs2017-relnotes#-visual-studio-2017-version-1594visual-studio-2017-version-1594-






        share|improve this answer




























          2












          2








          2







          I ran into this issue as well. My solution was to launch Visual Studio on the Mac (in my case a Mac Mini) and grab all updates for Visual Studio. One of the updates specifically mentioned the System.Threading.Tasks.Extensions.dll issue that I had been experiencing. After the updates I was able to build the project.



          Release note of Visual Studio 15.9.4 :
          "Error MT2002: Failed to resolve 'System.Runtime.CompilerServices.AsyncValueTaskMethodBuilder' reference from 'System.Threading.Tasks.Extensions...'" when building a Xamarin.iOS project."
          https://docs.microsoft.com/fr-fr/visualstudio/releasenotes/vs2017-relnotes#-visual-studio-2017-version-1594visual-studio-2017-version-1594-






          share|improve this answer















          I ran into this issue as well. My solution was to launch Visual Studio on the Mac (in my case a Mac Mini) and grab all updates for Visual Studio. One of the updates specifically mentioned the System.Threading.Tasks.Extensions.dll issue that I had been experiencing. After the updates I was able to build the project.



          Release note of Visual Studio 15.9.4 :
          "Error MT2002: Failed to resolve 'System.Runtime.CompilerServices.AsyncValueTaskMethodBuilder' reference from 'System.Threading.Tasks.Extensions...'" when building a Xamarin.iOS project."
          https://docs.microsoft.com/fr-fr/visualstudio/releasenotes/vs2017-relnotes#-visual-studio-2017-version-1594visual-studio-2017-version-1594-







          share|improve this answer














          share|improve this answer



          share|improve this answer








          edited Dec 13 '18 at 16:06









          Erzékiel

          1,49441736




          1,49441736










          answered Dec 11 '18 at 21:13









          DexterDexter

          211




          211























              1














              This issue was caused by a versioning mismatch.



              I was running developing in on my windows machine and deploying to an iOS device via a mac on my local network.



              The iOS version held on the mac differed from the version in my xamarin iOS project (the mac had been updated by another dev).



              The resolution for me was to make sure both versions were the same






              share|improve this answer




























                1














                This issue was caused by a versioning mismatch.



                I was running developing in on my windows machine and deploying to an iOS device via a mac on my local network.



                The iOS version held on the mac differed from the version in my xamarin iOS project (the mac had been updated by another dev).



                The resolution for me was to make sure both versions were the same






                share|improve this answer


























                  1












                  1








                  1







                  This issue was caused by a versioning mismatch.



                  I was running developing in on my windows machine and deploying to an iOS device via a mac on my local network.



                  The iOS version held on the mac differed from the version in my xamarin iOS project (the mac had been updated by another dev).



                  The resolution for me was to make sure both versions were the same






                  share|improve this answer













                  This issue was caused by a versioning mismatch.



                  I was running developing in on my windows machine and deploying to an iOS device via a mac on my local network.



                  The iOS version held on the mac differed from the version in my xamarin iOS project (the mac had been updated by another dev).



                  The resolution for me was to make sure both versions were the same







                  share|improve this answer












                  share|improve this answer



                  share|improve this answer










                  answered Dec 7 '18 at 13:33









                  tony09uktony09uk

                  1,03332441




                  1,03332441






























                      draft saved

                      draft discarded




















































                      Thanks for contributing an answer to Stack Overflow!


                      • Please be sure to answer the question. Provide details and share your research!

                      But avoid



                      • Asking for help, clarification, or responding to other answers.

                      • Making statements based on opinion; back them up with references or personal experience.


                      To learn more, see our tips on writing great answers.




                      draft saved


                      draft discarded














                      StackExchange.ready(
                      function () {
                      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53430937%2fxamarin-ios-can-not-resolve-reference-system-threading-tasks-extensions-dll%23new-answer', 'question_page');
                      }
                      );

                      Post as a guest















                      Required, but never shown





















































                      Required, but never shown














                      Required, but never shown












                      Required, but never shown







                      Required, but never shown

































                      Required, but never shown














                      Required, but never shown












                      Required, but never shown







                      Required, but never shown







                      Popular posts from this blog

                      Create new schema in PostgreSQL using DBeaver

                      Deepest pit of an array with Javascript: test on Codility

                      Costa Masnaga