VB 6 compatibility layer in VB.NET

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Is there a way to remove the VB 6 compatibility layer from VB.NET applications? The reason that I want to do this is so that I am sure that VB 6 syntax is not being used. Also, I am hoping that removing this layer reduces overhead for an application.
 
Hi Andrew

There is no VB6 syntax in VB.NET; it is all VB.NET syntax.

The compatibility stuff is in the Microsoft.VisualBasic.Compatibility
namespace, so as long as you don't import it you can't use it by accident.

HTH

Charles


Andrew Corley said:
Is there a way to remove the VB 6 compatibility layer from VB.NET
Click to expand...
applications? The reason that I want to do this is so that I am sure that VB
6 syntax is not being used. Also, I am hoping that removing this layer
reduces overhead for an application.
 
* "=?Utf-8?B?QW5kcmV3IENvcmxleSwgTUNTRCwgTUNEQkE=?= said:
Is there a way to remove the VB 6 compatibility layer from VB.NET
applications?
Click to expand...

Remove the references to "Microsoft.VisualBasic.Compatibilit.dll" and
"Microsoft.VisualBasic.Compatibility.Data.dll", if they are set.
The reason that I want to do this is so that I am sure that VB 6
syntax is not being used.
Click to expand...

Then you will have to choose another programming language, for example,
C++, C#, or Java.
Also, I am hoping that removing this layer reduces overhead for an
application.
Click to expand...

I would not use functionality implemented in the compatibility libraries
(Microsoft doesn't recommend that too). Nevertheless,
"Microsoft.VisualBasic.dll" is a "must" reference, IMO, if you want real
RAD development.
 
Is there a way to remove the VB 6 compatibility layer from VB.NET applications? The reason that I want to do this is so that I am sure that VB 6 syntax is not being used. Also, I am hoping that removing this layer reduces overhead for an application.
Click to expand...

Remove any references to Microsoft.VisualBasic.Compatibility.dll from
the project (of course, you won't need to from new projects because they
aren't added by default - unless the project is a VB6 conversion :)

Now, if you talking about the stuff in Microsoft.VisualBasic.dll -
that's a different story. That isn't a compatability layer, that's the
stuff that makes VB.NET, well, VB.NET :)
 
¤ Hi Andrew
¤
¤ There is no VB6 syntax in VB.NET; it is all VB.NET syntax.
¤

You were just kidding, right? ;-)


Paul ~~~ (e-mail address removed)
Microsoft MVP (Visual Basic)
 
Back
Top