[font="trebuchet ms"]Hi,
[font="trebuchet ms"]
[font="trebuchet ms"]Can u pls help me in calling the 'File in use' dialog in Basic MSI project.
[font="trebuchet ms"]
[font="trebuchet ms"]When i install my msi with with winword open, the installer launches the 'File in use' dialog. This way it is good.
[font="trebuchet ms"]
[font="trebuchet ms"]But when an instance of winword is opened by someother application(say, When outlook is opened, it might have winword as its editor, so a winword.exe instance will be running), the installer is not showing the 'file in use' dialog. Rather, it is throwing an error.
[font="trebuchet ms"]
[font="trebuchet ms"]So, i created a VBScript CA which checks for any instances of winwor.exe is running and popped up a msg 'Please close any instances of winword, before installing this application', and aborted the installation.
[font="trebuchet ms"]
[font="trebuchet ms"]But I need to provide the user, the option to close the winword instances that are running, rather than just aborting the installation.
[font="trebuchet ms"]
[font="trebuchet ms"]Please help me in achieving this.
[font="trebuchet ms"]
[font="trebuchet ms"]Thanks.
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
Do I have this right, that your script currently prompts the user to close WinWord and then exits? If so, you simply need to alter your script to loop until the WinWord process no longer exists, having prompted the user, and then continue. If it were me, I'd build in a counter and have a 'Cancel' button so that the script can exit the loop after 'x' iterations and the user can cancel the install if they want.
Answered 06/10/2008 by: VBScab
Red Belt

Please log in to comment
0
[font="trebuchet ms"]
[font="trebuchet ms"]Yes, u r right. But i feel this is a workaround for my problem.
[font="trebuchet ms"]
[font="trebuchet ms"]Because at times, the user may wonder how to close the 'winword.exe' instance, since winword is not actually opened(he may not know to close it from task manager). In those cases, if we could show the application which is holding winword(or which needs to be closed), it would be a good choice.
[font="trebuchet ms"]
[font="trebuchet ms"]That's y i thought of using the 'FileinUse' dialog. I believe this dialog does what i said.
[font="trebuchet ms"]
[font="trebuchet ms"]Can't this be achieved??
[font="trebuchet ms"]
[font="trebuchet ms"]Thanks Ian.
[font="trebuchet ms"]
[font="trebuchet ms"]
Answered 06/10/2008 by: vijayakumar
Orange Belt

Please log in to comment
0
[font="trebuchet ms"]Any suggesions on this?
[font="trebuchet ms"]
[font="trebuchet ms"]Thanks.
Answered 06/10/2008 by: vijayakumar
Orange Belt

Please log in to comment
0
As ever, Google to the rescue... search term was:

. "windows installer" "file in use" -appdeploy

http://blogs.msdn.com/windows_installer_team/archive/2006/12/11/windows-installer-and-restart-manager-msi-files-in-use-v2.aspx
It's do-able but then this is meat-and-potatoes to a hacker like me. You may not want to venture this far for what is utlimately a simple thing to achieve. Most setups are happy to just tell users to close everything.
Answered 06/11/2008 by: VBScab
Red Belt

Please log in to comment
Answer this question or Comment on this question for clarity