Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

2.2.100 causes 2.1.500 build failure: The "CheckForImplicitPackageReferenceOverrides" task could not be loaded from the assembly #2717

Closed
mcm-ham opened this issue Dec 5, 2018 · 1 comment

Comments

@mcm-ham
Copy link

mcm-ham commented Dec 5, 2018

If I install 2.2.100, and then add global.json to a project to use 2.1.500 I then get the following build failure:

C:\Program Files\dotnet\sdk\2.1.500\Sdks\Microsoft.NET.Sdk\targets\Microsoft.NET.Sdk.DefaultItems.targets(212,5): error MSB4062: The "CheckForImplicitPackageReferenceOverrides" task could not be loaded from the assembly C:\Program Files\dotnet\sdk\2.1.500\Sdks\Microsoft.NET.Sdk\targets\..\tools\netcoreapp2.0/Microsoft.NET.Build.Tasks.dll. Assembly with same name is already loaded Confirm that the <UsingTask> declaration is correct, that the assembly and all its dependencies are available, and that the task contains a public class that implements Microsoft.Build.Framework.ITask. [C:\repo\netstandard-lib.csproj] [C:\repo\netcoreapp-site.csproj]

If I uninstall 2.2.100 then the project builds fine.

@mcm-ham
Copy link
Author

mcm-ham commented Dec 5, 2018

Oops, I see we csproj exec command to call a custom dotnet command so need to investigate that.

@mcm-ham mcm-ham closed this as completed Dec 5, 2018
wli3 pushed a commit that referenced this issue Feb 7, 2020
….1 (#2717)

- Microsoft.NET.Sdk - 5.0.100-alpha1.19457.1
GangWang01 pushed a commit to GangWang01/sdk that referenced this issue Jun 7, 2022
…n parallel

To prevent mixture on console output between update status and creation steps, I converted `TemplatePackageCoordinator.CheckUpdateForTemplate` to just return results and now `CoordinateInvocationOrAcquisitionAsync` calls `DisplayUpdateCheckResults` after...
GangWang01 pushed a commit to GangWang01/sdk that referenced this issue Jun 21, 2022
…n parallel

To prevent mixture on console output between update status and creation steps, I converted `TemplatePackageCoordinator.CheckUpdateForTemplate` to just return results and now `CoordinateInvocationOrAcquisitionAsync` calls `DisplayUpdateCheckResults` after...
GangWang01 pushed a commit to GangWang01/sdk that referenced this issue Jul 11, 2022
…n parallel

To prevent mixture on console output between update status and creation steps, I converted `TemplatePackageCoordinator.CheckUpdateForTemplate` to just return results and now `CoordinateInvocationOrAcquisitionAsync` calls `DisplayUpdateCheckResults` after...
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant