Re: VS 2003 Deployment package issues

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

On 1, a reboot shouldn't be necessary because MSI broadcasts the "settings
changed" message, so it's a bit odd that your app doesn't pick them up
automatically (although Services behave differently). In general,
ScheduleReboot is what you need, although it's often easier to fix the app
rather than manually edit the MSI file as well as reboot the user.

On 2, that's the way MSI works. It's repair. Whatever tweaks you could use
(like DISABLEADVTSHORTCUTS, but no IDE support in VS setup projects)
ultimately won't be a complete solution because the user can always initiate
a manual repair.
http://ablog.apress.com/?p=868#more-868

--
Phil Wilson
[Microsoft MVP-Windows Installer]
Definitive Guide to Windows Installer
http://apress.com/book/bookDisplay.html?bID=280

"Roger Miller" <RogerMiller@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:03420747-A6A6-4F03-B1C5-9715A8F67D6F@xxxxxxxxxxxxxxxx
I have a moderate sized deployment project developed in c#/vs2003 that
works
well but has two lingering issues I haven't figured out.

1) After the MSI is deployed, I would love to reboot automatically. Setup
modifies enviroment variables (amoung other things) so a reboot is
necessary
before my app can run. Is there a way to do this? Or at least a typical
popup saying "Restart required. Restart now? -OK (reboot now) -Cancel
(reboot later)." and kick it off ?

2) After the MSI has been deployed, if any of the deployed files have been
removed manually (yes I know this is bad for various reasons but ...) if
the
main app is launched from a deployed shortcut, the app *knows* that its
files
have been modified and it immediately attempts to reinstall. This usually
fails b/c there is also a deployed service that is installed and already
running. I'm not sure what my ultimate desired behavior is, but I would
like
to understand what's going on and what options I have for
modifying/controlling this behavior.

Thanks,
Roger
Roger


.

Relevant Pages

  • Re: Why does my installer not work?
    ... I have just used this to successfully create a MSI for a Windows Mobile app. ... What I did was after adding the system folder was to add a subfolder to it ... variables in the installer class to point to the app. ...
    (microsoft.public.dotnet.framework.compactframework)
  • Re: Rollbacking from custom action
    ... I am using Setup wizard of Visual studio 2005 to create an MSI. ... set by "Parents"'s installer say HKLM\software\Parent. ... App "Child" which needs Parent of version 5 or later. ...
    (microsoft.public.dotnet.framework.setup)
  • Why does my installer not work?
    ... I need to create an MSI for my app. ... msdn. ... variables in the installer class to point to the app. ...
    (microsoft.public.pocketpc.developer)
  • Why does my installer not work?
    ... I need to create an MSI for my app. ... msdn. ... variables in the installer class to point to the app. ...
    (microsoft.public.dotnet.framework.compactframework)
  • Re: Compact Framework App Installation Fails on PPC 2003 2nd
    ... did you rebuild the CAB from the generated batch ... Yes MSI is created using standard VS.Net setup project ... That includes new emulators so you can test your app ... >>> If I copy the CAB file onto the device and run it, the app installs ...
    (microsoft.public.dotnet.framework.compactframework)