I know how it should be. I just thought that the ide should be aware that the sub getMyProperty() is a class property and treat it like one. It works either way: x.MyProperty and also x.GetMyProperty ... The ide should (in my opinion) not let me run with x.GetMyProperty.
1) The IDE does not "auto" suggest GetMyProperty when you type x., which is fine
2) You have to actually "overwrite" the autosuggestion to get GetMyProperty. Since GetMyProperty is a valid method though, what is wrong with the IDE not flagging it? What if someone else wants to actually use the GetMyProperty instead of the auto-generated getter/setter? Should the IDE stop them?
No it should not stop them. It should show a warning that the sub is "declared" as a property or something like. Because the ide has this visualbasic properties it should at least show a warning - this is what i meant
I guess you had to say it twice before it went through my thick skull. That does make sense (the warning display, a la "Varible 'y' is never assigned any value. (warning #10)")