. NET client application:. NET application update component (1)

Program | Client Author: Jamie Cool

Microsoft Corporation

3/4/02

Translation: Li Jia
Dongfong Beijing.
2004-6-1


Smart upgrades, Automatic Updates, this is a problem we often encounter and need to pay attention to when we used to develop Windows applications. This issue has been a pain in the neck until the. NET application update component is not present (unless you are not going to upgrade:). Who doesn't want to develop an application that has Automatic Updates like Windows XP itself or Microsoft Money? Use. NET application update component will make this all the easier. In the DevDay2004 of Microsoft, Cao has demonstrated the smart client issuevision a very important bright spot is the intelligent upgrade, automatic Update. The use of this is. NET application update component. This group of articles will use an example to discuss a generation that can automatically update itself. NET client application method.

I recently received a mail from the Microsoft IT team notifying me this they had detected several applications on my Deskt OP computer that did not have the latest patches installed and instructed me to install the latest. I'll be the the "I" I admit that I don ' t update the applications I run as much as I should; Either on my home machine or in my work machines. It usually takes a problem like a broken feature in a application or a email (or sometimes several) from the IT Departme NT, to get me to install updates. Unfortunately I ' m more of the "rule than" exception when it comes to users updating their.

I recently received an email from the Microsoft IT team reminding me that they had detected some applications on my desktop computer that did not have the latest patches installed, and recommended that I install these latest patches. I'll be the first to admit that I'm not running application updates manually although I can do that. Whether it's on my home computer or on my work machine. Let me install updates as often as a problem with an interrupt feature in an application or a (or sometimes multiple) message from an IT department. Unfortunately, I am more in compliance with the rules than those who have to update their applications.



This requirement of needing a user or admin to manually install an update are why rolling out client updates has Traditiona Lly been such a huge problem and expense. One solution is to move the responsibility of updating the application from the user to the application itself. Instead of the user obtaining and installing a software update, the client application itself is responsible for Downloadi Ng and installing updates from a-known server. The only user interaction necessary are whether or not they want to install the new updates now or later. You can-this type is approach to updating applications in action today, with the products like Windows XP and Microsoft Mon ey.

The need for users or administrators to manually install updates is the reason for polling for client updates, which has been a big problem and costly. One solution is to transfer the responsibility for the update from the user to the application itself. Instead of the user acquiring and installing a software update, the client application itself is responsible for downloading and installing updates from a known server. The only thing users need to intervene is to decide whether they want to install new updates now or later. You can now see actual products such as Windows XP and Microsoft Money for methods that update applications like this.



In this article we'll talk about a approach to building. NET client applications then are able to automatically update themselves.

In this article we will discuss a generation that automatically updates itself. NET client application method.



(To be continued)