Auto properties : What ifs ...

re: Auto properties : What ifs ...

bill — Mon, 31 Mar 2008 03:51:04 GMT

Hey Nick,

Well we might have to agree to disagree then ;) The C# iplementation simply wouldn't work in VB, especially such as having a mixed accessibility (private set, public get etc).

I also think the C# implementation is okay only for writing code the first time, but as soon as you want to modify anything it needs a refactoringn tool. I expect as time goes on that is the exact complaint we'll see more and more of from C# folks .

re: Auto properties : What ifs ...

Nick — Sun, 30 Mar 2008 23:00:24 GMT

Bill, I have to disagree I personally hate the auto-collapsing feature of Refactor! I actually decided to remove it purely based on how annoying this "feature" was - perhaps there's a way to disable it.....

I really like the C# implementation and if we can get something like that I think it would be a great time saver.

re: Auto properties : What ifs ...

bill — Fri, 28 Mar 2008 13:28:28 GMT

Hey Morgan,

Yep, good point. In C# a auto property can have a mixed accessibility, such as :

public string Foo { get; private set; }

re: Auto properties : What ifs ...

Morgan Persson — Fri, 28 Mar 2008 12:57:56 GMT

For the proposed solution there seems no way to handle a public Get and a protected Set. IIRC C# can do that.