Home/ Questions/Q 7161095
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-28T13:30:30+00:00

I Like .NET automatic properties, in C# it so easy to declare readonly property

  • 0

I Like .NET automatic properties, in C# it so easy to declare readonly property by declaring its set section as private like this:

public String Name{ get; private set; }

But when I tried that in VB.NET I was shocked that it is not supported as mentioned here and I have to write it as follows:

Private _Name as String
Public ReadOnly Property Name as String
   Get
      return _Name
   End Get
End Property

Or:

Private _Name as String
Public Property Name as String
   Get
      return _Name
   End Get
   Private Set(value as String)
      _Name = value
   End Set
End Property

What the difference between these declarations in VB.NET, which one is preferred and Why?

Edit

Which one will affect compile time, runtime or performance at all?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    In the case of ReadOnly, only those with access to the underlying variable may change the underlying value (i.e. elements within the same class, for instance) by directly applying such a change. In the latter case, Private Set – this is much the same – elements within the scope of the class can change the underlying value, but can do so by means of the property.

    Which one is preferred is circumstantial: one advantage of properties is that you can, like a method, have further implementation involved when applying the change (although side-effects should be avoided, you might ‘validate’ and take exception, for instance). If there is always something else to do when setting the value, that is strongly related to setting the value, you might do it within this property setter, as opposed to having to code that implementation everywhere you do the set.

    • 0