-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Current WCT solution does not build when .NET 5 preview is installed #3339
Comments
Hello jeromelaban, thank you for opening an issue with us! I have automatically added a "needs triage" label to help get things started. Our team will analyze and investigate the issue, and escalate it to the relevant team if possible. Other community members may also look into the issue and provide feedback 🙌 |
Thanks @jeromelaban for highlighting the issue!! |
Thanks @jeromelaban we hadn't noticed an issue yet, but had also only last tested with preview4 on our machines. Do you know if there's a .NET issue open for anything like this? FYI @azchohfi |
I do not know if there is an existing one. Mentioned it here as I'm not sure where it should be going :) |
@tommcdon @MichalStrehovsky any thoughts on what @jeromelaban is seeing here? Or know the right folks to pull in to this? I have .NET 5 Preview 4.20258.7 on my machine and have no troubles, so this appears like a regression in the .NET 5 Preview? |
Here is the runtime issue for your reference: dotnet/runtime#37672. |
@tommcdon Is it expected that the removal of WinRT affects the WPF the toolchain ? |
Describe the bug
When building the
Microsoft.Toolkit.Services
project, theWPFPopup
XAML page for thenet462
target is not getting its.i.g.cs
content generated properly, causing missing members compilation errors.Steps to Reproduce
Install .NET
5.0.100-preview.6.20277.5
, build the solution.Additional context
This looks like a .NET 5 issue, where the
MarkupCompilePass1
does not seem to be executed at all, even thoughPage
ItemGroup items are present.As a workaround, adding this to the
global.json
file works around the issue:The text was updated successfully, but these errors were encountered: