Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Building a project between two different SDKs fails hard if you reuse nodes

See original GitHub issue

Steps to reproduce

Build a project via msbuild with 2.1.300-preview2-008324
Before msbuild nodes shutdown, build a project via msbuild with 2.1.300-preview2-008533

Expected behavior

No errors

Actual behavior

Actual:

C:\Program Files\dotnet\sdk\2.1.300-preview2-008533\Sdks\Microsoft.NET.Sdk\targets\Microsoft.NET.RuntimeIdentifierInfer
ence.targets(134,5): error MSB4062: The "ShowPreviewMessage" task could not be loaded from the assembly C:\Program File
s\dotnet\sdk\2.1.300-preview2-008533\Sdks\Microsoft.NET.Sdk\targets\..\tools\net46/Microsoft.NET.Build.Tasks.dll.  Conf
irm 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. [E:\project-system2\src\Microsoft.Visual
Studio.ProjectSystem.VisualBasic.UnitTests\Microsoft.VisualStudio.ProjectSystem.VisualBasic.UnitTests.csproj]

Environment data

dotnet --info output:

Issue Analytics

State:
Created 5 years ago
Comments:10 (10 by maintainers)

Top GitHub Comments

1reaction

livarcocccommented, Apr 19, 2018

@nguerrera and I were just talking about this. We used to version assemblies out of the SDK for every build. It seems like we regressed with the infra-changes we did moving to repotoolset.

@tannergooding can you investigate this. I will mark this for 2.1.3xx and will consider taking it to shiproom.

0reactions

nguerreracommented, Aug 1, 2018

https://github.com/Microsoft/msbuild/issues/3572