Is the Microsoft.VisualBasic namespace “true .NET” code?

by

Microsoft.VisualBasic.dll <> Microsoft.VisualBasic.Compatibility.dll !!!

(or, if you prefer, Microsoft.VisualBasic.dll != Microsoft.VisualBasic.Compatibility.dll; )

The Microsoft.VisualBasic.Compatibility namespace is exclusively for use by the VB6 upgrade wizard, may be removed in future versions, and should not ever be used for new development.

The Microsoft.VisualBasic namespace is absolutely, 100% true .Net, fully supported, and will be around as long as .Net is around.

A few relevant links:

Edit: Added the official word from this MSDN article:

The Visual Basic Runtime provides the
underlying implementation for global
Visual Basic functions and language
features such as Len, IsDate, and
CStr. And though the new Visual Basic
Runtime provides similar facilities as
its predecessors, it is entirely
managed code (developed in Visual
Basic .NET) that executes on the
common language runtime. Furthermore,
the Visual Basic Runtime is part of
the .NET Framework, so it is never
something separate that your
application has to carry or deploy.

and

The Visual Basic 6.0 Compatibility
library is distinct from the Visual
Basic Runtime. The
Microsoft.VisualBasic.Compatibility
namespace is used by the tools that
upgrade Visual Basic 6.0 code to
Visual Basic .NET. It is a bridge to
support Visual Basic 6 features that
are not directly supported by the .NET
implementation of Visual Basic. Unlike
the Visual Basic Runtime, the
compatibility library is not
implicitly referenced by all Visual
Basic .NET applications. When you
upgrade a Visual Basic 6 project to
Visual Basic .NET, the upgrade wizard
adds a reference to
Microsoft.VisualBasic.Compatibility.

The compatibility classes should not
be used for new development. The
Microsoft.VisualBasic.Compatibility
namespace adds a layer of complexity
to your Visual Basic .NET application
and introduces some minimal
performance costs that could be
eliminated by recoding portions of the
application. In addition, the
Compatibility namespace often contains
many classes that wrap COM objects,
and as stated earlier, depending on
COM objects is not as optimal as a
pure managed implementation.

More Related Contents:

  1. For Each Loop in Visual Basic: IndexOutOfRangeException [closed]
  2. What do Option Strict and Option Explicit do?
  3. Clean up Excel Interop Objects with IDisposable
  4. “There is already an open DataReader…” Reuse or Dispose DB Connections?
  5. Using related data stored in a 2 dimensional array
  6. How do you parse an HTML in vb.net
  7. The proper way to dispose Excel com object using VB.NET?
  8. “Items collection must be empty before using ItemsSource.”
  9. Yield in VB.NET
  10. How to count the number of rows in excel with data?
  11. Searching values via a datagridview
  12. Getting the path of the current assembly
  13. VB.Net – Excel COM Object not getting released [duplicate]
  14. What is the difference between Dim v As String() and Dim v() As String?
  15. How can I make a single event handler handle ALL Button.Click events?
  16. How do I shuffle and deal cards one at a time to players?
  17. Where are My.Settings saved in VB 2010 .NET?
  18. Analyze colors of an Image
  19. Equivalent of MoveNext in VB.NET
  20. Pass Command Line to first instance of a Single Instance App
  21. Sorting a Data Table
  22. Start a Task in the Form Shown event
  23. Shuffling an array of strings in vb.net
  24. VB.NET: impossible to use Extension method on System.Object instance
  25. How to find the main() entry point in a VB.Net winforms app?
  26. How do I find out which control has focus in .NET Windows Forms?
  27. How do I fill an empty textbox with default text?
  28. Why doesn’t doubleclick event fire after mouseDown event on same element fires?
  29. String manipulation with & or + in VB.NET
  30. ‘Shadows’ vs. ‘Overrides’ in VB.NET

Leave a Comment