question-mark
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.

SDK 6.0.301 -> 6.0.302 upgrade breaks our build

See original GitHub issue

Describe the bug

The VS-Platform repo build broke when the .NET SDK version installed on local dev boxes went from 6.0.301 to 6.0.302 (which released yesterday). Some kind of breaking change was made in this version of the SDK.

To Reproduce

On a machine with 6.0.301 or 6.0.302 installed

git clone https://devdiv@dev.azure.com/devdiv/DevDiv/_git/_optimized/VS-Platform
cd VS-Platform
git checkout 359c6d2f1db9b1adc15b11262aaf74ac625af938
.\init -Feature Editor
msbuild /t:rebuild src\Editor\VisualStudio\Impl\EditorImpl.csproj /r

If 6.0.302 is present, you’ll see a bunch of build errors around the CsWin32 source generator we use, such as:

C:\Users\andarno\source\repos\VS-Platform\src\Editor\VisualStudio\Impl\Microsoft.Windows.CsWin32\Microsoft.Windows.CsWin32.SourceGenerator\Windows.Win32.PInvoke.User32.g.cs(331,52): error CS0111: Type ‘PInvoke’ already defines a member called ‘SetWindowPos’ with the same parameter types [C:\Users\andarno\source\repos\VS-Platform\src\Editor\VisualStudio\Impl\EditorImpl_jqjdp0fp_wpftmp.csproj]

But with 6.0.300 or 6.0.301, the build succeeds.

Further technical details

VS 17.4 Preview 1 (32711.401.main) is installed and where the msbuild.exe used in the repro steps comes from.

Issue Analytics

  • State:closed
  • Created a year ago
  • Reactions:1
  • Comments:8 (5 by maintainers)

github_iconTop GitHub Comments

2reactions
AArnottcommented, Sep 2, 2022

This is expected to be fixed this month (second Tuesday) in 6.0.304 and 6.0.401.

2reactions
AArnottcommented, Aug 10, 2022

This did not get fixed in 6.0.303 or 6.0.400. Sorely disappointing given how broken source generators are by this regression and we waited a month for the fix and it didn’t come. What’s going on?

Read more comments on GitHub >

github_iconTop Results From Across the Web

Update of Visual Studio (17.6.2) and SDK (6.0.302) ...
Errors are thrown during the build process: The type already contains a ... SDK 6.0.301 -> 6.0.302 upgrade breaks our build #26557.
Read more >
Visual Studio 2022 problem after upgrade to last version ...
This issue is caused not by the Visual Studio update from 17.2.5 to 17.2.6, but by the update from .NET SDK 6.0.301 to...
Read more >
Breaking change: Version requirements for .NET 6 SDK
Learn about the breaking change in the .NET 6 SDK where version 17.0 or newer of Visual Studio and MSBuild is required.
Read more >
Net Core/MSBuild Tooling not finding right version
We encountered this issue after upgraded our project to .NET Core 3.1.7 (SDK 3.1.401) today. We are using Microsoft hosted agent windows-latest/ ...
Read more >
Visual Studio 2019 unable to locate .Net Core SDK
My project has no global.json at the root, creating one with the the latest (3.1.201) from dotnet --list-sdks didn't help.
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found