Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Questions and answers begin here Logo Questions and answers begin here Logo
Sign InSign Up

Questions and answers begin here

Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • About Us
  • Blog
  • Contact Us

Could not load file or assembly ‘Microsoft.Bcl.AsyncInterfaces’ after updating all packages to .net core 3.0.

Home/ Questions/Q 452
Next
Answered
Could not load file or assembly 'Microsoft.Bcl.AsyncInterfaces' after updating all packages to .net core 3.0.
jafet_soliss
jafet_soliss Teacher

I’m trying to run my application on my production server but I’m getting this error message when I try to load it:
“Could not load file or assembly ‘Microsoft.Bcl.AsyncInterfaces, Version=1.0.0.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51’ or one of its dependencies. The system cannot find the file specified.”
I did install the same package version and copied the missing DLL file to the appropriate directory, but the error persists. I’m not sure if the DLL file I’m using is the right one or if I’m missing something else. Here’s my server configuration:
Windows Server 2012 R2 Standard
.NET Framework version 4.7.2
Microsoft Visual Studio 2017 version 15.9
Here’s the relevant part of my web.config file:






I’m not sure what else to try. Any help would be greatly appreciated!

.NETassemblyc#file-loadingtroubleshooting
  • 130
  • 0 Followers
  • 1
  • Report
Leave an answer

Leave an answer
Cancel reply

Browse

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Best Answer
    ramiro.velasco.16 Begginer
    2019-01-29T10:11:32+00:00Added an answer about 4 years ago

    Hello there! I see you are having trouble with the missing assembly issue. Well, the error message you are seeing usually means that the application is looking for a specific assembly that it cannot find. In the case of the Microsoft.Bcl.AsyncInterfaces assembly, it is needed for the proper functioning of certain async methods.
    To solve the problem, you need to make sure that the missing assembly is properly referenced in your code. First, try to find the assembly in your project’s reference list and make sure that the correct version is selected. If it’s not in the list, you can add it manually by browsing to the .dll file and selecting it.
    If the above solution does not work, then try including the assembly in the solution output. You can do this by right-clicking on the assembly in the Solution Explorer and selecting “Properties”. Then set the “Copy Local” property to “True”. This will ensure that the assembly is copied to the output directory when the solution is built.
    Another solution would be to make sure that the missing assembly is installed in the GAC (Global Assembly Cache). You can check if it’s installed by browsing to C:WindowsAssembly. If it’s not there, you can use the gacutil.exe tool to install it.
    Finally, if none of the above solutions help, you can try updating your NuGet package manager to see if the missing assembly can be added from there. Use the command “Update-Package Microsoft.Bcl.AsyncInterfaces” in the Package Manager Console to update your Nuget packages.
    I hope this helps you solve your issue! Remember, if none of the above solutions help, don’t hesitate to ask for help from fellow developers or support forums. Good luck and happy coding!

    • 75
    • Reply
    • Share
      Share
      • Share onFacebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report
  2. boobiebrooke Begginer
    2019-01-31T22:38:22+00:00Added an answer about 4 years ago

    The issue you are facing seems to a common one with Microsoft BCL AsyncInterfaces. The most common cause for such errors are version mismatch or missing files. One possible cause of this error could be that the references of the dependent files are not set up correctly in your project.

    To resolve this issue, one thing you can try is to reinstall the NuGet Package with the latest version of Microsoft BCL AsyncInterfaces. Another thing you can try is to check if all the dependencies are present in the project and if they are correctly referred to. You can also try clearing the NuGet package cache and then build the solution. This might help you resolve the error.

    I hope this will help you resolve your issue. If you have any further questions or concerns, feel free to ask.

    • 15
    • Reply
    • Share
      Share
      • Share onFacebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report
  3. krickwood87 Begginer
    2019-01-31T21:51:41+00:00Added an answer about 4 years ago

    In addition to updating your NuGet packages, you can also try clearing your project’s cache in Visual Studio. Sometimes cached data can cause unexpected behavior, such as the error message you are receiving.

    To clear your cache, close Visual Studio and navigate to the folder where your project is stored. You should see a folder named “bin” and “obj”. Delete both of these folders, as they contain cached data.

    Then, reopen your project in Visual Studio and try building and running it again. This should rebuild the necessary files and hopefully solve your issue.

    If clearing your cache and updating your NuGet packages do not work, you may need to try some other troubleshooting methods or seek help from a more experienced developer.

    • 3
    • Reply
    • Share
      Share
      • Share onFacebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.