- No crashes after 10 seconds
- No infinite loops
- No exception traces
- I won the lottery
I may be lying about one of those items, it's up to you to figure out which one.
Some caveats for other people trying to update:
- The link in the Updaters sticky thread to "the last good WAU build" at codeplex.com points to .738, which is the one which mysteriously start asploding the other day.
- The "outdated" WAU wiki page referred to at codeplex has two links. The zip file is .718, and the install-via-IE link is to the updated and working .746.
Finally, two questions, just out of curiosity (feel free to ignore them). I'm a programmer, and while I don't use .NET myself, I've plenty of other experience with similar technologies. What on earth happened to make .738 self-destruct even though nothing on the user's end had changed? And what happened to .739-ish to cause the corrupted-zip-infinite-loop thing?
It is no longer maintained. I stopped supporting it from a development standpoint in November (That is posted in this thread).
If you're referring to the post that stickied at the top of each page, then it's not clear that WAU is no longer maintained. The only restriction listed is "the only supported version is the one linked to from the main page", but nothing about the project being in maintenance mode.
If it's somewhere else in the thread, then I apologize for not reading all 16 pages of posts from last September. :-)
Ignore is working perfectly fine. Addons that WILL be ignored (Protected from updates) have their own category on the addons list. Scroll down to the bottom.
I don't see this at all, using the same version as you are.
If I right-click on the ignored addon, it still says it's ignored -- at least, it has a "stop ignoring this addon" entry on the menu. But there's no separate category at the bottom for it. Is there an option to enable that list?
Yes, I suppose throwing out all the work that's already gone into WAU is one possible solution. A less drastic approach might be to accept some constructive criticism, and incorporate that feedback into making the existing WAU a better program.
If you actually tried it, though, you would see that when the updater gets to that mod, it will say something like "IGNORED... Skipping".
Not to be rude, but that's rather poor design. Up until the user presses the Big Red Go Button, there's no visual feedback on whether or not the addon will actually be ignored or overwritten. If the user has made a mistake or forgotten to change the setting, they have no way of knowing until they click go, and then it's too late.
A suggestion on the confirmation box. Right now it asks the user if they're sure they want to update the marked addons. If the user answers yes, it changes the view to show *only* the list marked addons, as it updates them.
You might show that list before popping up the confirmation screen, so the user can see everything he's marked all at once before confirming.
I clicked "ignore flexbar2". It blanked the list, redrew the list from the beginning, cleared the addons that I had already checked, but FlexBar2 was still present, still shown, still there if I chose "mark installed," etc. No change at all.
Can individual addons be marked as "never update this"?
Right now I'm using "mark all installed addons" but then have to go through and uncheck a couple of addons which I do not want to change. If I could permanently "pin" those to their current versions, updating would be much faster.