Arguments not being passed after updateSolved

Hello-I'm evaluating wyBuild and wyUpdate for a new .NET WPF application my company has built. Generally things seem to be working how I want them to, but I have two questions: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.

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?

Thanks!Jared

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.

Thanks for the quick response, I'll switch to the new version when it is released. I can work around it for now.

Hello again - just checking the status on this...Can we expect v2.6.14 soon? I'd like to have a full working version soon to show my boss so we can make the purchase.

Hey Jared,

We're shooting for a release on Tuesday of next week (5/24/2011). If you don't want to wait for that you can checkout the latest AutomaticUpdater source code from the SVN repository where we have this bug fixed:

svn checkout http://automatic-updater.googlecode.com/svn/trunk/ automatic-updater-read-only

Jared,

wyBuild 2.6.14 is now out. Included is the latest AutomaticUpdater that has this bug fixed. Thanks for spotting it.

Thanks Wyatt. Our trial expired and this app needs to go into production sometime in the next few days, so we went ahead and purchased now that this bug is fixed, hopefully we can get it up and running end to end today