Skip to content
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

Nested x:TypeArguments: "Type was not found" error. #10114

Closed
Wirox opened this issue Oct 29, 2024 · 5 comments
Closed

Nested x:TypeArguments: "Type was not found" error. #10114

Wirox opened this issue Oct 29, 2024 · 5 comments
Labels
area-External Not owned by the WinUI team, not actionable in this repository. bug Something isn't working

Comments

@Wirox
Copy link

Wirox commented Oct 29, 2024

When using a nested generic type argument with the x:TypeArguments directive (such as Nullable<bool>), the following error is incorrectly shown in the XAML file:
Image

When you actually run the application, it works fine.

I'm using Visual Studio 2022 17.11.4.

@Wirox Wirox added the bug Something isn't working label Oct 29, 2024
@microsoft-github-policy-service microsoft-github-policy-service bot added the needs-triage Issue needs to be triaged by the area owners label Oct 29, 2024
@karkarl karkarl added area-External Not owned by the WinUI team, not actionable in this repository. and removed needs-triage Issue needs to be triaged by the area owners labels Nov 7, 2024
@karkarl
Copy link
Contributor

karkarl commented Nov 8, 2024

This looks like an issue with IntelliSense with Visual Studio.

@Wirox
Copy link
Author

Wirox commented Nov 8, 2024

@karkarl Yeah, I wasn't quite sure where the issue lies. Do you know if this should be reported in https://github.com/dotnet/roslyn then?

@karkarl
Copy link
Contributor

karkarl commented Nov 8, 2024

@karkarl Yeah, I wasn't quite sure where the issue lies. Do you know if this should be reported in https://github.com/dotnet/roslyn then?

You can try opening an issue there. In the meantime, this bug will routed internally to Visual Studio.

@Wirox
Copy link
Author

Wirox commented Nov 10, 2024

@karkarl Thanks, opened an issue there: dotnet/wpf#10050
Not sure if it means this one should be closed, but feel free to do that.

@evelynwu-msft
Copy link
Contributor

Marking issue as closed as it's related to WPF and not WinUI 3, and a bug has been opened in the corresponding repo.

@evelynwu-msft evelynwu-msft closed this as not planned Won't fix, can't repro, duplicate, stale Nov 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-External Not owned by the WinUI team, not actionable in this repository. bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants