You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/deployment/installchecks-element-bootstrapper.md
+8-8Lines changed: 8 additions & 8 deletions
Original file line number
Diff line number
Diff line change
@@ -18,12 +18,12 @@ manager: douge
18
18
ms.workload:
19
19
- "multiple"
20
20
---
21
-
# <InstallChecks>Element (Bootstrapper)
21
+
# <InstallChecks>element (bootstrapper)
22
22
The `InstallChecks` element supports starting a variety of tests against the local computer to make sure that all of the appropriate prerequisites for an application have been installed.
23
23
24
24
## Syntax
25
25
26
-
```
26
+
```xml
27
27
<InstallChecks>
28
28
<AssemblyCheck
29
29
Property
@@ -142,7 +142,7 @@ The `InstallChecks` element supports starting a variety of tests against the loc
142
142
## Example
143
143
The following code example demonstrates the `InstallChecks` element as it is used in the product file for the [!INCLUDE[dnprdnshort](../code-quality/includes/dnprdnshort_md.md)].
Copy file name to clipboardExpand all lines: docs/deployment/localizing-clickonce-applications.md
+11-11Lines changed: 11 additions & 11 deletions
Original file line number
Diff line number
Diff line change
@@ -24,7 +24,7 @@ manager: douge
24
24
ms.workload:
25
25
- "multiple"
26
26
---
27
-
# Localizing ClickOnce Applications
27
+
# Localize ClickOnce applications
28
28
Localization is the process of making your application appropriate for a specific culture. This process involves translating user interface (UI) text to a region-specific language, using correct date and currency formatting, adjusting the size of controls on a form, and mirroring controls from right to left if necessary.
29
29
30
30
Localizing your application results in the creation of one or more satellite assemblies. Each assembly contains UI strings, images, and other resources specific to a given culture. (Your application's main executable file contains the strings for the default culture for your application.)
@@ -42,30 +42,30 @@ Localization is the process of making your application appropriate for a specifi
42
42
43
43
This method is the default in [!INCLUDE[vsprvs](../code-quality/includes/vsprvs_md.md)]. To use this method in [!INCLUDE[vsprvs](../code-quality/includes/vsprvs_md.md)], you do not have to do any additional work.
44
44
45
-
To use this method with MageUI.exe, you must set the culture for your application to **neutral** in MageUI.exe. Next, you must manually include all of the satellite assemblies in your deployment. In MageUI.exe, you can add the satellite assemblies by using the **Populate** button on the **Files** tab of your application manifest.
45
+
To use this method with *MageUI.exe*, you must set the culture for your application to **neutral** in *MageUI.exe*. Next, you must manually include all of the satellite assemblies in your deployment. In *MageUI.exe*, you can add the satellite assemblies by using the **Populate** button on the **Files** tab of your application manifest.
46
46
47
47
The benefit of this approach is that it creates a single deployment and simplifies your localized deployment story. At run time, the appropriate satellite assembly will be used, depending on the default culture of the user's Windows operating system. A drawback of this approach is that it downloads all satellite assemblies whenever the application is installed or updated on a client computer. If your application has a large number of strings, or your customers have a slow network connection, this process can affect performance during application update.
48
48
49
49
> [!NOTE]
50
-
> This approach assumes that your application adjusts the height, width, and position of controls automatically to accommodate different text string sizes in different cultures. Windows Forms contains a variety of controls and technologies that enable you to design your form to make it easily localizable, including the <xref:System.Windows.Forms.FlowLayoutPanel> and <xref:System.Windows.Forms.TableLayoutPanel> controls as well as the <xref:System.Windows.Forms.Control.AutoSize%2A> property. Also see [How to: Support Localization on Windows Forms Using AutoSize and the TableLayoutPanel Control](http://msdn.microsoft.com/library/1zkt8b33\(v=vs.110\)).
50
+
> This approach assumes that your application adjusts the height, width, and position of controls automatically to accommodate different text string sizes in different cultures. Windows Forms contains a variety of controls and technologies that enable you to design your form to make it easily localizable, including the <xref:System.Windows.Forms.FlowLayoutPanel> and <xref:System.Windows.Forms.TableLayoutPanel> controls as well as the <xref:System.Windows.Forms.Control.AutoSize%2A> property. Also see [How to: Support localization on Windows forms using AutoSize and the TableLayoutPanel control](http://msdn.microsoft.com/library/1zkt8b33\(v=vs.110\)).
51
51
52
-
## Generate One Deployment for Each Culture
52
+
## Generate one deployment for each culture
53
53
In this deployment strategy, you generate multiple deployments. In each deployment, you include only the satellite assembly needed for a specific culture, and you mark the deployment as specific to that culture.
54
54
55
55
To use this method in [!INCLUDE[vsprvs](../code-quality/includes/vsprvs_md.md)], set the **Publish Language** property on the **Publish** tab to the desired region. [!INCLUDE[vsprvs](../code-quality/includes/vsprvs_md.md)] will automatically include the satellite assembly required for the region you select, and will exclude all other satellite assemblies from the deployment.
56
56
57
-
You can accomplish the same thing by using the MageUI.exe tool in the Microsoft [!INCLUDE[winsdklong](../deployment/includes/winsdklong_md.md)]. Use the **Populate** button on the **Files** tab of your application manifest to exclude all other satellite assemblies from the application directory, and then set the **Culture** field on the **Name** tab for your deployment manifest in MageUI.exe. These steps not only include the correct satellite assembly, but they also set the `language` attribute on the `assemblyIdentity` element in your deployment manifest to the corresponding culture.
57
+
You can accomplish the same thing by using the *MageUI.exe* tool in the Microsoft [!INCLUDE[winsdklong](../deployment/includes/winsdklong_md.md)]. Use the **Populate** button on the **Files** tab of your application manifest to exclude all other satellite assemblies from the application directory, and then set the **Culture** field on the **Name** tab for your deployment manifest in *MageUI.exe*. These steps not only include the correct satellite assembly, but they also set the `language` attribute on the `assemblyIdentity` element in your deployment manifest to the corresponding culture.
58
58
59
59
After publishing the application, you must repeat this step for each additional culture your application supports. You must make sure that you publish to a different Web server directory or file share directory every time, because each application manifest will reference a different satellite assembly, and each deployment manifest will have a different value for the `language`attribute.
60
60
61
-
## Downloading Satellite Assemblies on Demand
61
+
## Download satellite assemblies on demand
62
62
If you decide to include all satellite assemblies in a single deployment, you can improve performance by using on-demand downloading, which enables you to mark assemblies as optional. The marked assemblies will not be downloaded when the application is installed or updated. You can install the assemblies when you need them by calling the <xref:System.Deployment.Application.ApplicationDeployment.DownloadFileGroup%2A> method on the <xref:System.Deployment.Application.ApplicationDeployment> class.
63
63
64
64
Downloading satellite assemblies on demand differs slightly from downloading other types of assemblies on demand. For more information and code examples on how to enable this scenario using the [!INCLUDE[winsdkshort](../debugger/debug-interface-access/includes/winsdkshort_md.md)] tools for [!INCLUDE[ndptecclick](../deployment/includes/ndptecclick_md.md)], see [Walkthrough: Downloading Satellite Assemblies on Demand with the ClickOnce Deployment API](../deployment/walkthrough-downloading-satellite-assemblies-on-demand-with-the-clickonce-deployment-api.md).
65
65
66
66
You can also enable this scenario in [!INCLUDE[vsprvs](../code-quality/includes/vsprvs_md.md)]. Also see [Walkthrough: Downloading Satellite Assemblies on Demand with the ClickOnce Deployment API Using the Designer](http://msdn.microsoft.com/library/ms366788\(v=vs.110\)) or [Walkthrough: Downloading Satellite Assemblies on Demand with the ClickOnce Deployment API Using the Designer](http://msdn.microsoft.com/library/ms366788\(v=vs.120\)).
67
67
68
-
## Testing Localized ClickOnce Applications Before Deployment
68
+
## Testing localized ClickOnce applications before deployment
69
69
A satellite assembly will be used for a Windows Forms application only if the <xref:System.Threading.Thread.CurrentUICulture%2A> property for the main thread of the application is set to the satellite assembly's culture. Customers in local markets will probably already be running a localized version of Windows with their culture set to the appropriate default.
70
70
71
71
You have three options for testing localized deployments before you make your application available to customers:
@@ -74,7 +74,7 @@ Localization is the process of making your application appropriate for a specifi
74
74
75
75
- You can set the <xref:System.Threading.Thread.CurrentUICulture%2A> property programmatically in your application. (This property must be set before you call the <xref:System.Windows.Forms.Application.Run%2A> method.)
Copy file name to clipboardExpand all lines: docs/deployment/package-element-bootstrapper.md
+5-5Lines changed: 5 additions & 5 deletions
Original file line number
Diff line number
Diff line change
@@ -18,7 +18,7 @@ manager: douge
18
18
ms.workload:
19
19
- "multiple"
20
20
---
21
-
# <Package>Element (Bootstrapper)
21
+
# <Package>element (bootstrapper)
22
22
The `Package` element is the top-level XML element inside of a package file.
23
23
24
24
## Syntax
@@ -136,14 +136,14 @@ The `Package` element is the top-level XML element inside of a package file.
136
136
</Package>
137
137
```
138
138
139
-
## Elements and Attributes
139
+
## Elements and attributes
140
140
The `Package` element is required. It has the following attributes.
141
141
142
142
|Attribute|Description|
143
143
|---------------|-----------------|
144
144
|`Culture`|Required. Defines the culture for this package, which determines the language to be used. This attribute is a key into the `Strings` element, which lists culture-specific strings for product names and error messages during the installation.|
145
145
|`Name`|Required. The name of the package displayed to the developer within a tool such as [!INCLUDE[vsprvs](../code-quality/includes/vsprvs_md.md)]. This attribute is a key into the `Strings` element, which should contain a `String` element with the `Name` and `Culture` properties set to match the `Name` and `Culture` properties of `Package`.|
146
-
|`LicenseAgreement`|Optional. Specifies the name of the file in the distribution package which contains the End-User License Agreement (EULA). This file can be either plain text (.txt) or Rich Text Format. (.rtf)|
146
+
|`LicenseAgreement`|Optional. Specifies the name of the file in the distribution package which contains the End-User License Agreement (EULA). This file can be either plain text (*.txt*) or Rich Text Format. (*.rtf*)|
147
147
148
148
## Example
149
149
The following code example shows a complete package file for redistributing the [!INCLUDE[dnprdnlong](../code-quality/includes/dnprdnlong_md.md)].
@@ -183,5 +183,5 @@ The `Package` element is the top-level XML element inside of a package file.
183
183
</Package>
184
184
```
185
185
186
-
## See Also
187
-
[Product and Package Schema Reference](../deployment/product-and-package-schema-reference.md)
186
+
## See also
187
+
[Product and package schema reference](../deployment/product-and-package-schema-reference.md)
Copy file name to clipboardExpand all lines: docs/deployment/packagefiles-element-bootstrapper.md
+8-8Lines changed: 8 additions & 8 deletions
Original file line number
Diff line number
Diff line change
@@ -18,12 +18,12 @@ manager: douge
18
18
ms.workload:
19
19
- "multiple"
20
20
---
21
-
# <PackageFiles>Element (Bootstrapper)
21
+
# <PackageFiles>element (bootstrapper)
22
22
The `PackageFiles` element contains `PackageFile` elements, which define the installation packages executed as a result of the `Command` element.
23
23
24
24
## Syntax
25
25
26
-
```
26
+
```xml
27
27
<PackageFiles
28
28
CopyAllPackageFiles
29
29
>
@@ -37,7 +37,7 @@ The `PackageFiles` element contains `PackageFile` elements, which define the ins
37
37
</PackageFiles>
38
38
```
39
39
40
-
## Elements and Attributes
40
+
## Elements and attributes
41
41
The `PackageFiles` element has the following attribute.
42
42
43
43
|Attribute|Description|
@@ -60,7 +60,7 @@ The `PackageFiles` element contains `PackageFile` elements, which define the ins
60
60
## Example
61
61
The following code example defines packages for the [!INCLUDE[dnprdnshort](../code-quality/includes/dnprdnshort_md.md)] redistributable package and its dependencies, such as the Windows Installer.
Copy file name to clipboardExpand all lines: docs/deployment/product-and-package-schema-reference.md
+5-5Lines changed: 5 additions & 5 deletions
Original file line number
Diff line number
Diff line change
@@ -28,7 +28,7 @@ manager: douge
28
28
ms.workload:
29
29
- "multiple"
30
30
---
31
-
# Product and Package Schema Reference
31
+
# Product and package schema reference
32
32
A *product file* is an XML manifest that describes all of the external dependencies required by a [!INCLUDE[ndptecclick](../deployment/includes/ndptecclick_md.md)] application. Examples of external dependencies include the [!INCLUDE[dnprdnshort](../code-quality/includes/dnprdnshort_md.md)] and the Microsoft Data Access Components (MDAC). A package file is similar to a product file but is used to install the culture-dependent components of a dependency, such as localized assemblies, license agreements, and documentation.
33
33
34
34
The product and packages file consists of either a top-level `Product` or `Package` element, each of which contains the following elements.
@@ -44,7 +44,7 @@ A *product file* is an XML manifest that describes all of the external dependenc
44
44
|[\<Strings> Element](../deployment/strings-element-bootstrapper.md)|Required element. Stores localized versions of the product name and error strings.|None|
45
45
46
46
## Remarks
47
-
The package schema is consumed by Setup.exe, a stub program generated by the MS Build bootstrapping task that contains little hard-coded logic of its own. The schema drives every aspect of the installation process.
47
+
The package schema is consumed by *Setup.exe*, a stub program generated by the MS Build bootstrapping task that contains little hard-coded logic of its own. The schema drives every aspect of the installation process.
48
48
49
49
`InstallChecks` the tests that setup.exe should perform for the existence of a given package. `PackageFiles` lists all of the packages that the setup process might have to install, should a given test fail. Each Command entry under Commands executes one of the tests described by `InstallChecks`, and specifies which `PackageFile` to run should the test fail. You can use the `Strings` element to localize product names and error messages, so that you can use one single installation binary to install your application for any number of languages.
50
50
@@ -153,6 +153,6 @@ A *product file* is an XML manifest that describes all of the external dependenc
0 commit comments