Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Rhinorhino on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
ActiveX in Vista 1
- Thread starter sacsac
- Start date
- Thread starter
- #3
I did not mean that I personally had experienced any installation problems - I have not even tried to install my apps on a Vista machine.
However, I am just picking up rumours that there can be difficulties with getting controls successfully installed/registered if not logged in as Administrator (I saw a report which stated that it was not sufficient to have Admin rights, but the login actually had to be the Administrator). Also, I am confused by the talk of MS not supporting VB6. Does this mean that the VB6 runtime file will not function correctly? Any help or comments appreciated.
However, I am just picking up rumours that there can be difficulties with getting controls successfully installed/registered if not logged in as Administrator (I saw a report which stated that it was not sufficient to have Admin rights, but the login actually had to be the Administrator). Also, I am confused by the talk of MS not supporting VB6. Does this mean that the VB6 runtime file will not function correctly? Any help or comments appreciated.
- Thread starter
- #5
StrongM - I have seen quite a lot of comment about support ceasing for VB6 (mainly on the websites of the 'classic VB' supporters). Maybe this means telephone/on-line support, rather than VB6 being 'supported' by the new Vista OS. Perhaps it's just me being paranoid!
HughLerwill
Programmer
Strongm,
I guess the vb5/6 runtime is still being included with a Vista installation like it was since (about) the W2k vintage OS?
I guess the vb5/6 runtime is still being included with a Vista installation like it was since (about) the W2k vintage OS?
-
1
- #8
dilettante
MIS
The other consideration with ActiveX/COM is the use of Reg-Free COM in XP, 2003, and Vista where it makes sense. But most of the issues with ActiveX will be related to the installer you employ.
The biggest issues with Vista are UAC related but these apply to pretty much all development tools and the applications they produce. There are a few "snags" with VB6 features that (in theory) we weren't supposed to be using even on Win2K and WinXP, let alone Vista (where they are now enforced). The most obvious is the use of GetSettings/SaveSettings, creating/writing files in "Program Files," etc.
There are actions you can take to avoid VB6 applications having App Compat workarounds applied in Vista too. The VB6 development tools won't handle this for you by themselves. Other issues are somewhat cosmetic, like avoiding the use of MsgBox in favor of ShellMessageBox. There are also places where you'd want to use ShellExecute instead of CreateProcess in order to have Vista's Application Information Service invoked when initiating new processes.
There are even workarounds to allow VB6 programs to use the Aero Glass look for forms and dialogs.
Of course none of this is directly available, so there is some learning and extra effort required to produce "proper" Vista programs in VB6. The good news is that many of the manual enhancements you can make will make your programs "better" XP programs too, and over time people will develop sets of modules and classes that will make Vista programming in VB6 easier.
Only a few Vista issues will interfere with the average VB6 program working as is under Application Compatability though.
The biggest issues with Vista are UAC related but these apply to pretty much all development tools and the applications they produce. There are a few "snags" with VB6 features that (in theory) we weren't supposed to be using even on Win2K and WinXP, let alone Vista (where they are now enforced). The most obvious is the use of GetSettings/SaveSettings, creating/writing files in "Program Files," etc.
There are actions you can take to avoid VB6 applications having App Compat workarounds applied in Vista too. The VB6 development tools won't handle this for you by themselves. Other issues are somewhat cosmetic, like avoiding the use of MsgBox in favor of ShellMessageBox. There are also places where you'd want to use ShellExecute instead of CreateProcess in order to have Vista's Application Information Service invoked when initiating new processes.
There are even workarounds to allow VB6 programs to use the Aero Glass look for forms and dialogs.
Of course none of this is directly available, so there is some learning and extra effort required to produce "proper" Vista programs in VB6. The good news is that many of the manual enhancements you can make will make your programs "better" XP programs too, and over time people will develop sets of modules and classes that will make Vista programming in VB6 easier.
Only a few Vista issues will interfere with the average VB6 program working as is under Application Compatability though.
>I did not mean that I personally had experienced any installation problems
Yes, I read that too fast.
>Application Compatability
No guarentee was given that this will be possible on post Vista versions. And the C:\program data writings get re-directed to the User Data folders, if not rejected, which may cause some head scatching. So brush up on those old W2k and XP guidelines and policies now.
And then there is hope for those older products with the now free "MS eatened" Vitual PC (and Vitual Server) with network capabilities ...
Yes, I read that too fast.
>Application Compatability
No guarentee was given that this will be possible on post Vista versions. And the C:\program data writings get re-directed to the User Data folders, if not rejected, which may cause some head scatching. So brush up on those old W2k and XP guidelines and policies now.
And then there is hope for those older products with the now free "MS eatened" Vitual PC (and Vitual Server) with network capabilities ...
dilettante
MIS
Yes, even Longhorn Server is still a big question mark regarding VB6 programs and the betas are about to begin.
- Status
Similar threads
- Locked
- Question
