Re: VB6, VB2005, or Something Else?

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

We now know that Vista will support VB6 apps (good news of course). This
buys us 6 or so years to start a long-term migration to another coding

You have to keep in mind that MS is migrating to 64 bit by the year end.
I hear Exchange is going to be in 64 bit and will be released this summer.
VB6 works OK in 64 Bit, but has many limitations, the biggest is you
can't add a menu to the context menu using a 32 bit DLL. You can
add a menu though without a DLL.

Also a bug in their API to access Program Files has not been fixed,
doubt the gigolos will have much for us to work with.
With their small size brain, they think they got us by the balls.



"Anthony" <Anthony@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:47D55D9C-1F71-4F4B-823C-7B9F0E3D7248@xxxxxxxxxxxxxxxx
I am hoping this is a subject suitable for this newsgroup, since I know it
can be a sensitive one. Hoping to avoid namecalling here, I have a
question
which I could really use some opinions on.

I work for a a small software company. Our entire application suite is
written in Visual Studio 6 (primarily VB6). We looked at VB.NET when it
came
out, but decided against it because (1) our code wouldn't convert, (2) the
framework seemed overly large for shareware downloads, (3) anyone that
wanted
to could decompile our code, and (4) the final application seemed very
sluggish (slow) compared to a vb6 app. Seemed to us the .NET framework was
great for corporations, but not so great for small companies selling
software.

Now VB 2005 is out, we have looked at it, and it has some nice new stuff,
but still suffers from the same items above.

We now know that Vista will support VB6 apps (good news of course). This
buys us 6 or so years to start a long-term migration to another coding
platform. Our dilema is whether or not we should keep coding in VB6 from
this
point foreward. We wonder if Microsoft will somehow purposely kill the
functionality of the VB6 runtime in the os after Vista. Should we hold out
hope that some company will save the day and revive VB6? What is their
history of supporting the VB 1,2,3,4 and 5 runtimes?

If we SHOULD NOT continue with VB6, should we consider moving to VB 2005?
I
personally hesitate to move there based on the issues above. What else is
a
viable option? C++? Java? Delphi? It would take us 2 years to just get our
apps into a new system (and thats just maintaining what they already do -
not
really upgrading any functionality - essentially 2 years to get back to
square one). If we are going to make a move, I don't want to EVER have to
do
this again. I hesitate to go to a microsoft platform in fear they will
pull
the rug like they did with VB6.

Anybody facing the same dilema? Any food for thought?

Thanks -





.

Relevant Pages

  • Re: Hi all.
    ... I don't complain so much about the coding in DONT NET since I've made ... Then Microsoft optimized he code and now, ion VB6 ... Maybe I can do some coding in both, but I don't know if there are hidden ... Look for groups with 'dotnet' in the name. ...
    (microsoft.public.vb.general.discussion)
  • Re: VB6, VB2005, or Something Else?
    ... written in Visual Studio 6 (primarily VB6). ... vb6 app. ... man-hours rewriting code just to get back to where they are now so that they ... functionality - essentially 2 years to get back to square one). ...
    (microsoft.public.vb.general.discussion)
  • Re: Which Back-End Affordable Database do you RECOMMEND???
    ... when you're creating a VB6 app that is going to need an *affordable* ... To give you a bit of a benchmark, though I have used SQL Server in the ... database that works well with VB6. ... I'm migrating because I think it's only a matter of time before the MSDE ...
    (microsoft.public.vb.general.discussion)
  • Re: VB.NET Discussion
    ... I just opened VB 6.0 and started coding. ... > this and want it to be just an upgrade to VB6. ... and VB6 remains a viable tool for ... > Remove the crap from my email address before using. ...
    (microsoft.public.vb.general.discussion)
  • Multi threading using COM interop and firing events
    ... exposed to VB6 via COM. ... The .NET library is using asynchronous sockets to connect to a server. ... The event is generated from the worker thread and is not ... being raised in the VB6 app as intended. ...
    (microsoft.public.dotnet.languages.csharp)