deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-06-15 18:33:43 +00:00
Code Issues Actions 3 Packages Projects Releases Wiki Activity

Remove unnecessary indentation in code blocks

Browse Source
This commit is contained in:
Gary Moore
2021-12-02 16:12:02 -08:00
parent 5cf8e2f278
commit 3a9d3c466f
1 changed files with 53 additions and 53 deletions
Download Patch File Download Diff File Expand all files Collapse all files

106
windows/configuration/ue-v/uev-application-template-schema-reference.md
View File

@ -223,24 +223,24 @@ Author identifies the creator of the settings location template. Two optional ch
Processes contains at least one `<Process>` element, which in turn contains the following child elements: **Filename**, **Architecture**, **ProductName**, **FileDescription**, **ProductVersion**, and **FileVersion**. The Filename child element is mandatory and the others are optional. A fully populated element contains tags similar to this example: Processes contains at least one `<Process>` element, which in turn contains the following child elements: **Filename**, **Architecture**, **ProductName**, **FileDescription**, **ProductVersion**, and **FileVersion**. The Filename child element is mandatory and the others are optional. A fully populated element contains tags similar to this example:
```xml ```xml
<Process> <Process>
<Filename>MyApplication.exe</Filename> <Filename>MyApplication.exe</Filename>
<Architecture>Win64</Architecture> <Architecture>Win64</Architecture>
<ProductName> MyApplication </ProductName> <ProductName> MyApplication </ProductName>
<FileDescription>MyApplication.exe</FileDescription> <FileDescription>MyApplication.exe</FileDescription>
<ProductVersion> <ProductVersion>
<Major Minimum="2" Maximum="2" /> <Major Minimum="2" Maximum="2" />
<Minor Minimum="0" Maximum="0" /> <Minor Minimum="0" Maximum="0" />
<Build Minimum="0" Maximum="0" /> <Build Minimum="0" Maximum="0" />
<Patch Minimum="5" Maximum="5" /> <Patch Minimum="5" Maximum="5" />
</ProductVersion> </ProductVersion>
<FileVersion> <FileVersion>
<Major Minimum="2" Maximum="2" /> <Major Minimum="2" Maximum="2" />
<Minor Minimum="0" Maximum="0" /> <Minor Minimum="0" Maximum="0" />
<Build Minimum="0" Maximum="0" /> <Build Minimum="0" Maximum="0" />
<Patch Minimum="5" Maximum="5" /> <Patch Minimum="5" Maximum="5" />
</FileVersion> </FileVersion>
</Process> </Process>
``` ```
### Filename ### Filename
@ -299,13 +299,13 @@ If this element is absent, the settings location template ignores the process’
ProductName is an optional element used to identify a product for administrative purposes or reporting. ProductName differs from Filename in that there are no regular expression restrictions on its value. This allows for more easily understood descriptions of a process where the executable name may not be obvious. For example: ProductName is an optional element used to identify a product for administrative purposes or reporting. ProductName differs from Filename in that there are no regular expression restrictions on its value. This allows for more easily understood descriptions of a process where the executable name may not be obvious. For example:
```xml ```xml
<Process> <Process>
<Filename>MyApplication.exe</Filename> <Filename>MyApplication.exe</Filename>
<ProductName>My Application 6.x by Contoso.com</ProductName> <ProductName>My Application 6.x by Contoso.com</ProductName>
<ProductVersion> <ProductVersion>
<Major Minimum="6" Maximum="6" /> <Major Minimum="6" Maximum="6" />
</ProductVersion> </ProductVersion>
</Process> </Process>
``` ```
### FileDescription ### FileDescription
@ -353,10 +353,10 @@ The product and file version elements may be left unspecified. Doing so makes th
Product version: 1.0 specified in the UE-V template generator produces the following XML: Product version: 1.0 specified in the UE-V template generator produces the following XML:
```xml ```xml
<ProductVersion> <ProductVersion>
<Major Minimum="1" Maximum="1" /> <Major Minimum="1" Maximum="1" />
<Minor Minimum="0" Maximum="0" /> <Minor Minimum="0" Maximum="0" />
</ProductVersion> </ProductVersion>
``` ```
**Example 2:** **Example 2:**
@ -364,12 +364,12 @@ Product version: 1.0 specified in the UE-V template generator produces the follo
File version: 5.0.2.1000 specified in the UE-V template generator produces the following XML: File version: 5.0.2.1000 specified in the UE-V template generator produces the following XML:
```xml ```xml
<FileVersion> <FileVersion>
<Major Minimum="5" Maximum="5" /> <Major Minimum="5" Maximum="5" />
<Minor Minimum="0" Maximum="0" /> <Minor Minimum="0" Maximum="0" />
<Build Minimum="2" Maximum="2" /> <Build Minimum="2" Maximum="2" />
<Patch Minimum="1000" Maximum="1000" /> <Patch Minimum="1000" Maximum="1000" />
</FileVersion> </FileVersion>
``` ```
**Incorrect Example 1 – incomplete range:** **Incorrect Example 1 – incomplete range:**
@ -377,9 +377,9 @@ File version: 5.0.2.1000 specified in the UE-V template generator produces the f
Only the Minimum attribute is present. Maximum must be included in a range as well. Only the Minimum attribute is present. Maximum must be included in a range as well.
```xml ```xml
<ProductVersion> <ProductVersion>
<Major Minimum="2" /> <Major Minimum="2" />
</ProductVersion> </ProductVersion>
``` ```
**Incorrect Example 2 – Minor specified without Major element:** **Incorrect Example 2 – Minor specified without Major element:**
@ -387,9 +387,9 @@ Only the Minimum attribute is present. Maximum must be included in a range as we
Only the Minor element is present. Major must be included as well. Only the Minor element is present. Major must be included as well.
```xml ```xml
<ProductVersion> <ProductVersion>
<Minor Minimum="0" Maximum="0" /> <Minor Minimum="0" Maximum="0" />
</ProductVersion> </ProductVersion>
``` ```
### FileVersion ### FileVersion
@ -407,18 +407,18 @@ Including a FileVersion element for an application allows for more granular fine
The child elements and syntax rules for FileVersion are identical to those of ProductVersion. The child elements and syntax rules for FileVersion are identical to those of ProductVersion.
```xml ```xml
<Process> <Process>
<Filename>MSACCESS.EXE</Filename> <Filename>MSACCESS.EXE</Filename>
<Architecture>Win32</Architecture> <Architecture>Win32</Architecture>
<ProductVersion> <ProductVersion>
<Major Minimum="14" Maximum="14" /> <Major Minimum="14" Maximum="14" />
<Minor Minimum="0" Maximum="0" /> <Minor Minimum="0" Maximum="0" />
</ProductVersion> </ProductVersion>
<FileVersion> <FileVersion>
<Major Minimum="14" Maximum="14" /> <Major Minimum="14" Maximum="14" />
<Minor Minimum="0" Maximum="0" /> <Minor Minimum="0" Maximum="0" />
</FileVersion> </FileVersion>
</Process> </Process>
``` ```
### <a href="" id="application21"></a>Application Element ### <a href="" id="application21"></a>Application Element