Issue building with Windows Desktop 6.0.2

[RussKie]

After updating to 6.0.2 you may experience issues running WPF apps built against 6.0.2 on 6.0.0 or 6.0.1 runtime with the following error.

CoreCLR Version: 6.0.121.56705
.NET Version: 6.0.1
Description: The process was terminated due to an unhandled exception.
Exception Info: System.IO.FileLoadException: Could not load file or assembly 'PresentationFramework, Version=6.0.2.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'. The located assembly's manifest definition does not match the assembly reference. (0x80131040)
File name: 'PresentationFramework, Version=6.0.2.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'

For an available workaround please refer to dotnet/core#7176.

[dotMorten]

We're hitting this too. Didn't happen with 6.0.1. If we build a class library with 6.0.2, then try and consume it in an application built on a PC with 6.0.0 or 6.0.1 on it (ie haven't update VS yet), the compilation will fail.

CSC : error CS1705: Assembly 'MyClassLib' with identity 'MyClassLib, Version=1.2.3.0, Culture=neutral, PublicKeyToken=8fc3cc631e44ad86' uses 'PresentationFramework, Version=6.0.2.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' which has a higher version than referenced assembly 'PresentationFramework' with identity 'PresentationFramework, Version=6.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'

[FG-rgb]

Hello, is there a possibility to tell visual studio 2022 (v 17.1.0) to explicitly build with .net 6.0.0 or 6.0.1 instead of 6.0.2?

[RussKie]

6.0.3 has been released today, please consider updating. Also check dotnet/core#7176 for suggested workarounds.

[Molinarius]

I see exactly the same issue after updating to Visual Studio 17.1.1, .NET 6.0.3, .NET SDK 6.0.201, on 2 different computers.

[FG-rgb]

Me too. A helping workaround is using a global.json in solution dir:

{
"sdk": {
"version": "6.0.100",
"rollForward": "disable"
}
}

[RaulFunezp]

Thank you FG-rgb

After several weeks trying to solve this problem with the other suggestions your workaround works fine for me using a global.json and version 6.0.103.

I am using WPF, .NET 6.0.3, .NET SDK 6.0.201.

Me too. A helping workaround is using a global.json in solution dir:

{ "sdk": { "version": "6.0.100", "rollForward": "disable" } }