<13******@gmail .comwrote in message
news:91******** *************** ***********@i12 g2000prf.google groups.com...
>I am in the process of writing programs using VB6 in XP Pro. However,
I am thinking about starting over using VB2005 as my company is
migrating to Vista.
Two questions...
What kinds of problems will I have installing and running my VB6 app
under Vista?
You need a Vista manifest for the program so that it will run on Vista with
the proper privileges. You need a Vista manifest to run programs with the
proper privileges such as Run as Administrator on Vista, even .Net
solutions.
>
If I develop VB2005 apps under XP, what kinds of problems will I have
installing and running under Vista?
The problem you will face is picking up or using DLL(s) on XP (DLL hell
deployment ) that may not work on Vista or that may cause Vista to crash.
Although XP and Vista are NT based O/S(s), they are different under the
hood. All you have to do is to step into any Vista NG and see the various
problems of some user installing non Vista compliant such as XP based
solution on to the machine running Vista to watch things blow-up to hell and
back.
The rule of thumb is one complies/builds using the DLL(s) or whatnot from a
given platform and deploys the application with other needed components to
the platform it is intended to run on, Vista to Vista and XP to XP -- not XP
to Vista or Vista to XP.
This link may help you to not consider trying to ploy something you have
developed on XP thinking that it can be deployed to Vista and it may not
cause some problems.
http://blogs.zdnet.com/Ou/?p=785
If you're going to be developing on the Vista platform, then do your home
work and find out what's happening on the hood of Vista from a software
development standpoint, because Vista is not XP.
