Hey Jared,
1. Our application is always started with one command line argument. In the constructor of my main wpf form, I set automaticUpdater.Arguments = commandLineArguments[0]; But after an update, my application is restarted with no command-line arguments.
You're right, this is a bug. It slipped by our tests, I apologize. We'll have this fixed in 2.6.14 (coming in about a week).
Thanks for spotting this.
2. Because the application is tightly integrated with our website, I want to ensure users can only run the most recent version of the application. I figure if I do a call to ForceCheckForUpdate() and a call to InstallNow() when an update is found, that will do what I need. Are there any problems with this approach I need to be aware of?
From a technical standpoint there shouldn't be any problems doing this.