Files-In-Use Extension for Inno Setup
First of all I would like to give a big thanks to Jordan Russell for the best freeware installer for Windows programs: Inno Setup. If you need to deploy your applications this is the best free tool you will find, trust me. If you don't want to write script by hand you can always use ISTool to edit these scripts faster in a visual and easy environment.
Files-In-Use functionality is among the countless services that Windows Installer exposes for setup authors to leverage for their application install/maintenance. This functionality lets setup authors display the processes that hold on to files that would be updated by this install. The user would want to shut those processes before continuing with the install to ensure that the install wouldn’t require a reboot.
Now you can do the same thing with Inno Setup avoiding unnecessary reboots when installing your application exe files / plugin / shell extension / ocx etc with My Files In Use Extension for Inno Setup
Features:
- small size (it will add less than 20KB to your setup. )
- multi-language support (you can add or modify the language file)
- multiple file search (a semicolon list with exe/dll/ocx names and path can be used)
- wildcard file match ( * = matches any characters, zero or more times ; ? = matches any character, one time )
- exact folder match (detect if your file is in use only from a specified folder )
- applications exe names will be listed not just their description
- both 32 and 64 bit applications detection (Vista & XP x64 )
- user friendly: applications are displayed along with their icon
- possibility to end the detected process forcedly (right click on process for more options)
- easy to use and 100% free
How do I get it to work with Inno?
1. Download latest File In Use Extension for Inno (IssProc.dll and Inno script demo included)
2. Add the extension (IssProc.dll) in your [Files] section script :
-
[Files]
-
;------ add Files In Use Extension
-
Source: IssProc.dll; DestDir: {tmp}; Flags: dontcopy
-
;------ add Files In Use Extension extra language file (you don t need to add this file if you are using english only)
-
Source: IssProcLanguage.ini; DestDir: {tmp}; Flags: dontcopy
-
;------ Copy IssProc.dll in your app folder if you want to use it on unistall
-
Source: IssProc.dll; DestDir: {app}
-
Source: IssProcLanguage.ini; DestDir: {app}
-
;------
3. Add below code in your [Code] section script (you can modify it as you like):
-
[Code]
-
// IssFindModule called on install
-
function IssFindModule(hWnd: Integer; Modulename: PChar; Language: PChar; Silent: Boolean; CanIgnore: Boolean ): Integer;
-
external 'IssFindModule@files:IssProc.dll stdcall setuponly';
-
-
// IssFindModule called on uninstall
-
function IssFindModuleU(hWnd: Integer; Modulename: PChar; Language: PChar; Silent: Boolean; CanIgnore: Boolean ): Integer;
-
external 'IssFindModule@{app}\IssProc.dll stdcall uninstallonly';
-
-
//********************************************************************************************************************************************
-
// IssFindModule function returns: 0 if no module found; 1 if cancel pressed; 2 if ignore pressed; -1 if an error occured
-
//
-
// hWnd = main wizard window handle.
-
//
-
// Modulename = module name(s) to check. You can use a full path to a DLL/EXE/OCX or wildcard file name/path. Separate multiple modules with semicolon.
-
// Example1 : Modulename='*mymodule.dll'; - will search in any path for mymodule.dll
-
// Example2 : Modulename=ExpandConstant('{app}\mymodule.dll'); - will search for mymodule.dll only in {app} folder (the application directory)
-
// Example3 : Modulename=ExpandConstant('{app}\mymodule.dll;*myApp.exe'); - just like Example2 + search for myApp.exe regardless of his path.
-
//
-
// Language = files in use language dialog. Set this value to empty '' and default english will be used
-
// ( see and include IssProcLanguage.ini if you need custom text or other language)
-
//
-
// Silent = silent mode : set this var to true if you don't want to display the files in use dialog.
-
// When Silent is true IssFindModule will return 1 if it founds the Modulename or 0 if nothing found
-
//
-
// CanIgnore = set this var to false to Disable the Ignore button forcing the user to close those applications before continuing
-
// set this var to true to Enable the Ignore button allowing the user to continue without closing those applications
-
//******************************************************************************************************************************************
-
-
-
function NextButtonClick(CurPage: Integer): Boolean;
-
var
-
hWnd: Integer;
-
sModuleName: String;
-
nCode: Integer; {IssFindModule returns: 0 if no module found; 1 if cancel pressed; 2 if ignore pressed; -1 if an error occured }
-
begin
-
Result := true;
-
-
if CurPage = wpReady then
-
begin
-
Result := false;
-
ExtractTemporaryFile('IssProcLanguage.ini'); { extract extra language file - you don't need to add this line if you are using english only }
-
hWnd := StrToInt(ExpandConstant('{wizardhwnd}')); { get main wizard handle }
-
sModuleName :=ExpandConstant('{app}\Myprog.exe'); { searched modules. Tip: separate multiple modules with semicolon Ex: '*mymodule.dll;*mymodule2.dll;*mymodule3.dll'}
-
-
nCode:=IssFindModule(hWnd,sModuleName,'en',false,true); { search for module and display files-in-use window if found }
-
//sModuleName:=IntToStr(nCode);
-
// MsgBox ( sModuleName, mbConfirmation, MB_YESNO or MB_DEFBUTTON2);
-
-
if nCode=1 then begin { cancel pressed or files-in-use window closed }
-
PostMessage (WizardForm.Handle, $0010, 0, 0); { quit setup, $0010=WM_CLOSE }
-
end else if (nCode=0) or (nCode=2) then begin { no module found or ignored pressed}
-
Result := true; { continue setup }
-
end;
-
-
end;
-
-
end;
-
-
-
function InitializeUninstall(): Boolean;
-
var
-
sModuleName: String;
-
nCode: Integer; {IssFindModule returns: 0 if no module found; 1 if cancel pressed; 2 if ignore pressed; -1 if an error occured }
-
-
begin
-
Result := false;
-
sModuleName := ExpandConstant('*Myprog.exe;'); { searched module. Tip: separate multiple modules with semicolon Ex: '*mymodule.dll;*mymodule2.dll;*myapp.exe'}
-
-
nCode:=IssFindModuleU(0,sModuleName,'enu',false,false); { search for module and display files-in-use window if found }
-
-
if (nCode=0) or (nCode=2) then begin { no module found or ignored pressed}
-
Result := true; { continue setup }
-
end;
-
-
// Unload the extension, otherwise it will not be deleted by the uninstaller
-
UnloadDLL(ExpandConstant('{app}\IssProc.dll'));
-
-
end;
4. Set sModuleName from the above code with your own modules names (separate multiple modules with semicolon)
5. Compile and test your setup. Before Inno will begin install operation The File In Use Extension will check if your modules (DLL's/exe's/ocx's names) are in use and it will popup with a window asking the user to close those applications. The user can choose to Ignore this and continue with setup rebooting at the end, or he can close those applications and click on Retry.
Version History
Download
Donate
Download
Build Notes
ReportWho's Using IssProc?
- ZGuideTV
( If you are you using IssProc and want to be listed here please let me know! )
related things:
Author: Raz | On March 17th, 2007 | [ En ], - Raz-Soft News | 13 Comments
Q: So what can I do next?
A: You can Buy me a Beer or Coffee. You can say Hi! or peek on the related stuff. You can follow any responses to this entry through the RSS 2.0 feed.
You can leave a response, or trackback from your own site.
Spammers: Beware of » my Dog! «
13 Responses to “Files-In-Use Extension for Inno Setup”
April 7th, 2007 at 11:22 am
Hi,
Is there a way to translate the popup window asking the user to close those applications? I need a translation for a germany setup file.
Thanks
April 7th, 2007 at 12:29 pm
Hi George,
The popup window is in English and there is no multi-language support for now, but multi-lang support is scheduled to be added in the next build.
Thanks
April 15th, 2007 at 10:33 pm
Multi-language support added in IssProc.dll v1.0.1
July 7th, 2007 at 11:06 am
My installation fails under Vista Enterprise x64, as well as the sample setup I've compiled from your sample.
I'm getting the following error immediately after launching setup:
---------------------------
Runtime Error (at -1:0):
Cannot Import dll:C:\TEMP\is-SL00G.tmp\IssProc.dll.
---------------------------
I tried changing the script to delay load your dll but it stll fails during the installation.
On Win98/2000/WinXP anything goes fine.
I wonder it might be smth with manifests, etc.
July 7th, 2007 at 11:32 am
Hi Crulex,
It looks like Inno Setup cannot Import the DLL in Vista Enterprise x64. I guess the only thing that causes the failure is the extension packer (used to reduce the size). The only thing I can do is to send you the unpacked version of the extension, you can download it from here
Please let me know if the unpacked version works on your installlation.
July 12th, 2007 at 4:23 am
I am using your unpacked version on Vista 64 Business edition as the other one wont work. If possible could you please add detection of 64 bit programs?
July 12th, 2007 at 12:41 pm
Hi Raz,
Thanks for the feedback, I've just needed to resolve this issue today.
The unpacked version works very well on my Vista x64 installation.
I've found that the packed version installs correctly if I turn off DEP on my Vista installation by running the following command from the command prompt with administrative privileges:
bcdedit.exe /set {current} nx AlwaysOff
It seems that a lot of the execiutable packers are incompatible with DEP
September 25th, 2007 at 9:55 am
Hi all,
IssProc v1.0.2 is out: no more packer and DEP problems (i hope), support for both 32 & 64 apps, fully tested on XP and Vista x64 and more user friendly. Let me know your thoughts
Thank you
November 13th, 2007 at 1:45 pm
Hi,
During install in english we can see on the main form 'Setup - My Program' and in french 'Installation - My program' ... great !
But during uninstall in english we can see on the main form 'Setup' and in french 'setup'
It should be great during uninstall to see in english 'Setup - My Program' and in french 'Désinstallation - My Program' like in inno setup !
I do not really understand how to add a second language in the code (french and english). Could you give me an example please ?
I've translated the IssProcLanguage.ini file in french. If you want this one email me please
Thanks for all
Neo
November 13th, 2007 at 2:27 pm
Hi Neo,
For now caption on install/uninstall can not be set from language file but I will add that on my "to do list".
For your translation: in the file IssProcLanguage.ini file create a section called [fr] (used on install ) and [fru] (unsinstall) and add your translated variables just like those in english, something like this (you can copy the below code and translate):
After you add (and translate) the above sections use "fr" and "fru" for language param of IssProc function like this:
and on uninstall like this:
Please send you translation file at: razvar .at. gmail .dot. com and I will reply you with the working/modified french one.
Thanks
November 13th, 2007 at 3:42 pm
Hi,
Yes working great with : nCode:=IssFindModule(hWnd,sModuleName,'fr',false,true);
and : nCode:=IssFindModule(hWnd,sModuleName,'fru',false,true);
But in fact I use innosetup in multi language in my case the users select english or french during the first screen !
And right now I just can use IssProc in english or french but not the both.
I hope you understand what I mean !
Neo
November 15th, 2007 at 7:55 pm
Hi Neo,
You must modify your script and put additional checks: If the user has selected the english language then use IssProg with 'en' value on the language param. If it selects french then use IssProc with 'fr' and so on...You must have some experience with inno script (delphi/pascal) to make that work.
I can help you out with that too, but right now time is not on my side. Send me your script (attach the language file as well) and I shall modify it for you one more time
Raz
May 17th, 2008 at 1:37 am
Hi,
Is it possible to get the name and icon of the file-in-use from the app's main window, instead of getting it from the FileVersion info? This is what Task Manager does for the "Applications" tab, as it is generally more useful/correct than just the FileVersion info.
The exact problem I'm having is this: when the file-in-use is a Java app, IssProc will display something like "Java (TM) 2 Platform Standard Edition binary (javaw.exe)" with the ugly default icon. Of course, most users have no idea what that is!
I think that getting the icon and name from the FileVersion info is a good backup strategy for processes that don't have any windows.
Thanks for a nice utility!
Daniel