This problem was reported by our QA department who are all running XP. I am
running 2003 Server.
When you say 'Notepad' you are referring to FoobarAppl10.exe, right?
The log that I sent does not include code 1903. Do our logs otherwise
match? When you say the file was moved to Config.MSI, does that mean it is
no longer in the installation folder?
I just retried the test by using a virtual machine running XP. I should
have done this test first before starting this thread because the behavior
is a bit different. I installed the test package that I sent to you. I
started the shortcut, then started the uninstall. When prompted to close
Notepad, I chose Ignore. I still was not prompted for a reboot. When I did
reboot, the file was gone but the folders (Acme\Foobar10) were still there.
Then I tried the same test with my application. Same results....no prompt
for reboot, but *all* files gone after reboot and install folders left
behind.
This is much different than the behavior of my own PC. Is it possible that
there is a domain policy causing this? Our IT dept has just started using
AD to push applications and maybe they have added a setting the the Group
Policy that they don't completely understand.
Thanks for your time on this.
On 11/23/06, Bob Arnson <[EMAIL PROTECTED]> wrote:
Adding *wix-users* back to the thread.
John Lalande wrote:
I copied Notepad.exe to a folder shared with Sample.wxs and changed its
name to FoobarAppl10.exe. Then I compiled. I ran the resulting installer
and fired up the app from the desktop shortcut. Without closing the app, I
started the uninstall. When the uninstall warned me that I should shut down
the application, I clicked Ignore. The uninstall proceeded, but did not
prompt for a reboot. I rebooted anyway and found that FoobarAppl10.exewas
still on the disk.
On my machine, leaving Notepad open causes the built-in FilesInUse dialog
to be displayed. When I hit Ignore, the uninstall continues. MSI moves the
.exe into its private Config.MSI directory. There's a code 1903 in the log
indicating that a reboot is required but because the file was moved, there
isn't a good enough reason to force a reboot.
I can't reproduce the behavior you get. I was running on XP. Which OS are
you testing on?
--
sig://boB
http://bobs.org
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
