-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
CS8785 error after updating from 8.0.304 to 8.0.306 SDK #44145
Comments
@nico-1987 I saw you were able to workaround the issue. Can you also try the |
Thanks for the quick update, i just tested in our .NET 6 product with
This did not fix the issue, actually the whole WinRT.SourceGenerator folder, and thus Generator.WinRTAotSourceGenerator\WinRTGlobalVtableLookup.g.cs does not exist (anymore?) in our obj path (for which we use a custom path)
Error: |
I suffer from the same issue after .Net 8 SDK update to 8.0.403
I tried all workarounds for this issue but nothing works |
The only fix that works for me is: dotnet-core-uninstall remove 8.0.403 --sdk |
Have you tried the workaround to disable WinRT AOT optimizer in project file, that was proposed here? <CsWinRTAotOptimizerEnabled>false</CsWinRTAotOptimizerEnabled> At least for me it did work. EDIT: Sorry, I just saw that you posted there that it didn't work for you. |
@ekalchev please provide a binlog - we think the issue should be fixed but without further details we can't dig into what's going on in your system. |
@baronfel is this enough or you need the entire log? |
Unfortunately It's not enough to double check if you applied the workaround described above and/or see if there's some other context in your working environment that triggers the issue. If you can create a developer community ticket to securly upload the binlog we can privately investigate if that's alright with you. |
@baronfel Here the ticket https://developercommunity.visualstudio.com/t/Building-with-SDK-80403-throws-CSC-err/10779441
|
@manodasanW can you take a look at the binlogs and offer guidance? |
I believe we have fixed this issue for our next update. But |
Describe the bug
After updating the .NET 8 SDK from 8.0.304 to the latest 8.0.306 some or our projects targeting framework net8.0-windows10.0.19041 fail with error.
We use Visual Studio 2022 17.10.7.
and
We did find that adding this to our Directory.Build.props code base "resolves" the issue, though in the documentation we can read its not recommended to use this property.
For now we can keep this as a workarround, but we would like to understand the proper fix.
To Reproduce
I have not been able to reproduce this yet outside our own code base. We don't know where this code generator comes from and what it triggers.
Exceptions (if any)
and
Further technical details
.NET SDKs installed:
2.1.202 [C:\Program Files\dotnet\sdk]
2.1.512 [C:\Program Files\dotnet\sdk]
3.1.423 [C:\Program Files\dotnet\sdk]
5.0.416 [C:\Program Files\dotnet\sdk]
6.0.310 [C:\Program Files\dotnet\sdk]
6.0.427 [C:\Program Files\dotnet\sdk]
8.0.304 [C:\Program Files\dotnet\sdk]
8.0.306 [C:\Program Files\dotnet\sdk]
Visual Studio 2022 - 17.10.7
Windows 11 Version 23H2
The text was updated successfully, but these errors were encountered: