I have a vb.net module file with a few public variables. They are used from other modules simply by calling the variable name (and not module.foo)
Code issues detects the module as being unused and suggest it can be removed
Static Code Analysis – "Unused type" analyzer false positive in the Visual Basic module
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.
- v19.2.3Download Official Update
- v19.1.10Sign in to Request Hotfix
Hi Dan,
Thank you for pointing out this issue.
I have reproduced this false triggering of the Unused Type analyzer in the Visual Basic module. As soon as we fix it, we will notify you.