Enabling Self-Repair Capability

[NewsArchive]

Hi all...

Regarding InstallShield Developer 7.01 (Standard Project): I hope I'm
overlooking something simple here... It seems that if I install my app with
the associated shortcuts NOT set as Advertised, the Windows Installer's
wonderful ability to repair the app if I delete the .exe or a critical .ocx
just doesn't happen... However, setting the shortcuts to Advertised allows
this self-repair capability to work fine after the app finally installs.

But if I set the shortcut to Advertised, it (of course) asks me for my
installation media the first time I try to run the app - yuck, my users
aren't going to like that. What's more, before the first attempt to run the
app, I can open the programs folder -- Lo And Behold! The .exe and all its
happy little siblings are there on the disk already! So why does the darn
thing have to nag me for the CD when I double-click the icon?

Ah, well... This would all be boring if we didn't have a few challenges now
and then.

Thanks in advance for any light you can shed on this.

Rick Bezouska
Senior Product Developer
VantageMed Corporation
rbezouska@vantagemed.com

[NewsArchive]

Calling it an advertised shortcut does not necessarily mean that the feature
is in an advertised state. A better term is probably "MSI Shortcut". And
you are required to use one to get the free repair that comes with using the
Windows Installer.

If you are seeing the installer launch when you start you application the
first time you may want to try running validation on your MSI package. You
also may want to try using a tool called MSISpy which comes with the
platform SDK. The problem is that one of your components *things* it is not
installed even though the files may be there. MsiSpy will tell you which
component is having the problem.


"Rick Bezouska" <rbezouska@vantagemed.com> wrote in message
news:3c0ec949$1@news.installshield.com...
> Hi all...
>
> Regarding InstallShield Developer 7.01 (Standard Project): I hope I'm
> overlooking something simple here... It seems that if I install my app
with
> the associated shortcuts NOT set as Advertised, the Windows Installer's
> wonderful ability to repair the app if I delete the .exe or a critical
..ocx
> just doesn't happen... However, setting the shortcuts to Advertised allows
> this self-repair capability to work fine after the app finally installs.
>
> But if I set the shortcut to Advertised, it (of course) asks me for my
> installation media the first time I try to run the app - yuck, my users
> aren't going to like that. What's more, before the first attempt to run
the
> app, I can open the programs folder -- Lo And Behold! The .exe and all
its
> happy little siblings are there on the disk already! So why does the darn
> thing have to nag me for the CD when I double-click the icon?
>
> Ah, well... This would all be boring if we didn't have a few challenges
now
> and then.
>
> Thanks in advance for any light you can shed on this.
>
> Rick Bezouska
> Senior Product Developer
> VantageMed Corporation
> rbezouska@vantagemed.com
>
>
>

[NewsArchive]

Awesome, David... and thank you. I am not in the office today so have not
yet been able to follow your suggestions. But I have read enough of your
replies here in the newsgroup to know that You Da Man... I expect to have no
further difficulties with this.

The Rest Of You: Listen to this guy, he knows his s**t

Gratefully,

Rick

"David Thornley" <davidt@installshield.com> wrote in message
news:3c0fdce5$1@news.installshield.com...
> Calling it an advertised shortcut does not necessarily mean that the
feature
> is in an advertised state. A better term is probably "MSI Shortcut". And
> you are required to use one to get the free repair that comes with using
the
> Windows Installer.
>
> If you are seeing the installer launch when you start you application the
> first time you may want to try running validation on your MSI package.
You
> also may want to try using a tool called MSISpy which comes with the
> platform SDK. The problem is that one of your components *things* it is
not
> installed even though the files may be there. MsiSpy will tell you which
> component is having the problem.
>
>
> "Rick Bezouska" <rbezouska@vantagemed.com> wrote in message
> news:3c0ec949$1@news.installshield.com...
> > Hi all...
> >
> > Regarding InstallShield Developer 7.01 (Standard Project): I hope I'm
> > overlooking something simple here... It seems that if I install my app
> with
> > the associated shortcuts NOT set as Advertised, the Windows Installer's
> > wonderful ability to repair the app if I delete the .exe or a critical
> .ocx
> > just doesn't happen... However, setting the shortcuts to Advertised
allows
> > this self-repair capability to work fine after the app finally installs.
> >
> > But if I set the shortcut to Advertised, it (of course) asks me for my
> > installation media the first time I try to run the app - yuck, my users
> > aren't going to like that. What's more, before the first attempt to run
> the
> > app, I can open the programs folder -- Lo And Behold! The .exe and all
> its
> > happy little siblings are there on the disk already! So why does the
darn
> > thing have to nag me for the CD when I double-click the icon?
> >
> > Ah, well... This would all be boring if we didn't have a few challenges
> now
> > and then.
> >
> > Thanks in advance for any light you can shed on this.
> >
> > Rick Bezouska
> > Senior Product Developer
> > VantageMed Corporation
> > rbezouska@vantagemed.com
> >
> >
> >
>
>