Member Avatar for jhai_salvador

Hi!

I don't know where to post this, but since this is vb6 thread i'll just post it here.

I need all of your support by voting Visual Basic Classic to be improved. here is the link:

To vote:
Click the vote button and Choose 3 and thats it. No need to register. We need a lot of votes so spread the word about it.

Thank you,

  • 5 Contributors
  • 7 Replies
  • 268 Views
  • 1 Year Discussion Span
  • Latest Post Latest Post by sten2005
AndreRet commented: I voted. I agree with most of the posts there as well. +13

Dani AI

Generated

Good to see this thread and the community pushing on the same goal. started a clear call to action, and thanks to , and for keeping momentum. ’s suggestion to pursue a sticky and sharpen the title is practical — visibility helps, but visibility alone won’t move engineering teams.

Be explicit about the ask. “Bring back Classic Visual Basic” can mean very different things to different people. A short, prioritized spec will make the campaign persuasive: backward compatibility requirements (what must run unchanged), target platforms and 32/64-bit expectations, IDE feature set (designer, debugger, package management), supported interop (COM/.NET), and a maintenance/patching commitment. Concrete asks are easier to evaluate than emotional appeals.

Turn votes into evidence. Collect a few enterprise case studies showing maintenance cost or business risk from rewriting, a small migration-cost estimate, and a minimal prototype or mockups that show what “improved VB Classic” looks like in practice. Organize those into a one-page executive summary plus a technical appendix. That kind of package communicates seriousness to product teams and decision makers.

While campaigning, protect existing apps. Practical steps that reduce immediate risk: keep a documented build and test VM snapshot that runs the VB6 IDE and runtime; separate UI from business logic where possible; wrap legacy components behind COM or service boundaries so they can be incrementally replaced; add automated tests around critical flows; and move sources into version control with a reproducible build process. These reduce the urgency of a full rewrite and buy time for a coordinated effort.

Finally, coordinate rather than spam. Ask a moderator about a sticky (as suggested), keep updates short and technical, and gather cross-community endorsements (enterprise IT, independent ISVs). A focused, well-documented request backed by measurable impact will always be more effective than raw vote counts alone.

Recommended Answers

All 7 Replies

Member Avatar for AndreRet

Indeed. I voted!!

Member Avatar for jhai_salvador

Indeed. I voted!!

Thank you very much ;)

Anyone, please do vote VB Classic to be improved:

Member Avatar for TnTinMN

I wish you the best of luck with this.

If MS does finally see the light and provide an update, I hope that they also will have the sense to draw the line on the .Net side of things and admit that it is not a natural progression from VB6 and in doing so eliminate the stuff in it that tries to tie it back to VB6. That stuff only confuses people.

commented: my thoughts exactly. :) +13
Member Avatar for TnTinMN

@Jhai,

It may help if you request that a moderator "sticky" this thread for a month or two. Just make a posting and flag it as a bad post (I really dislike the name they use to request moderator attention).

I also suggest that you request that the title be changed to something like:

Please vote for "MS to update VB6" - we have their attention - Act Now!

Member Avatar for sten2005

This vote is still live.
Please vote VB Classic to be improved:

Member Avatar for sten2005

This vote is now the fifth highest out of over 8000

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.