CODEWITHSUNDEEP
asp.net
corymathews
corymathews

Reputation: 12619

Managing Software Updates

I am looking into different ways to handle updating an ASP.NET application across many different clients, and looking for suggestions from your previous experience.

Thanks

Edit: after thinking more about this overnight, I would have to agree that auto updates may not be the best. However maybe something more along the lines of how wordpress does it. Wordpress will display saying that there is an update available then clicking will auto update the system.

Upvotes: 0

Views: 172

Answers (2)

Justin Niessner
Justin Niessner

Reputation: 245399

Having a hard time figuring out if you're actually talking about a web application or a desktop application. If you're trying to do something similar to Chrome...I'm guessing a desktop application. If that's the case...check out ClickOnce deployment.

It offers the first three bullet points you mention:

  1. Every time a person runs the app, it will check for updates.
  2. If updates are found, the user can choose to install them or not (better user experience than forcing the update on the user).
  3. The application always checks the URL that the app was installed from...which in your case would be your servers.

Upvotes: 1

kemiller2002
kemiller2002

Reputation: 115460

I would absolutely not have your application auto update on clients (assuming you mean clients are entities external to your organization) servers. We would immediately stop using a product that would "phone home" and update itself. Clients need to be able to choose when and how an update on their server occurs.

If you are going to do this, the easiest way would be to set up URI the systems could ping once a day etc. and see if there are updates available. If so the application would pull it down from the host system and update itself. If you do it using SSL then the certificate would verify the URI being hit is your company.

Upvotes: 2

Related Questions