ansaurus

Question

Friend WithEvents in VB vs private in C#

Answer 1

A:

Perhaps VB is trying to be Friendlier to new programmers and allow them to see all the Friend controls in the form from anywhere in their project?

Friend being internal, only thing I can think of, not sure why the defaults would be different other than to assist new programmers...

Aequitarum Custos 2009-12-17 15:20:47

I believe the new programmers should think OOP, and learn its (Black)Box concept.

serhio 2009-12-17 15:22:46

OOP is easy to preach, but even with C# many green developers learn just enough to get by and fall into a procedural approach. Proper OO design requires additional forethought and greater consideration, so naturally it's a skill that develops *after* learning the basics of an OO language.

STW 2009-12-17 15:26:32

I agree, just one of many reasons I recommend C# to new programmers...

Aequitarum Custos 2009-12-17 15:26:35

I actually offer VB.NET as the better "learning" language; it lets a new developer cut their teeth worrying less about syntax and higher-level design and more about learning the framework. Once a developer is competent with the basic framework tools then they can consider the design and security aspects; it makes for a natural breaking point to make the switch.

STW 2009-12-17 15:29:14

Answer 2

+1 A:

I think it is to help with migration from earlier versions of VB as code in the forms tended to be modified from outside more frequently. Friend is also the default.

Private is better from a code design perspective and is used in C# as there is no similar historic coding practice I guess!

DiggerMeUp 2009-12-17 15:22:42

Answer 3

+4 A:

Friend WithEvents is used for compatibility with older Visual Basic code, where normally a control was used outside the form which contained it.
Differently, in C# there is not the need to keep the compatibility with old code code, which doesn't exist.

private is a better solution, for new code.

kiamlaluno 2009-12-17 15:24:50

Answer 4

+3 A:

Typically VB.NET leans towards exposing too much (privacy is mostly opt-in) whereas C# is the inverse, privacy is typically opt-out. As others have mentioned the reason is likely due to VB.NET's legacy and the "friendliness" of exposing everything; it makes it easy to get started but also leads to poor design and additional effort to ensure loose coupling.

STW 2009-12-17 15:25:24

Answer 5

A:

Anyone know how to make VB default to Private for new forms and user controls??

Darrren 2010-04-30 00:46:22

You don't have to edit the code to do this, there's a "modifiers"property in the properties window for this.

serhio 2010-04-30 07:27:32

by the way, this is not an answer, so you should start a new question for this, or, if you want, I could include your question in mine and reopen it.

serhio 2010-04-30 07:30:21

Thanks, have got round to starting a new question here:http://stackoverflow.com/questions/2800618/set-a-project-default-for-vb-net-projects-so-that-the-default-modifiers-property

Darrren 2010-05-10 06:02:20

ansaurus

tags:

views:

answers:

Friend WithEvents in VB vs private in C#

related questions