-
Notifications
You must be signed in to change notification settings - Fork 14
/
ns-System.Deployment.Application.xml
15 lines (12 loc) · 2.71 KB
/
ns-System.Deployment.Application.xml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
<Namespace Name="System.Deployment.Application">
<Docs>
<summary>With the <see cref="N:System.Deployment.Application" /> namespace, you can program custom upgrade behavior into your ClickOnce application.</summary>
<remarks>
<format type="text/markdown"><![CDATA[
## Remarks
The key class in this namespace is <xref:System.Deployment.Application.ApplicationDeployment>. You can test whether your deployment has an available update by using either the <xref:System.Deployment.Application.ApplicationDeployment.CheckForUpdate%2A> or <xref:System.Deployment.Application.ApplicationDeployment.CheckForUpdateAsync%2A> methods; the latter method raises the <xref:System.Deployment.Application.ApplicationDeployment.CheckForUpdateCompleted> event when it has successfully completed. <xref:System.Deployment.Application.ApplicationDeployment.CheckForDetailedUpdate%2A> returns important information about the update, such as its version number and whether it is a required update for current users. If an update is available, you can install it by using <xref:System.Deployment.Application.ApplicationDeployment.Update%2A> or <xref:System.Deployment.Application.ApplicationDeployment.UpdateAsync%2A>; the latter method raises the <xref:System.Deployment.Application.ApplicationDeployment.UpdateCompleted> event after installation of the update is finished. For large updates, you can receive progress notifications through the <xref:System.Deployment.Application.ApplicationDeployment.CheckForUpdateProgressChanged> and <xref:System.Deployment.Application.ApplicationDeployment.UpdateProgressChanged> events, and use the information in <xref:System.ComponentModel.ProgressChangedEventArgs> to notify the user of the download status.
You can also use <xref:System.Deployment.Application.ApplicationDeployment> to download large files and assemblies on demand. These files must be marked as "optional" within the deployment's application manifest, so that they are not downloaded at installation. You can download the files at any point during the application's duration by using the <xref:System.Deployment.Application.ApplicationDeployment.DownloadFileGroup%2A> or <xref:System.Deployment.Application.ApplicationDeployment.DownloadFileGroupAsync%2A> methods. You can download assemblies before they are loaded into memory by supplying an event handler for the <xref:System.AppDomain.AssemblyResolve> event on the <xref:System.AppDomain> class. For more information, see [Walkthrough: Downloading Assemblies on Demand with the ClickOnce Deployment API Using the Designer](/visualstudio/deployment/walkthrough-downloading-assemblies-on-demand-with-the-clickonce-deployment-api-using-the-designer).
]]></format>
</remarks>
</Docs>
</Namespace>