hespect.softwaresHello, I have searched the forums and stack overflow, but just can't get this figured out. I have a winforms app in production. We have done about 10 version updates over the last year (and I have another client with a different winforms app and we have done 6-8 updates for them too) all with no problem.
But somewhere along the line, the auto-updater in one (call it "PD" for short) just stopped working. running wyUpdate works perfectly. AU never seems to recognize an update is present. I do see that a ".AUTOUPDATE" file is being created in the Roaming folder when the app opens (days between check = 0). But I can't find anything in any logs or event viewer etc.
I have a complex but hopefully not atypical set of environments:"production" branch"efix" branch"dev" branch"alternate dev" branch
In WyBuild I maintain two projects: "PD-Production" and "PD-Test". They have a different root location for versions folders, and different server locations etc.
In a normal development sprint I will make my changes in "dev", then for user acceptance testing, create a wyBuild update version in the PD-Test project. I will use the files from dev branch "bin\release" folder to move to the wyBuild version folder and then point the wyBuild update to that folder.
I build the wyUpdate and client.wyc, copy them to the dev visual studio project folder and the wyc file to the PS-Test version folder.
Then, in wyBuild I build the update, and upload it to the test server. My clients test and approve and now we need a production update. So, merge changes from dev branch to production branch, build, test, then open the wyBuild PD-Production project, add a new version update, create a version folder, copy production branch bin/release files, build the wyUpdate and client.wyc, copy them as above, build the update, and push the the production server.
And version 1.1.4 production in the wild doesn't seem to notice. When I do a clean install of 1.1.4 production on a test box, like I said above an AUTOUPDATE file is created. but AU never does anything in my app.
please help!-David
It's very unclear what exact is happening and what you exactly you expect to happen.
For starters, just use wyUpdate directly. Don't use the AutomaticUpdater. We're dropping support for it in the next version because customers more often use it incorrectly than correctly.
hespect.softwaresOK, maybe I can simplify my questions then, and get a short term fix; and then modify the app as you say.
What would make autoupdater download .autoupdate files and then not show the UI? Is it something to do with the project GUID?
I have multiple branches of my app (dev, test, production) and I have a wyBuid project and an update server for each. I copy client.wyc files from folder to folder to control what code being run is connecting to which update server. Is it possible I got the wrong client.wyc file pushed out to my production installs and that is why they can no longer see their updates with autoUpdater?
thanks!
>> "What would make autoupdater download .autoupdate files and then not show the UI? Is it something to do with the project GUID? "
Misuse of the AutomaticUpdater API.
Short answer: don't use the AutomaticUpdater at all. We've dropped support for it in the next version. Just use wyUpdate directly -- it's faster and harder to mess up (because we handle the details).
hespect.softwaresI know, I get that, but I really need to rescue my currently-installed production units. Modifying my app for the next release is totally on the plan now, thank you, but I really need to straighten out whatever I did to break my production updates.
I'm not using the AU API, all I did was drop the AU control on my main form, set the update type and days between settings. And it worked great for a dozen releases. Did I push out a bad client.wyc file with the last update that worked? if I build update files with the gui that matches that client.wyc will it go back to working?
thank you!
