Home Explore Help
Sign In
pascal
/
innosetup
mirror of https://github.com/jrsoftware/issrc.git
2
0
Fork 0
Files Issues 0 Wiki
Browse Source

Documentation improvements.

Martijn Laan 7 years ago
parent
5d6ba5f6ff
commit
2465379e2f
3 changed files with 11 additions and 9 deletions
Split View Show Diff Stats
  1. 7 7
      ISHelp/isetup.xml
  2. 2 0
      ISHelp/isx.xml
  3. 2 2
      whatsnew.htm

+ 7 - 7
ISHelp/isetup.xml
View File 

@@ -63,12 +63,12 @@
 
     <contentstopic title="64-bit Installation Limitations" topic="64bitlimitations" />

     <contentstopic title="Wizard Pages" topic="wizardpages" />

     <contentstopic title="Installation Order" topic="installorder" />

-    <contentstopic title="Command Line Compiler Execution" topic="compilercmdline" />

+    <contentstopic title="Unsafe Files" topic="unsafefiles" />

+    <contentstopic title="Compiler Command Line Execution" topic="compilercmdline" />

     <contentstopic title="Setup Command Line Parameters" topic="setupcmdline" />

     <contentstopic title="Setup Exit Codes" topic="setupexitcodes" />

     <contentstopic title="Uninstaller Command Line Parameters" topic="uninstcmdline" />

     <contentstopic title="Uninstaller Exit Codes" topic="uninstexitcodes" />

-    <contentstopic title="Unsafe Files" topic="unsafefiles" />

     <contentstopic title="Miscellaneous Notes" topic="technotes" />

     <contentstopic title="Example Scripts" topic="examples" />

     <contentstopic title="Frequently Asked Questions" topic="faq" />

@@ -2098,9 +2098,9 @@ Name: "nl"; MessagesFile: "compiler:Languages\Dutch.isl"
 
 </param>

 

 <param name="MessagesFile" required="yes">

-<p>Specifies the name(s) of file(s) to read the default messages from. The file(s) must be located in your installation's <link topic="sourcedirectorynotes">source directory</link> when running the Setup Compiler, unless a fully qualified pathname is specified or the pathname is prefixed by "compiler:", in which case it looks for the file in the Compiler directory.</p>

-<p>When multiple files are specified, they are read in the order they are specified, thus the last message file overrides any messages in previous files.</p>

-<p>See the <link topic="messagessection">[Messages] section</link> help topic for details on the format of .isl files.</p>

+<p>Specifies the name(s) of the .isl file(s) to read the default messages from. The file(s) must be located in your installation's <link topic="sourcedirectorynotes">source directory</link> when running the Setup Compiler, unless a fully qualified pathname is specified or the pathname is prefixed by "compiler:", in which case it looks for the file in the Compiler directory.</p>

+<p>Each message file may contain a <link topic="langoptionssection">[LangOptions] section</link>, a <link topic="messagessection">[Messages] section</link>, and a <link topic="custommessagessection">[CustomMessages] section.</link></p>

+<p>When multiple files are specified, they are read in the order they are specified, thus the last message file overrides any language options or messages from previous files. Any language options or messages in the main script override the ones from message files.</p>

 <examples>

 <pre>

 MessagesFile: "compiler:Dutch.isl"

@@ -3051,7 +3051,7 @@ Filename: "{win}\MYPROG.INI"; Section: "InstallSettings"; Key: "InstallPath"; St
 
 <p>Optionally you could also use the <tt>skipifsilent</tt> and <tt>skipifnotsilent</tt> flags and make your application aware of a '/updated' parameter to for example show a nice message box to inform the user that the update has completed.</p>

 </li>

 

-<li>Inno Setup's own installers accept an additional /PORTABLE=1 command line parameter to enable portable mode.</li>

+<li>Inno Setup's own installers accept an additional /PORTABLE=1 command line parameter to enable portable mode which causes the installers to not create an uninstaller nor an entry in the Add/Remove Programs Control Panel applet.</li>

 

 <li>The Inno Setup backup website can be found at <extlink href="http://www.innosetup.nl/">www.innosetup.nl</extlink>. Normally this link will simply redirect you to the main website at <extlink href="http://www.jrsoftware.org/">www.jrsoftware.org</extlink> but in case of emergencies this redirect will be disabled.</li>

 

@@ -3512,7 +3512,7 @@ Keep the default set of selected tasks, but deselect the "desktopicon" task:<br/
 
 <keyword value="Unsafe Files" />

 <body>

 

-<p>As a convenience to new users who are unfamiliar with which files they should and should not distribute, the Inno Setup compiler will display an error message if one attempts to install certain "unsafe" files using the <link topic="filessection">[Files] section</link>. These files are listed below.</p>

