Identifies auto-assigned object declarations.
New This feature is currently only available in pre-release builds (or the xmldoc asset doesn’t yet exist on
Inspection type: CodeQualityIssues
Auto-assigned objects are automatically re-created as soon as they are referenced. It is therefore impossible to set one such reference to 'Nothing' and then verifying whether the object 'Is Nothing': it will never be. This behavior is potentially confusing and bug-prone
The following quick-fixes are available for this inspection:
Each example is a self-contained MCVE showing the feature in a single specific scenario.
Module1by default, these are general-purpose standard procedural modules.
Class1by default, these modules define the default interface for an object of that type.
VB_PredeclaredIdattribute set to
True(with or without a
@Interfaceannotation) whose default interface is not a class type intended to be instantiated.
The following code should trigger this inspection:
The content of this page was generated from xml/comments in the source code compiled into
Edit this page