-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
System.Text.Json
SG is run twice in WPF projects
#10175
Comments
Tagging subscribers to this area: @dotnet/area-infrastructure-libraries |
@ZzZombo - I attempted to replicate the issue on my end, but it seems I might be missing some setup details. Could you please provide a minimal sample repro application? |
Sure, but fair warning, I'm currently on sick leave and unlikely to get access to the project for a week. |
I setup a minimal repro here: This is a freshly generated project from the WPF template with only the addition of a PackageReference to the csproj and an arbitrary class to trigger the System.Text.Json source generator. I chose to add that class to MainWindow.xaml.cs but it could go anywhere. You may note that you can "fix" the issue for this project by removing the PackageReference. In this contrived min-reproduction case this may be an option but in real projects the System.Text.Json could be transitive or the specific version necessary. |
Description
Similar to dotnet/extensions#4969, the SG is included twice in a compilation, resulting in duplicate definition errors and build failure due to the way WPF is built, involving a temporary project.
Reproduction Steps
Expected behavior
SG is included only once.
Actual behavior
SG is included twice and prevents the build from finishing successfully.
Regression?
I can't say, sorry. There was one other issue previously but because of two SGs being active at once.
Known Workarounds
I can't say, unless switching back to reflection is considered one.
Configuration
I target
net9-windows
on Windows 10 x64. It shouldn't be specific to that configuration but I don't know for sure.Other information
AS I said already, it shows up twice in output, once per each project in the compilation, even though IMO the temp. WPF project shouldn't run the JSON SG at all, so preventing it from running in either when building a WPF application should fix the issue.
The text was updated successfully, but these errors were encountered: