| > Are there any compelling reasons to use one over the other?
|
[quoted text clipped - 7 lines]
| will. If you decide to go .Net you should seriously consider using C#
| as that looks to have a better chance at survival and stability.
As far as support for VB6, despite the link David Segal posted claiming
2008 is the cut off, MS has effectively dropped support for VB already.
No more service packs or fixes, no help with bugs and issues. The
support for VB6 has been groups like this one for a while now.
Instead of VB.Net, they should have called it VB#. It has the same
relationship to VB that C# has to C++, that is, the same general syntax,
but a totally different code model. Plus they use the same CLR and more
or less the same compiler.
The real question is do you want an ActiveX/COM type of programming
tool, or a .Net Framework type of tool. If you run AutoCAD LT 2000 and
AutoCAD LT 2005 side by side, you can see what happens with a .Net
program - much slower start up time, no improvement in user interface,
the addition of networking and Internet doo-dads for updating widget
libraries and publishing files.