Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Can I add a shortcut with InnoSetup?
Message
De
04/04/2006 14:04:52
 
 
À
04/04/2006 12:11:35
Information générale
Forum:
Visual FoxPro
Catégorie:
Installation et configuration
Versions des environnements
Visual FoxPro:
VFP 7 SP1
Divers
Thread ID:
01110286
Message ID:
01110347
Vues:
50
This message has been marked as a message which has helped to the initial question of the thread.
>>>While installing my app can I add a shortcut?
>>
>>In the help file, look up "[icons]" in the index. But do yourself a favour and get a copy of istool. It's donationware.
>
>I already use IStool. I looked up [icons] in the index and got nothing in return.
>
>So I'm still stuck. I'm able to add an icon in the menu but I don't know how to add a shortcut.

Did you look up [icons] in istool, or in Innosetup. Make sure you're looking in Innosetup's help.

For the record, here is the section from the help file:
[Icons] section

This optional section defines any shortcuts Setup is to create in the Start Menu 
and/or other locations, such as the desktop. 

Here is an example of an [Icons] section: 

[Icons] 
Name: "{group}\My Program"; Filename: "{app}\MYPROG.EXE"; WorkingDir: "{app}" 
Name: "{group}\Uninstall My Program"; Filename: "{uninstallexe}"

The following is a list of the supported parameters: 

Name  (Required) 
	Description: 
The name and location of the shortcut to create. Any of the shell folder 
constants or directory constants may be used in this parameter. 
	Keep in mind that shortcuts are stored as literal files so any characters not 
	allowed in normal filenames can't be used here. Also, because it's not 
	possible to have two files with the same name, it's therefore not possible to 
	have two shortcuts with the same name. 

	Examples: 
Name: "{group}\My Program" 
Name: "{group}\Subfolder\My Program" 
Name: "{userdesktop}\My Program" 
Name: "{commonprograms}\My Program" 
Name: "{commonstartup}\My Program" 

Filename  (Required) 
	Description: 
The command line filename for the shortcut, which normally begins with a 
directory constant. 
	Examples: 
Filename: "{app}\MYPROG.EXE" 
Filename: "{uninstallexe}" 
Parameters 
	Description: 
Optional command line parameters for the shortcut, which can include constants. 
	Example: 
Parameters: "/play filename.mid" 
WorkingDir 
	Description: 
The working (or Start In) directory for the shortcut, which is the directory in 
which the program is started from. If this parameter is not specified or is 
blank, Windows will use a default path, which varies between the different 
Windows versions. This parameter can include constants. 

	Example: 
WorkingDir: "{app}" 
HotKey 
	Description: 
The hot key (or "shortcut key") setting for the shortcut, which is a combination 
of keys with which the program can be started. 
	Note: If you change the shortcut key and reinstall the application, Windows 
	may continue to recognize old shortcut key(s) until you log off and back on or 
	restart the system. 
	Example: 
HotKey: "ctrl+alt+k" 
Comment 
	Description: 
Specifies the Comment (or "description") field of the shortcut, which determines 
the popup hint for it in Windows 2000, Me, and later. Earlier Windows versions 
ignore the comment. 

	Example: 
Comment: "This is my program" 
IconFilename 
	Description: 
The filename of a custom icon (located on the user's system) to be displayed. 
This can be an executable image (.exe, .dll) containing icons or a .ico file. If 
this parameter is not specified or is blank, Windows will use the file's default 
icon. This parameter can include constants. 
	Example: 
IconFilename: "{app}\myicon.ico" 
IconIndex 

	Default: 
0 
	Description: 
Zero-based index of the icon to use in the file specified by IconFilename. 
	If IconIndex is non-zero and IconFilename is not specified or is blank, it 
	will act as if IconFilename is the same as Filename. 
	Example: 
IconIndex: 0 
Flags 
	Description: 
This parameter is a set of extra options. Multiple options may be used by 
separating them by spaces. The following options are supported: 

closeonexit 
When this flag is set, Setup will set the "Close on Exit" property of the 
shortcut. This flag only has an effect if the shortcut points to an MS-DOS 
application (if it has a .pif extension, to be specific). If neither this flag 
nor the dontcloseonexit flags are specified, Setup will not attempt to change 
the "Close on Exit" property. 

createonlyiffileexists 
When this flag is set, the installer will only try to create the icon if the 
file specified by the Filename parameter exists. 

dontcloseonexit 
Same as closeonexit, except it causes Setup to uncheck the "Close on Exit" 
property. 

runmaximized 
When this flag is set, Setup sets the "Run" setting of the icon to "Maximized" 
so that the program will be initially maximized when it is started. 

runminimized 
When this flag is set, Setup sets the "Run" setting of the icon to "Minimized" 
so that the program will be initially minimized when it is started. 

uninsneveruninstall 
Instructs the uninstaller not to delete the icon. 

useapppaths 
When this flag is set, specify just a filename (no path) in the Filename 
parameter, and Setup will retrieve the pathname from the 
"HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths" 
registry key and prepend it to the filename automatically. 

	Example: 
Flags: runminimized 
Components and Tasks Parameters 
Common Parameters
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform