Sorry, don't think that is valid. Fields *can* be public eg:

public class Class1
    {
        public string NameField;
        public string NameProperty { get; set; }
    }

Two members; one a field, one a property. Both are visible outside the class. That said, I agree that members intended to be visible outside the class should definitely be declared as properties not fields (and for very good reasons). Whether the scope should be public, protected or internal is a secondary consideration....
In the same vein class level fields should almost always be private - but again, in some circumstances 'protected' may make more sense ?


>A field is a variable that is visible to the entire class. If it needs to be seen from a different class, make it a property.
>
>
>>I don't think that having public field is the same as public memvar in VFP. But I could be mistaken.