Setting up the AppUpdater Component to work with Windows Server 2003
The AppUpdater Component is sexy. Check out the article on it to get a good start on getting it working. It's a little goofy at first, but works fantastically and is very flexible to fit your needs. For a recent project I did, I set it up to call a WebService to check for updates checking who the user is (a custom forms authentication) and checking a versions database to see what the latest version for that user is. This allows you to do some neat things like have beta versions that only some people get.
One of the big hurdles I've mentioned before (and have seen other people have problems with) is getting it to work with Windows Server 2003. As we all know it's very locked down from the get go which is great, but sometimes makes it hard to get things working. The following steps will help you setup what you need in IIS 6.0 to get the AppUpdater component to work with a Win2K3 Server:
- Open up IIS
- Click on the Web Service Extensions node
- Click on WebDAV
- Click the Allow button
- Under Web Sites, navigate to the folder that will hold all the different versions of your applications, in my case, a folder called “versions“.
- Right mouse click on the “versions” folder and click Properties
- Click the Create button to make it an IIS Application
- Click the Configuration button
- Select .config in the application extensions list
- Click the Remove button and hit OK
- Check the “Directory browsing” checkbox and hit OK
Hope this helps! :) Again, these instructions are only for the changes necessary for the versions to be housed on a Windows Server 2003 box. For the rest of the “How-To” on getting the AppUpdater Component to work, check out the link above.