In my old VS 2010/Delphi Prism environment, when I typed a new property name like “Abc” and then typed “read f”, I was presented with the choice of the backing field named “fAbc”.
That still happens.
But when I used to type “write set”, I would get a choice of “setAbc”. That doesn’t happen any more.
Is that missing, or am I doing it wrong?
… time passes …
Hmmm… when I create a NEW project, it seems to be working correctly. But in the one I just created that didn’t work, when I go back there, it STILL doesn’t work. Not sure what is breaking it.
It doesn’t even do the “fAbc” part now.
… time passes …
Now this is just bizarre. I got rid of the property I typed in. I did a clean. I did a rebuild. I think I positioned my cursor at the end of a property line and pressed enter to get a new line for a new property, and IT PUT BACK MY DELETED LINE.
Somebody got a clue on this?
… time passes …
I shutdown VS and restarted it and reopened my project. Now it is working.
… time passes …
OMG, no it didn’t work. It prompted for the “fSelectedPerson” (in this case), and put it in after the read, but it didn’t generate a private backing field. What the heck is going on here?
… time passes …
I DID find my previous post: How do I make the event handler method auto generate the code?
Apparently the behavior is still not fixed. (or else I need to download a beta or something)
… time passes …
Ew, this seems a mess. Sometimes I get the “fAbc” and sometimes I don’t. Sometimes I get the “SetAbc” and sometimes I don’t.
It looks like if I type “read fAbc write SetA”, “SetAbc” is not a choice.
But if I close the popup, and then press “Ctrl-Space”, THEN the choice is there.
Why would it not show up on the first popup?