The Updater Application Block… various additions…

One of the nice things about the Updater Application Block is that it was written to be quite extensible… I saw a post today where SamSantiago mentioned he had created a custom class to delete all those old versions on your machine whenever you do an update…. very cool, I’ll be trying that out right away…

Personally, I’ve updated the updater in a few different ways, but the most recent changes have been the most reusable, in my opinon;

  • I fixed the code so that it no longer requires users to have admin rights…
  • I added a ‘mandatory’ flag to the updates (and updated the manifestutility in a few different ways), so that for some updates the client app would know not to ask the user if they want to upgrade… great for occasionally forcing everyone up to the same build…
  • and I modified the manifest retrieval code so that it can call an ASP or ASP.NET page, which in turn allowed me to create a manifest.aspx page that returns different manifests based on the user’s credentials (so I can have a ‘beta’ group who are given one version, and everyone else gets the last major release…)

I’ve got to work out a way to get these bits of code online…. it isn’t hard, but it takes time that I haven’t planned in yet đŸ™‚

Author: Duncan Mackenzie

I'm the Developer Lead for the Channel 9 team, formerly worked on MSDN as a developer, content strategist and author.

3 thoughts on “The Updater Application Block… various additions…”

  1. Hi Duncan

    What do I need to do to get rid of admin rights being required? Admin rights is a requirement to install publisher policy into the GAC – is there any way to get around this? What did you do to get rid of the admin rights requirement?


  2. I was actually looking to do the same thing (i.e. different downloads for different users) would you be willing to share the code for how you did this ?

Leave a Reply