ByVal and Visual Studio 2010 SP1

Question

After installing VS 2010 SP1 I noticed that ByVal keyword doesn't automatically appear after declaring Function or Sub parameters. Is it new feature or bug?

For instance, if I wrote

Function GetValue(sName as String) As Double

and then pressed ENTER, the VB Editor automatically inserted ByVal before "sName":

Function GetValue(ByVal sName as String) As Double

End Function

---

There is no knowle

Answer 1

It is a change - as byval as default and therefore the pretty lister has been modified to avoid it inserting byval into your source.

 

 

 

 

Answer 2

Agree with ya! The code looks much cleaner without ByVal. :)

---

There is no knowledge that is not power.

Answer 3

Ironic.

I don't have SP1 (Is it official, yet?) but it's interesting how all these features that have been added over the years to the 'toy' language Visual Basic, are now being removed. I'm pretty certain that one of the versions of VB did not have the ByVal qualifier (VB 3, 4, or 5?), or it was optional.

---

Stephen J Whiteley

Answer 4

In VB classic it was Byref as default and optional.  

I think when it was switch to .NET it became ByVal as default and therefore it was probably more important to highlight this distinction.   After 5 different version of VB.NET this is probably not a source of confusion any more.

Removal of the Byval in VB.NET source code doesnt change any behavior as such - it just become implied by default.

I see a lot more features being added to the language as well as new syntax with removal of old items which may be a little obsolete with current programming practice.

Answer 5

I think it's better without ByVal keyword. In C#, this keyword is not automatically added when you add parameter. I think it's a decision with the Visual Basic team to be more close to the c# rules.

 

In a couple of years, visual basic will be a curly brace language and after that, it will die. :D