Differences between VB5 and VB6
in [Visual Basic]
|
From: MM on 16 Feb 2010 09:15 On Tue, 16 Feb 2010 09:50:54 -0000, "Mike Williams" <Mike(a)WhiskyAndCoke.com> wrote: > >"Horst Heinrich Dittgens" <hhd71(a)sofort-mail.de> wrote in message >news:hle1p6$g9j$00$1(a)news.t-online.com... > >> [regarding running from CD / USB memory stick etc] >> Well, this does convince me immediately. But shame to >> me, even writing Basic apps for years I never did work >> with manifests (it simply did work for me without that). > >That'll probably because your programs did not happen to use things that >would otherwise need to be registered. > >> Where can I learn more about how to use manifest files >> for registration free use of components (don't say read >> online help - that's what I always tell my clients <bg>)? > >The best place to start is here . . . > > http://mmm4vb6.atom5.com/ > >. . . where you'll be able to download the latest version of the "Make My >Manifest" program, which is excellent. The download contains all the >information you'll need to get started, but essentially all you need to do >is point MMM at one of your VB projects and it will analyze it and create >the required manifest for you, either as a separate manifest file or >embedded into your compiled VB exe file, whichever you choose. > >Mike New users of MMM should just be aware of the caveat (from the author to me) to use a DEPS folder for any COM Dlls/ActiveX controls. Horst could download my app and look at the manifest file and the folder tree, whereupon it should become self-explantory. In summary, have a main folder, e.g. MyApp and create a subfolder in it called Deps (you can actually name it anything you like). Place the ..exe, manifest, .ini, etc in the MyApp folder and place files like COMDLG32.OCX, MSCOMCTL.OCX, MSFLXGRD.OCX etc in the Deps folder. Any non-COM "helper" DLLs can go in the MyApp folder. For example, I have a Freeware vbhlp32.dll from Softcircuits that contains various high speed bit shifting routines and other useful stuff. This goes in the MyApp folder. MM
From: Paul Clement on 16 Feb 2010 09:24 On Thu, 11 Feb 2010 14:39:35 -0800 (PST), NadCixelsyd <nadcixelsyd(a)aol.com> wrote: � I'm an old school QuickBasic programmer with hundreds of programs that � will not work on my new 64-bit computer. In the past, I've used VB5 � only when QB won't do it (e.g. mouse support). Now I'm about to re- � write my programs in VB before my old computer bytes the dust. � � Should I upgrade to VB6? Should I learn VB.NET? Where can I find VB6 � features not available in VB5? Googling, "VISUAL BASIC 5 6 � DIFFERENCES" didn't work. There is no upgrade available from version 5.0 to 6.0, and support is limited to the run time libraries. If you're looking to work in a current environment try Visual Basic Express Edition. It's free so if you don't like it you can stick with VB 5.0 or find a used copy of VB 6.0 somewhere. http://www.microsoft.com/express/Downloads/#2008-Visual-Basic Paul ~~~~ Microsoft MVP (Visual Basic)
From: Karl E. Peterson on 16 Feb 2010 21:13 Horst Heinrich Dittgens wrote: > I always wonder why it's such a big disussion about VB runtimes to be > included or not in a future OS version. If they include the runtime with the OS, they're on the hook to support it for the same support life as the OS itself. The VB6 runtime currently enjoys a support life sunsetting in 2019. :-) -- ..NET: It's About Trust! http://vfred.mvps.org
From: MM on 17 Feb 2010 01:51 On Tue, 16 Feb 2010 18:13:20 -0800, Karl E. Peterson <karl(a)exmvps.org> wrote: >Horst Heinrich Dittgens wrote: >> I always wonder why it's such a big disussion about VB runtimes to be >> included or not in a future OS version. > >If they include the runtime with the OS, they're on the hook to support >it for the same support life as the OS itself. The VB6 runtime >currently enjoys a support life sunsetting in 2019. :-) ....by which date I shall be 73 and past caring. MM
From: Horst Heinrich Dittgens on 17 Feb 2010 07:23
Thank you very much! That's why I still love usegroups. |