Hi
The events, in the code behind (Xamarin) appears to be disable as if the event is not used.
Please view the attached screen shot.
How can I make the event to appear "enabled"
Regards
Dimitris
Code Analysis - CodeRush incorrectly marks event handlers as unused members in XAML code-behind files
Answers approved by DevExpress Support
We have fixed the issue described in this ticket and will include the fix in our next maintenance update. To apply this solution before the official update, request a hotfix by clicking the corresponding link for product versions you require.
Note: Hotfixes may be unavailable for beta versions and updates that are about to be released.
- v17.1.9Download Official Update
Hi Dimitris,
Your event is not disabled. It's painted in a different color to notify that the event handler is empty and is not used (so, it can be safely removed). You can disable such behavior in options:
Editor\All Languages\Code Analysis\Static Code Analysis options page, 'Highlight unused members'
Here is more information regarding this feature:
https://documentation.devexpress.com/CodeRushForRoslyn/119066/Code-Analysis/Analyzers-Library/CRR0026-Unused-member
Hi Alex and thank you for your answer.
I wrote (appears to be disable) to describe the appearance of the event handler. (The actual event handler is not disable obviously)
The event handler "appears as disabled" (I hope that is more clear now) even if there is code inside!
In Xamarin forms (and perhaps other technologies like Web forms, event handlers are very common and all will "appear as disabled".
Maybe you need to reconsider for coloring event handlers as disabled.
I haven't check the solution that you provided yet, but I trust that will solve the problem.
I will get back to you if there are any problems.
Dimitris
Dimitris,
Can you please send a small project where the event handler is shown as unused so we can try to reproduce the issue on our side? Thanks in advance!
Hi
Attached you can find the solution that you asked.
It's a new Xamarin.Forms application and there is one event handler in MainPage.
In the attachment you can also find a screenshot of what I was describing.
There is nothing special about the solution. I just created it.
Dimitris
Hi Dimitris,
Thank you for the clarification. I reproduced the issue and we are working on it.