Microsoft MVPs move to save Visual Basic

TalkBack 44 of 88:

Next »

« Previous

• Thread View
• Flat View

True inheritance is new

for one thing. Besides, you asked what you would gain. Ease of programming when it comes to the reasons I posted before is enough for me.

I must have mistaken your tone and "bloat" comments for ".NET is bad" then.

Don't get me wrong, I do sympathize with you and the other people who want to stick with VB6.
I wish the petition the best of luck, I liked vb6 and still work with it occasionally.

But knocking vb.net for forcing a conversion to .NET when you KNEW it would do that (a talkback post from 2-4 weeks ago) is not helping.

The conversion wizard is not really world ready, and would need to be a LOT better before any true migration could occur. This is a big issue, and does need to be addressed by MS.

For the "Real" question, you did not ask me that. You asked that in another post responding to someone else.
Also note that VBA IS different then vb6. You can even get the VBA SDK and add VBA support to your own applications if you so desire, although that may go the same way of vb6.
Now that you have asked me that question, I would go with .NET.
The reason for this is that you can create COM interop wrappers and Runtime Callable Wrappers so that you can use a .NET assembly for your codebase and have it work with COM clients such as the Office suite or .NET clients seamlessly. This will also be a supported way to go moving forward.
No one has to throw away any hardware for this, and you don't have to wait for longhorn. You don't even have to maintain more then one set of code.
Conversely, you could also create a Runtime Callable wrapper for your COM object, so either way would be valid.

For your speed point, I contend that it's not going to make much difference for most applications. For some it will, but also note that you can generate native images with .NET assemblies. Go look up some perf tests, and you will see that .NET is not really slower.
If you need that much speed, then perhaps you should be using C++ or C instead.

Posted by: eb276   Posted on: 03/11/05 You are currently: a Guest | Members login | Terms of Use

Alert moderator to an offensive message

Subscribe to this discussion via Email or RSS

SponsoredWhite Papers, Webcasts, and Downloads

• Virtualization: Architectural Considerations And Other Evaluation Criteria VMware Of the many approaches to x86 systems virtualization available in the ... Download Now
• Three Steps You Need to Know to Stop Data Loss Varonis Sensitive data exposed to misuse or loss... it is the stuff of nightmares ... Download Now
• The Impact of Virtualization Software on Operating Environments VMware Today's use of virtualization technology allows IT professionals to ... Download Now