Visual Basic Functions VS .NET Functions

[ImDaFrEaK]

I have found a site straight from MS that helps you understand the better part of VB functions vs .net functions. Sometimes VB functions are equal or better; other times worse.

I incourage anyone looking to optimize their code for either, performance, readability, flexability, or safety to view this webpage. It was very useful to me.

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dv_vstechart/html/vbtchMicrosoftVisualBasicNETInternals.asp

Summary from the page:

Conclusion

Visual Basic .NET seeks to maximize developer productivity without limiting any of the power of the .NET Framework. It accomplishes this goal through a number of unique language constructs and through an extensive run-time library. Visual Basic .NET also defaults to code safety by enabling integer overflow checking by default. However, you as the developer have the ultimate say about safety versus performance.
The Visual Basic Runtime provides many familiar utility methods that will speed development and aid in porting your Visual Basic 6 code. You can choose to leverage the conveniences of the Visual Basic Runtime which are provided in addition to the System classes. In most instances, using the Visual Basic Runtime methods will not have any affect on overall application performance, and it will enhance consistency with other Visual Basic code. The only exception is where you utilize certain Visual Basic Runtime functions for a very large number of operations. This paper has documented the specific functions that you should be aware of in these circumstances. It is also worth noting that if an application is experiencing performance bottlenecks, it is not likely to be remedied by simply utilizing the System methods, as performance and scalability are products of the overall application architecture.
Visual Basic also provides facilities for migrating existing Visual Basic code to the .NET Framework. The Microsoft.VisualBasic.Compatibility namespace contains classes and methods specifically for this task. It is recommended that these classes be used when upgrading, but they should not be used for new code.
As you have seen, Visual Basic provides complete access to the Framework plus a number of additional tools for you to leverage as a developer. These come in the form of language constructs (late binding, optional parameters, and so on), and a runtime which includes methods and compiler services. With an understanding of the internals of Visual Basic, you can decide how to leverage the Visual Basic feature set to achieve the optimal balance of developer productivity, code safety, and execution speed.

 

[JohnH]

The new MY feature is similar to this issue. MY is 'native' .Net but not supported in other than the VB flavour, which fits the bill just fine since Visual Basic is our programming language anyway.