You have to use expanded property-definition syntax if you want to do any one of the following:Īdd code to the Get or Set procedure of a property, such as code to validate incoming values in the Set procedure. However, you can supply a value by using an array initializer, as shown in the following examples. When you declare an auto-implemented property as an array, you cannot specify explicit array bounds. When you declare an auto-implemented property as a member of a Structure, you can only initialize the auto-implemented property if it is marked as Shared. You cannot initialize an auto-implemented property that is a member of an Interface, or one that is marked MustOverride. However, the backing field does not show in an IntelliSense word completion list. The backing field can be accessed from code within the class and from debugging tools such as the Watch window. If the property is marked as Shared, the backing field also is shared.Īttributes specified for the property do not apply to the backing field. The access modifier for the backing field is always Private, even when the property itself has a different access level, such as Public. Be careful - if you include a member of your class that is also named _ID, you produce a naming conflict and Visual Basic reports a compiler error.
For example, if you declare an auto-implemented property named ID, the backing field is named _ID. The backing field name is the auto-implemented property name preceded by an underscore (_). Property CustomerName() As String = "New"
0 kommentar(er)
