如果你定义一个只有一个getter的接口的接口(= VBO中的ReadOnly),你为什么要在用C#实现类而不是用VB实现类时定义setter？

我原以为它是在.NET级别定义的,而不是特定于语言的.

示例：对于此接口

'VB.NET
Interface SomeInterface

    'the interface only say that implementers must provide a value for reading
    ReadOnly Property PublicProperty As String

End Interface@H_403_8@ 
 
要么
 
  
 
//C# code
interface IPublicProperty
{
    string PublicProperty { get; }
}@H_403_8@ 
 
这是C#中的正确实现：
 
  
 
public class Implementer:IPublicProperty
    {
        private string _publicProperty;

        public string PublicProperty
        {
            get
            {
                return _publicProperty;
            }
            set
            {
                _publicProperty = value;
            }
        }
    }@H_403_8@ 
 
但这在VB.NET中无效
 
  
 
Public Property PublicProperty As String Implements SomeInterface.PublicProperty
    Get
        Return _myProperty
    End Get
    Set(ByVal value As String)
        _myProperty = value
    End Set
End Property@H_403_8@ 
 
更新2015/04/23
 
 
原来这个功能是VB14的一部分！
见Languages features in C# 6 and VB 14和New Language Features in Visual Basic 14：
 
  
 
 
  
ReadOnly interface properties can be implemented by ReadWrite props
 This cleans up a quirky corner of the language. Look at this example:
 
  
06004
 
  
PrevIoUsly,if you were implementing the ReadOnly property I.P,then
 you had to implement it with a ReadOnly property as well. Now that
 restriction has been relaxed: you can implement it with a read/write
 property if you want. This example happens to implement it with a
 read/write autoprop,but you can also use a property with getter and
 setter.