ynkmr/Sourcetrail
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

src: correct spelling errors (#1162)

Browse Source
This commit is contained in:
Josh Soref
2021-03-14 07:47:26 +01:00
committed by GitHub
parent 5932e9f1e8
commit 3a75ef0df4
97 changed files with 261 additions and 261 deletions
Download Patch File Download Diff File Expand all files Collapse all files
deployment/windows/wixSetup/CustomActions/Microsoft.Deployment.WindowsInstaller.xml
+17 -17
View File
@@ -776,7 +776,7 @@
<summary>Detects the range of versions including the value in VersionMin.</summary>
</member>
<member name="F:Microsoft.Deployment.WindowsInstaller.UpgradeAttributes.VersionMaxInclusive">
<summary>Dectects the range of versions including the value in VersionMax.</summary>
<summary>Detects the range of versions including the value in VersionMax.</summary>
</member>
<member name="F:Microsoft.Deployment.WindowsInstaller.UpgradeAttributes.LanguagesExclusive">
<summary>Detects all languages, excluding the languages listed in the Language column.</summary>
@@ -1115,7 +1115,7 @@
<summary>
Gets the set of registered qualifiers for the component.
</summary>
<returns>Enumeration of the qulifiers for the component.</returns>
<returns>Enumeration of the qualifiers for the component.</returns>
<exception cref="T:Microsoft.Deployment.WindowsInstaller.InstallerException">The installer configuration data is corrupt</exception>
<remarks><p>
Because qualifiers are not ordered, any new qualifier has an arbitrary index,
@@ -1438,7 +1438,7 @@
</member>
<member name="M:Microsoft.Deployment.WindowsInstaller.CustomActionProxy.MethodHasCustomActionSignature(System.Reflection.MethodInfo)">
<summary>
Checks if a method has the right return and paramater types
Checks if a method has the right return and parameter types
for a custom action, and that it is marked by a CustomActionAttribute.
</summary>
<param name="method">Method to be checked.</param>
@@ -1508,7 +1508,7 @@
needed, as leaving lots of unused handles open can degrade performance.
</p><p>
The database is opened in <see cref="F:Microsoft.Deployment.WindowsInstaller.DatabaseOpenMode.CreateDirect" /> mode, and will be
automatically commited when it is closed.
automatically committed when it is closed.
</p><p>
Win32 MSI API:
<a href="http://msdn.microsoft.com/library/en-us/msi/setup/msiopendatabase.asp">MsiOpenDatabase</a>
@@ -1532,7 +1532,7 @@
longer needed, as leaving lots of unused handles open can degrade performance.
</p><p>
A database opened in <see cref="F:Microsoft.Deployment.WindowsInstaller.DatabaseOpenMode.CreateDirect" /> or
<see cref="F:Microsoft.Deployment.WindowsInstaller.DatabaseOpenMode.Direct" /> mode will be automatically commited when it is
<see cref="F:Microsoft.Deployment.WindowsInstaller.DatabaseOpenMode.Direct" /> mode will be automatically committed when it is
closed. However a database opened in <see cref="F:Microsoft.Deployment.WindowsInstaller.DatabaseOpenMode.Create" /> or
<see cref="F:Microsoft.Deployment.WindowsInstaller.DatabaseOpenMode.Transact" /> mode must have the <see cref="M:Microsoft.Deployment.WindowsInstaller.Database.Commit" /> method
called before it is closed, otherwise no changes will be persisted.
@@ -2779,7 +2779,7 @@
<summary>Patches that are superseded by other patches.</summary>
</member>
<member name="F:Microsoft.Deployment.WindowsInstaller.PatchStates.Obsoleted">
<summary>Patches that are obsolesced by other patches.</summary>
<summary>Patches that are obsoleted by other patches.</summary>
</member>
<member name="F:Microsoft.Deployment.WindowsInstaller.PatchStates.Registered">
<summary>Patches that are registered to a product but not applied.</summary>
@@ -3340,7 +3340,7 @@
</member>
<member name="P:Microsoft.Deployment.WindowsInstaller.MergeException.Message">
<summary>
Gets a message that describes the merge conflits.
Gets a message that describes the merge conflicts.
</summary>
</member>
<member name="M:Microsoft.Deployment.WindowsInstaller.MergeException.GetObjectData(System.Runtime.Serialization.SerializationInfo,System.Runtime.Serialization.StreamingContext)">
@@ -3471,7 +3471,7 @@
</summary>
<param name="logModes">One or more mode flags specifying the type of messages to log</param>
<param name="logFile">Full path to the log file. A null path disables logging,
in which case the logModes paraneter is ignored.</param>
in which case the logModes parameter is ignored.</param>
<exception cref="T:System.ArgumentException">an invalid log mode was specified</exception>
<remarks>This method takes effect on any new installation processes. Calling this
method from within a custom action will not start logging for that installation.</remarks>
@@ -3483,7 +3483,7 @@
</summary>
<param name="logModes">One or more mode flags specifying the type of messages to log</param>
<param name="logFile">Full path to the log file. A null path disables logging,
in which case the logModes paraneter is ignored.</param>
in which case the logModes parameter is ignored.</param>
<param name="append">If true, the log lines will be appended to any existing file content.
If false, the log file will be truncated if it exists. The default is false.</param>
<param name="flushEveryLine">If true, the log will be flushed after every line.
@@ -3846,7 +3846,7 @@
<summary>
Determines which patches apply to a specified product and in what sequence. If
the product is installed, this method accounts for patches that have already been applied to
the product and accounts for obsolete and superceded patches.
the product and accounts for obsolete and superseded patches.
</summary>
<param name="product">The product that is the target for the set of patches. This may be
either a ProductCode (GUID) of a product that is currently installed, or the path to a an
@@ -4267,7 +4267,7 @@
<a href="http://msdn.microsoft.com/library/en-us/msi/setup/msigetfeatureinfo.asp">MsiGetFeatureInfo</a>,
<a href="http://msdn.microsoft.com/library/en-us/msi/setup/msisetfeatureattributes.asp">MsiSetFeatureAttributes</a>
</p><p>
Since the lpAttributes paramter of
Since the lpAttributes parameter of
<a href="http://msdn.microsoft.com/library/en-us/msi/setup/msigetfeatureinfo.asp">MsiGetFeatureInfo</a>
does not contain an equivalent flag for <see cref="F:Microsoft.Deployment.WindowsInstaller.FeatureAttributes.UIDisallowAbsent"/>, this flag will
not be retrieved.
@@ -4453,7 +4453,7 @@
</member>
<member name="P:Microsoft.Deployment.WindowsInstaller.InstallerHandle.Sync">
<summary>
Gets an object that can be used internally for safe syncronization.
Gets an object that can be used internally for safe synchronization.
</summary>
</member>
<member name="M:Microsoft.Deployment.WindowsInstaller.InstallerHandle.Dispose(System.Boolean)">
@@ -4824,7 +4824,7 @@
</member>
<member name="P:Microsoft.Deployment.WindowsInstaller.PatchInstallation.IsObsoleted">
<summary>
Gets a value indicating whether this patch is marked as obsolte.
Gets a value indicating whether this patch is marked as obsolete.
</summary>
</member>
<member name="P:Microsoft.Deployment.WindowsInstaller.PatchInstallation.IsSuperseded">
@@ -5328,7 +5328,7 @@
</summary>
<remarks><p>
Win32 MSI API:
<a href="http://msdn.microsoft.com/library/en-us/msi/setup/msirecordcleardata.asp">MsiRecordClearData</a>
<a href="http://msdn.microsoft.com/library/en-us/msi/setup/msirecordclearedata.asp">MsiRecordClearData</a>
</p></remarks>
</member>
<member name="M:Microsoft.Deployment.WindowsInstaller.Record.IsNull(System.Int32)">
@@ -6085,7 +6085,7 @@
<item><description>The Select and Installed states for all features in the Feature table</description></item>
<item><description>The Action state of each component in the Component table, based on the new level</description></item>
</list>
If 0 or a negative number is passed in the ilnstallLevel parameter,
If 0 or a negative number is passed in the installLevel parameter,
the current installation level does not change, but all features are still
updated based on the current installation level.
</p><p>
@@ -6200,7 +6200,7 @@
</member>
<member name="M:Microsoft.Deployment.WindowsInstaller.Session.ValidateSessionAccess">
<summary>
Throws an exception if the custom action is not able to access immedate session details.
Throws an exception if the custom action is not able to access immediate session details.
</summary>
</member>
<member name="T:Microsoft.Deployment.WindowsInstaller.ShortcutTarget">
@@ -6605,7 +6605,7 @@
<member name="P:Microsoft.Deployment.WindowsInstaller.SummaryInfo.Template">
<summary>Gets or sets the Template summary information property.</summary>
<remarks><p>
The Template summary information propery indicates the platform and language versions supported by the database.
The Template summary information property indicates the platform and language versions supported by the database.
</p><p>
The syntax of the Template Summary property information is:
[platform property][,platform property][,...];[language id][,language id][,...]
deployment/windows/wixSetup/build.sh
+1 -1
View File
@@ -23,7 +23,7 @@ echo "installer version is $VERSION_STRING"
PRODUCT_GUID=$("uuidgen")
if [ -z "$PRODUCT_GUID" ]; then
echo "Unable to generate GUID. Make sure to run this script from the Visual Studio command propmt. Aborting now."
echo "Unable to generate GUID. Make sure to run this script from the Visual Studio command prompt. Aborting now."
exit 1
else
echo "$WIN_ARCH product guid is $PRODUCT_GUID"
deployment/windows/wixSetup/wixReadme.txt
+7 -7
View File
@@ -10,7 +10,7 @@ Build the installer
-I used stable version 3.10.3 for development
-make sure the WiX directory is in you OS path variable ('..\WiX Toolset v3.10\bin')
-Sourcetrail has to be built with the 'deploy' flag
-installer would still build if the deploy flag wasnt set, but the Sourcetrail wont run properly on a user machine
-installer would still build if the deploy flag wasn't set, but the Sourcetrail wont run properly on a user machine
-Execute build.bat
-This will build sourcetrail.msi file, all needed custom action dlls and the setup.exe file
@@ -41,10 +41,10 @@ Add new components (e.g. files) to the installation
-...
Generel
General
-to add a file create a <Component> element
-mind the <Directory> tags, they define where the component will be installed. Add new directories if necessary
-Id: the directory will be refered to within the wix project using this id
-Id: the directory will be referred to within the wix project using this id
-Name: the name of the folder that will be created on the user machine
-Id: is used to refer to the component within the wix project
-Guid: GUIDs are unique id's used by windows to identify and refer to installed files, applications and so on. You need to create a new GUID for every new component
@@ -55,7 +55,7 @@ Generel
-Name: the name that the file will have on the user machine, may be different from the file name on the source machine
-Source: the path and name to the file on the source machine, relative to the current .wxs file
-KeyPath: depends on where you want to install the file, see below in 'Add new file to...'
-usually there is one component for each single file. Multiple files can be added to a component, this might make sense if the files are considered 100% unseperable. The recommended way however is one file per component
-usually there is one component for each single file. Multiple files can be added to a component, this might make sense if the files are considered 100% inseparable. The recommended way however is one file per component
Add new file to the installation directory (installDir.wxs)
@@ -76,7 +76,7 @@ Not quite done yet! (sourcetrail.wxs)
-components need to be added to a feature (a feature is part of a software, consisting of components, that may or may not be installed during setup)
-right now we only have the Complete/Program feature, so no part of sourcetrail is optional right now
-to add a component to a feature use the <ComponentRef> tag
-Id: id of the component you want to refere to
-Id: id of the component you want to reference
------------------
@@ -89,7 +89,7 @@ Version Number
-candle.exe -dprojectVersion="0.7.0" ...
-replace 0.7.0 with the desired version number
Minor upgrage (sourcetrail.wxs)
Minor upgrade (sourcetrail.wxs)
-for when only a few files are to be updated
-update the version number in build.bat script
-do NOT change the product GUID
@@ -101,4 +101,4 @@ Major upgrade (sourcetrail.wxs)
-update the version number in build.bat script
-DO change the product GUID
-insert the same GUID into the uninstall_wix.bat script
-package GUID changes too, but thats again done automatically
-package GUID changes too, but that's again done automatically