Re: PDW, Registry, Unistall and VB6.

Message has been deleted

MikeD

unread,

Mar 27, 2007, 9:06:48 PM3/27/07

to

"Fabio" <f.vi...@gmail.com> wrote in message
news:1174914663.9...@b75g2000hsg.googlegroups.com...
>I have a lot of VB6 applications.
> I use Package & Deployment Wizard (included in Visual Sudio 6) to
> create the setup.
> After an installation of one application, when I want uninstall it,
> some key registry aren't removed and I must remove them manually.
> Is there a method to know which keys are created by an installation
> with PDW and so remove all them during unistall?
>

The PDW uninstaller WILL remove whatever the PDW Setup program creates in
the Registry.

If your app creates the Registry key (or anything in the Registry), the
Setup program and the uninstaller know nothing about it and therefore the
uninstaller won't remove it. This is NOT uncommon. MOST programs, when
uninstalled, leave junk in the Registry. I'm not saying that's good or even
acceptable. I'm just saying that's the way it is. For an uninstaller to
remove things in the Registry that the installer program didn't create, the
uninstaller needs specifically written to remove them. PDW doesn't provide
this. You'd need your application to modify the uninstall log file when your
app creates new keys/entries in the Registry. The best way to figure out how
to do this is to look at the pertinant code in Setup1.vbp, which is included
with VB.

--
Mike
Microsoft MVP Visual Basic

Fabio

unread,

Mar 28, 2007, 9:15:42 AM3/28/07

to

> The PDW uninstaller WILL remove whatever the PDW Setup program creates in
> the Registry.
>
> If your app creates the Registry key (or anything in the Registry), the
> Setup program and the uninstaller know nothing about it and therefore the
> uninstaller won't remove it. This is NOT uncommon. MOST programs, when
> uninstalled, leave junk in the Registry. I'm not saying that's good or even
> acceptable. I'm just saying that's the way it is. For an uninstaller to
> remove things in the Registry that the installer program didn't create, the
> uninstaller needs specifically written to remove them. PDW doesn't provide
> this. You'd need your application to modify the uninstall log file when your
> app creates new keys/entries in the Registry. The best way to figure out how
> to do this is to look at the pertinant code in Setup1.vbp, which is included
> with VB.
>
> --
> Mike
> Microsoft MVP Visual Basic

My app doesn't create the Registry keys.
PDW creates them and sometimes it doesn't remove all keys when I
uninstall the app.
I saw the uninstall log file and there aren't all registry keys
created.
I don't know Setup1.vbp. It's possible write into log all keys
created.
Can you give me some more information about that?
Thanks

Jan Hyde

unread,

Mar 28, 2007, 10:58:44 AM3/28/07

to

"Fabio" <f.vi...@gmail.com>'s wild thoughts were released
on 28 Mar 2007 06:15:42 -0700 bearing the following fruit:

It might help if you tell us which registry keys your
talking about.

Fabio

unread,

Mar 29, 2007, 4:30:36 AM3/29/07

to

I have 4 standard (.exe) apps and 5 com+ apps (.dll) used by .exe.
They are vb6 apps.
I created setup for all of them with PDW (com+ apps have 2
setup:server and proxy).
I installed all proxy components of com+ apps and all exe apps into my
workstation, it's used for development too.
I think that this is the problem!!!!
I modify the com+ apps, and update the dlls used by proxy (I overwrite
them) and so when I uninstall them the registry isn't clean
completely.
About your opinion, is correct this?