Using .Net instead of VB for a standalone app

  • Thread starter Thread starter Punya Narra
  • Start date Start date
P

Punya Narra

Hi All,

I have a choice of using VB and .Net in developing a standalone load
distribution application. I need to provide a case study on what are the
major advantages of using .Net with respect to VB?

Looking forward for a reply

Thanks,
Punya
 
Here are a few links which might help you out:

http://www.ftponline.com/vsm/2003_06/online/meader/default_pf.aspx
http://www.fawcette.com/Archives/premier/mgznarch/vbpj/2001/02feb01/jf0102/j
f0102.asp

For me, the biggest advantage of .NET is the power it gives you over VB6,
for example, using libraries written in other languages, etc. An advantage
of VB6 is that the VB6 runtime is significantly smaller than the .NET
Framework.

You might also consider what langauge you would use with .NET. Comparing VB6
and C# .NET is different than comparing VB6 and VB.NET.

Mack D. Male
MVP Visual Developer - Academic
 
Hi Punya,

In addition to Mack,
If you only use managed code, you do not get anymore conflicts with com
objects which not are loaded or has the wrong version. You also do not have
to registrate them. And therefore deployment is much easier.

The toolkit from VB.net is much larger than VB6 (C#6 did not exist) and as
sample doing the registry goes now in a more common way. (But that is with
most operations)

What Mack what saying about a smaller runtimer from VB6 is only temporary.
In the standard update from Microsoft on operatings systems which can use it
is the Net1.1 included, while it is a standard coponent already from Server
2003. So in future it is an advantage upon VB6 with this also.

Between the languages which uses managed code is not much difference, either
in performance and also not in writing, knowing the framework is more
important, those languages are only the cement to build it.

My 2 Eurocent

Cor
 
Hi,
Thanks
I am planning on using C# and would like to the major benefits I get by
using C# in place of VB.
Regards,
Punya
 
Cor makes a really great point, future operating systems have the .NET
Framework included as a standard component, like Windows Server 2003 and I
would suspect Windows XP Service Pack 2. You must also keep in mind however
that there are huge numbers of people still using Windows 98 as their
primary operating system, so they will need to acquire the framework unless
they upgrade to a newer operating system.

Another thing I wanted to mention is that VB.NET and the other languages are
all capable of writing things like Windows Services, something VB6 just
couldn't do. In addition, you can use VB.NET to write web pages and web
services, again, something VB6 simply cannot do.

Cor makes another good point that I should have mentioned (it was
late)....no more DLL Hell if you are using .NET!

Regards,

Mack D. Male
MVP Visual Developer - Academic

Hi Punya,

In addition to Mack,
If you only use managed code, you do not get anymore conflicts with com
objects which not are loaded or has the wrong version. You also do not have
to registrate them. And therefore deployment is much easier.

The toolkit from VB.net is much larger than VB6 (C#6 did not exist) and as
sample doing the registry goes now in a more common way. (But that is with
most operations)

What Mack what saying about a smaller runtimer from VB6 is only temporary.
In the standard update from Microsoft on operatings systems which can use it
is the Net1.1 included, while it is a standard coponent already from Server
2003. So in future it is an advantage upon VB6 with this also.

Between the languages which uses managed code is not much difference, either
in performance and also not in writing, knowing the framework is more
important, those languages are only the cement to build it.

My 2 Eurocent

Cor
 
Punya,
In addition to the other comments.

..NET (both C# & VB.NET) are fully object oriented (encapsulation,
polymorphism, inheritance).

The Framework itself, is generally more powerful then VB6's runtime & 3rd
party COM components, however its not complete yet, consider all the cool
new stuff in .NET 2.0! Also the Framework itself is also OO, which IMHO in
itself makes it more powerful!

Hope this helps
Jay
 
Mack D. Male said:
Cor makes a really great point, future operating systems have the .NET
Framework included as a standard component, like Windows Server 2003 and I
would suspect Windows XP Service Pack 2. You must also keep in mind however
that there are huge numbers of people still using Windows 98 as their
primary operating system, so they will need to acquire the framework unless
they upgrade to a newer operating system.
Click to expand...

Also, isn't the Framework still free? Or has this changed?
 
Back
Top