[XAML] Nested x:TypeArguments: "Type was not found" error.

[Wirox]

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:

When you actually run the application, it works fine.

I'm using Visual Studio 2022 17.11.4.

[miloush]

This seems to be a Visual Studio/designer issue, out of scope for this repo.

[h3xds1nz]

Yeah, that's been there for quite some time.

Similarly, using a Nullable<T> binding over a generic will yield the same result (though it's a bit different case) though there are no issues in runtime as its supported.

[mgoertz-msft]

FYI @etvorun

[Wirox]

This seems to be a Visual Studio/designer issue, out of scope for this repo.

Yeah, I've got to say I'm not quite sure which repo is the right place to report this sort of a bug. Do you know if there is a repo for Visual Studio itself? Or do I have to report the bug through the in-app system?

[miloush]

There is no repo for that, yes you go in VS to Help > Send Feedback > Report problem.

Btw is this WPF/UWP/WinUI?

[Wirox]

There is no repo for that, yes you go in VS to Help > Send Feedback > Report problem.

Btw is this WPF/UWP/WinUI?

Thanks. And this is WPF.