+<p>As a convenience to new users who are unfamiliar with which files they should and should not distribute, the compiler will display an error message if one attempts to install certain "unsafe" files using the <link topic="filessection">[Files] section</link>. These files are listed below.</p>

 

 <p>(Note: It is possible to disable the error message by using a certain flag on the [Files] section entry, but this is NOT recommended.)</p>

+ 2 - 0
ISHelp/isx.xml
View File 

@@ -649,6 +649,8 @@ external '[email protected] stdcall';
 
 

 <p>Open the "CodeAutomation.iss" file in the "Examples" subdirectory in your Inno Setup directory for an example script using IDispatch based COM Automation objects.</p>

 

+<p>If you're using a .NET COM object and loading it fails since Inno Setup 5.5.9 try putting this line in your script before creating the COM object: <tt>LoadDLL(ExpandConstant('{sys}\mscoree.dll'), ErrorCode);</tt> and add a variable <tt>ErrorCode</tt> of type <tt>Integer</tt>.</p>

+

 </dd>

 

 <dt><b>IUnknown based COM</b></dt>

+ 2 - 2
whatsnew.htm
View File 

@@ -30,8 +30,8 @@ For conditions of distribution and use, see <a href="http://www.jrsoftware.org/f
 
 <p>A number of changes have been made to the administrative vs. non administrative install mode functionality:</p>

 <ul>

    <li>Added a separate <a href="http://www.jrsoftware.org/is6help/index.php?topic=admininstallmode">Non Administrative Install Mode</a> topic to the help file.</li>

-   <li>Added new &quot;auto&quot; constants which automatically map to their &quot;common&quot; form unless the installation is running in non administrative install mode, in which case they map to their &quot;user&quot; form. It is recommended you always use these "auto" constants when possible to avoid mistakes. The list of added &quot;auto&quot; constants is: <tt>{autoappdata}</tt>, <tt>{autocf}</tt>, <tt>{autocf32}</tt>, <tt>{autocf64}</tt>, <tt>{autodesktop}</tt>, <tt>{autodocs}</tt>, <tt>{autopf}</tt>, <tt>{autopf32}</tt>, <tt>{autopf64}</tt>, <tt>{autoprograms}</tt>, <tt>{autostartmenu}</tt><tt>, {autostartup}</tt>, and <tt>{autotemplates}</tt>.</li>

-   <li><b>Change in default behavior:</b> The &quot;common&quot; Shell Folder contants are no longer mapped to their "user" form if the installation is running in non administrative install mode. Instead they simply return the requested common directory. The list of available &quot;common&quot; Shell Folder constants is: <tt>{commonappdata}</tt>, <tt>{commondesktop}</tt>, <tt>{commondocs}</tt>, <tt>{commonprograms}</tt>, <tt>{commonstartmenu}</tt><tt>, {commonstartup}</tt>, and <tt>{commontemplates}</tt>.</li>

+   <li>Added new &quot;auto&quot; constants which automatically map to their &quot;common&quot; form unless the installation is running in non administrative install mode, in which case they map to their &quot;user&quot; form. It is recommended to update your scripts to use these "auto" constants as much as possible to avoid mistakes. The list of added &quot;auto&quot; constants is: <tt>{autoappdata}</tt>, <tt>{autocf}</tt>, <tt>{autocf32}</tt>, <tt>{autocf64}</tt>, <tt>{autodesktop}</tt>, <tt>{autodocs}</tt>, <tt>{autopf}</tt>, <tt>{autopf32}</tt>, <tt>{autopf64}</tt>, <tt>{autoprograms}</tt>, <tt>{autostartmenu}</tt><tt>, {autostartup}</tt>, and <tt>{autotemplates}</tt>.</li>

+   <li><b>Change in default behavior:</b> The &quot;common&quot; Shell Folder contants are no longer mapped to their "user" form if the installation is running in non administrative install mode. Instead they simply return the requested common directory. The list of affected &quot;common&quot; constants is: <tt>{commonappdata}</tt>, <tt>{commondesktop}</tt>, <tt>{commondocs}</tt>, <tt>{commonprograms}</tt>, <tt>{commonstartmenu}</tt><tt>, {commonstartup}</tt>, and <tt>{commontemplates}</tt>.</li>

    <li>The <tt>{commonfavorites}</tt> constant has been removed: this directory doesn't exist anymore in Windows.</li>

    <li>The <tt>{pf}</tt> and <tt>{cf}</tt> constants have been renamed to <tt>{commonpf}</tt> and <tt>{commoncf}</tt>. This includes <tt>{pf32}</tt> to <tt>{commonpf32}</tt>, etc. The old names are still supported, but it is recommended to update your scripts to the new names.</tt>

    <li>The <tt>{userpf}</tt> and <tt>{usercf}</tt> constants and the <tt>AlwaysUsePersonalGroup</tt> [Setup] section directive can now correctly trigger a <a href="http://www.jrsoftware.org/files/is5-whatsnew.htm#useduserareaswarnings">used user areas warning</a>.</li>