D
donna
what's the difference between vb and vb .net. which one is better
Thanks
Thanks
K
Karl E. Peterson
donna said:
What's the difference between an apple and a kumkwat?
A troublemaker, are ya? <g>
C
Cindy M -WordMVP-
Hi =?Utf-8?B?ZG9ubmE=?=,
COM interface and generates COM applications/components.
VB.NET (and other .NET languages, such as C#) runs in the .NET
Framework and, by default, creates application/components that run
in the .NET Framework. It can also interface with COM, but that
path is frought with pitfalls and gotchas.
Microsoft came up with the .NET Framework for a couple of reasons
- Different Security concept, that's supposed to make it more
difficult for viruses and other "bad stuff" to install themselves
and run
- Avoid common pitfalls of the COM interface, such as DLL-Hell
(Versioning problems)
The VB.NET language has a lot in common with classical Visual
Basic, but isn't identical. The transition, at a superficial level
anyway, isn't too difficult. The .NET framework provides useful
tools and functionality (things one needed special libraries or
APIs for in classic VB).
You can't really say that one is "better" than the other, although
each certainly has its convinced proponents. When deciding which to
use, you need to analyze where your application will run, and what
system/security requirements are necessary. Since you're asking
this in a Word VBA group, one could guess that you're thinking
about automating Word? In that case, unless you explicitly need
something that .NET offers (the customer requires .NET Framework,
or you need to communicate with a web app, for example), the
classical COM is still the better bet.
Cindy Meister
INTER-Solutions, Switzerland
http://homepage.swissonline.ch/cindymeister (last update Jun 8
2004)
http://www.word.mvps.org
This reply is posted in the Newsgroup; please post any follow
question or reply in the newsgroup and not by e-mail
In a nutshell, the classic VB (Visual Basic) runs in the Windows
COM interface and generates COM applications/components.
VB.NET (and other .NET languages, such as C#) runs in the .NET
Framework and, by default, creates application/components that run
in the .NET Framework. It can also interface with COM, but that
path is frought with pitfalls and gotchas.
Microsoft came up with the .NET Framework for a couple of reasons
- Different Security concept, that's supposed to make it more
difficult for viruses and other "bad stuff" to install themselves
and run
- Avoid common pitfalls of the COM interface, such as DLL-Hell
(Versioning problems)
The VB.NET language has a lot in common with classical Visual
Basic, but isn't identical. The transition, at a superficial level
anyway, isn't too difficult. The .NET framework provides useful
tools and functionality (things one needed special libraries or
APIs for in classic VB).
You can't really say that one is "better" than the other, although
each certainly has its convinced proponents. When deciding which to
use, you need to analyze where your application will run, and what
system/security requirements are necessary. Since you're asking
this in a Word VBA group, one could guess that you're thinking
about automating Word? In that case, unless you explicitly need
something that .NET offers (the customer requires .NET Framework,
or you need to communicate with a web app, for example), the
classical COM is still the better bet.
Cindy Meister
INTER-Solutions, Switzerland
http://homepage.swissonline.ch/cindymeister (last update Jun 8
2004)
http://www.word.mvps.org
This reply is posted in the Newsgroup; please post any follow
question or reply in the newsgroup and not by e-mail