none
MSB4062 The ProcessFrameworkReferences task could not be loaded from the C:\Program Files\dotnet\sdk\3.0.100\Sdks\Microsoft.NET.Sdk\targets\..\tools\net472/Microsoft.NET.Build.Tasks.dll assembly. RRS feed

  • Question

  • Hello, everyone,
    after the update (VS 2019, ver. 16.3.1) I have an error message in a BLAZOR project and I can compile even the smallest project!

    Error is:
    "Severity Code Description Project File Line Suppress State Suppress State Suppress State
    Error MSB4062 The ProcessFrameworkReferences task could not be loaded from the C:\Program Files\dotnet\sdk\3.0.100\Sdks\Microsoft.NET.Sdk\targets\..\tools\net472/Microsoft.NET.Build.Tasks.dll assembly.  Make sure the <UsingTask> declaration is correct, the assembly and all associated dependencies are available, and the task contains a public class implementing Microsoft.Build.Framework.ITask. ohaPortal C:\Program Files\dotnet\sdk\3.0.100\Sdks\Microsoft.NET.Sdk\targets\Microsoft.NET.Sdk.FrameworkReferenceResolution.targets 59."

    My VS information:

    Visual Studio Professional 2019
    Version 16.3.1
    VisualStudio.16.Release/16.3.1+29324.140
    Microsoft .NET Framework
    Version 4.8.03752

    Installierte Version: Professional

    Allgemeine Azure-Tools   1.10
    Bietet allgemeine Dienste für die Verwendung durch Azure Mobile Services und Microsoft Azure-Tools.

    Application Insights-Tools für Visual Studio-Paket   9.1.00913.1
    Application Insights-Tools für Visual Studio

    ASP.NET and Web Tools 2019   16.3.283.64955
    ASP.NET and Web Tools 2019

    ASP.NET Web Frameworks and Tools 2019   16.3.283.64955
    Weitere Informationen finden Sie unter https://www.asp.net/.

    Azure App Service-Tools v3.0.0   16.3.283.64955
    Azure App Service-Tools v3.0.0

    Azure Functions and Web Jobs Tools   16.3.283.64955
    Azure Functions and Web Jobs Tools

    C#-Tools   3.3.1-beta3-19461-02+2fd12c210e22f7d6245805c60340f6a34af6875b
    C#-Komponenten, die in der IDE verwendet werden. Abhängig von Ihrem Projekttyp und den zugehörigen Einstellungen kann eine andere Version des Compilers verwendet werden.

    Extensibility Message Bus   1.2.0 (d16-2@8b56e20)
    Provides common messaging-based MEF services for loosely coupled Visual Studio extension components communication and integration.

    IntelliCode-Erweiterung   1.0
    Detaillierte Informationen zur IntelliCode Visual Studio-Erweiterung

    Microsoft Azure-Tools   2.9
    Microsoft Azure-Tools für Microsoft Visual Studio 0x10 – v2.9.20816.1

    Microsoft Continuous Delivery Tools für Visual Studio   0.4
    Die Konfiguration von Azure DevOps-Pipelines von der Visual Studio-IDE aus wird vereinfacht.

    Microsoft JVM Debugger   1.0
    Provides support for connecting the Visual Studio debugger to JDWP compatible Java Virtual Machines

    Microsoft MI-Based Debugger   1.0
    Provides support for connecting Visual Studio to MI compatible debuggers

    Microsoft Visual Studio-Tools für Container   1.1
    Jetzt können Sie Ihre ASP.NET Core-Anwendung in der Zielumgebung entwickeln, ausführen und überprüfen. Drücken Sie F5, um die Anwendung direkt in einem Container mit Debugfunktionen auszuführen, oder STRG+F5 zum Bearbeiten und Aktualisieren Ihrer Anwendung, ohne den Container erneut erstellen zu müssen.

    Mono Debugging for Visual Studio   16.3.7 (9d260c5)
    Support for debugging Mono processes with Visual Studio.

    NuGet-Paket-Manager   5.3.0
    NuGet-Paket-Manager in Visual Studio. Weitere Informationen zu NuGet finden Sie unter https://docs.nuget.org/.

    ProjectServicesPackage Extension   1.0
    ProjectServicesPackage Visual Studio Extension Detailed Info

    SQL Server Data Tools   16.0.61908.27190
    Microsoft SQL Server Data Tools

    TypeScript-Tools   16.0.10821.2002
    TypeScript-Tools für Microsoft Visual Studio

    Visual Basic-Tools   3.3.1-beta3-19461-02+2fd12c210e22f7d6245805c60340f6a34af6875b
    Visual Basic-Komponenten, die in der IDE verwendet werden. Abhängig von Ihrem Projekttyp und den zugehörigen Einstellungen kann eine andere Version des Compilers verwendet werden.

    Visual F# Tools 10.4 für F# 4.6   16.3.0-beta.19455.1+0422ff293bb2cc722fe5021b85ef50378a9af823
    Microsoft Visual F# Tools 10.4 für f# 4.6

    Visual Studio-Tools für Container   1.0
    Visual Studio-Tools für Container

    Visual Studio-Tools für Unity   4.3.3.0
    Visual Studio-Tools für Unity

    Visual Studio Code-Debugadapter-Hostpaket   1.0
    Interopebene zum Hosten der Visual Studio Code-Adapter in Visual Studio

    VisualStudio.Mac   1.0
    Mac Extension for Visual Studio

    Xamarin   16.3.0.274 (d16-3@06531f8)
    Visual Studio-Erweiterung, um Entwicklung für Xamarin.iOS und Xamarin.Android zu ermöglichen.

    Xamarin Designer   16.3.0.230 (remotes/origin/d16-3-xcode11@bbe518670)
    Visual Studio-Erweiterung zum Aktivieren der Xamarin Designer-Tools in Visual Studio.

    Xamarin Templates   16.3.565 (27e9746)
    Templates for building iOS, Android, and Windows apps with Xamarin and Xamarin.Forms.

    Xamarin.Android SDK   10.0.0.43 (d16-3/8af1ca8)
    Xamarin.Android Reference Assemblies and MSBuild support.
        Mono: mono/mono/2019-06@7af64d1ebe9
        Java.Interop: xamarin/java.interop/d16-3@5836f58
        LibZipSharp: grendello/LibZipSharp/d16-3@71f4a94
        LibZip: nih-at/libzip/rel-1-5-1@b95cf3f
        ProGuard: xamarin/proguard/master@905836d
        SQLite: xamarin/sqlite/3.27.1@8212a2d
        Xamarin.Android Tools: xamarin/xamarin-android-tools/d16-3@cb41333


    Xamarin.iOS and Xamarin.Mac SDK   13.2.0.42 (5e8a208)
    Xamarin.iOS and Xamarin.Mac Reference Assemblies and MSBuild support.



    Monday, September 30, 2019 8:58 AM

All replies

  • Hi Dimitri,

    Do you mean that all projects have the same issue?

    Please check the .NET core SDK version in your side with the command line.

    dotnet --info output:

    Someone reported the similar issue and resolved after he clean up the cache:

    https://github.com/dotnet/winforms/issues/417

    But I suggest you check that whether it has two versions SDK in the same project's build:

    https://github.com/dotnet/cli/issues/9759

    If still no help, maybe you could share a simple sample, I will debug it in my side with the same VS version as yours.

    Sincerely,

    Jack


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.


    Tuesday, October 1, 2019 9:10 AM
    Moderator
  • Hi Dimitri Sluzki,

    What about this issue in your side?

    Would you please share us the latest information?

    Best Regards,

    Jack


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Thursday, October 3, 2019 6:13 AM
    Moderator