I have an application built, with (VERSION 1.0.0.0).the update 1.0.0.1 is built and uploaded.But the updater does not see it.If I can into the folder where the app and WyUpdate.exe file is and I click on it, I get the message"the version of xxx installed on this computer is 1.0.0.0. The latest version is 1.0.0.1. with the update button.
So is the auto updater not running when I start the up.For the record I do get the app saying update, and checking for update. It just cant find it.
So is the auto updater not running when I start the up.
The AutomaticUpdater does not check on every startup of your app. Why? Because that would hammer your servers unnecessarily. Adjust how often the AutomaticUpdater checks for updates (specifically: DaysBetweenChecks, WaitBeforeCheckSecs).
Thanks for the reply, but I don't think that is the issue.Since I have automaticUpdater.ForceCheckForUpdate(); in my loadsettings() function.in my WyUpdatelocation is just wyUpdate.exe and the switches in the command line are /quickcheck /noerr /skipinfo
the command line are /quickcheck /noerr /skipinfo
Don't do that. Those are only for wyUpdate in standalone mode. Not for the AutomaticUpdater.
Also, make sure you're using the latest version of the AutomaticUpdater.
Also, make sure you actually read the return Boolean for ForceCheckForUpdate() If it returns false then that means it will not check immediately. Actually -- better yet, don't use ForceCheckForUpdate() at all. Just let the AutomaticUpdater handle the checking for update (that is what it's designed to do, after all).
But it needs to check whenever a user starts the application, that is why I used ForceCheckForUpdate().
Just set DaysBetweenChecks to 0 and remove your call to ForceCheckForUpdate.
I honestly don't think that is the problem ,because it does say "updating" but it does not find a file to update unless I run it manually. And I have 500 users waiting for an update.
Sorry, it says "checking for updates" But it does not find it.
It sounds like you have another copy of wyUpdate (or the client.wyc file) that has already been updated.
how is that possible?
Many, many different ways.
Look in your code and the properties. Are you using the "wyUpdateCommandline"? In most cases: don't.
Look where your executable is sitting. Sitting next to it is wyUpdate.exe and client.wyc. When you run wyUpdate.exe next to where your executable is sitting, does it say you're already up-to-date?
Try replacing the ":wyUpdateLocation" property to an absolute path to where you know wyUpdate.exe is sitting.
vaughanheat is empty.in the wyupdatelocation is only wyUpdate.exe
I can use absolute path, because the app may go into the "c:\program files" or "C::\ program files (x86) " folder.
Lets try that again.
wyUpdateCommandlineis empty.in the wyupdatelocation is only wyUpdate.exe
I can't use absolute path, because the app may go into the "c:\program files" or "C::\ program files (x86) " folder.
For testing, I mean. Not permanently.
that Is not a good answer.How do I set the relative path of the update?
The AutomaticUpdater and wyUpdate work fine here (and with thousands upon thousands of other customers). Maybe you've encountered a bug. Or, more likely you've done something wrong.
I'm trying to help you debug this problem to see whether it's our bug or your bug.
So what should you do? This:
Look where your executable is sitting. Sitting next to it is wyUpdate.exe and client.wyc. When you run wyUpdate.exe next to where your executable is sitting, does it say you're already up-to-date?
Try replacing the ":wyUpdateLocation" property to an absolute path to where you know wyUpdate.exe is sitting.
Do I mean permanently hardcode the path to wyUpdate? Of course not. But you should do it when you're trying to solve this problem.
You are still not answering my question.How do I set the updater to run automatically in the folder where the application I am trying to update resides?
How do I set the updater to run automatically in the folder where the application I am trying to update resides?
I'm not sure what you're asking.
He're's what I want you to do. Go to wherever your application *.exe is sitting. Do you see wyUpdate.exe? If so, double click it. Does it say there are updates available? If not, then there's your problem.
Number 2: hardcode the location of wyUpdate.exe in the "wyUpdateLocation" property. You're not doing this permanently. Just do this so you can debug the problem. Tell me the result.
if it is hard coded to the location, it works fine.
That tells me that you have multiple wyUpdate.exes(and client.wycs) sitting on your computer. The one sitting next to your executable (in the Bin/Debug or Bin/Release folder) has already been updated (hence the AutomaticUpdater saying it has already been updated).
What do you do? replace the wyUpdate.exe/client.wyc file that have already been updated (sitting next to your app .exe file) with the wyUpdate.exe and client.wyc that actually match your app's version number (double click the client.wyc file).
That makes no sense. Of course there are multiple files on my computer, but only 1 in the folder that the app is running in
