You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using the ObservableObject attribute from the CommunityToolkit.Mvvm v8.3.2 package on the code behind partial class of a WPF UserControl like this:
The reference <see cref = "ObservableObject"/> symbol reference is not resolved in the *.g.cs file generated by the ObservableObjectGenerator.
First, I opened a ticket in the DocFx project because I found this issue working with DocFx. Analyzing the problem with a contributor from the DocFx team, I was sent over here.
How to fix problem
ObservableObject should be referenced by using fully qualified name.
(e,g, <see cref = "global::CommunityToolkit.Mvvm.ComponentModel.ObservableObject"/>)
Describe the bug
When using the ObservableObject attribute from the CommunityToolkit.Mvvm v8.3.2 package on the code behind partial class of a WPF UserControl like this:
The reference
<see cref = "ObservableObject"/>
symbol reference is not resolved in the *.g.cs file generated by the ObservableObjectGenerator.First, I opened a ticket in the DocFx project because I found this issue working with DocFx. Analyzing the problem with a contributor from the DocFx team, I was sent over here.
How to fix problem
ObservableObject should be referenced by using fully qualified name.
(e,g,
<see cref = "global::CommunityToolkit.Mvvm.ComponentModel.ObservableObject"/>
)It probably can be fixed by changing following line.
https://github.com/CommunityToolkit/dotnet/blob/v8.3.2/src/CommunityToolkit.Mvvm/ComponentModel/ObservableObject.cs#L275
Regression
No response
Steps to reproduce
Have a look at my test project DocFxTest to reproduce this issue or follow these steps:
Expected behavior
Symbol should be resolved (and highlighted).
Screenshots
No response
IDE and version
VS 2022
IDE version
17.11.5
Nuget packages
Nuget package version(s)
8.3.2
Additional context
No response
Help us help you
Yes, I'd like to be assigned to work on this item.
The text was updated successfully, but these errors were encountered: