Update notification fail
-
Now, which option should I choose?
-
FILE_NOT_FOUND, obviously.
-
The deactivated "close" button is classic.
-
-
What the...?
Is that program trying to use IE to scrape their update-notification webpage, and then display the output in a messagebox?
-
I think they are rather downloading their own page directly and stripping all HTML off it. And they use IIS and didn't think that through.
-
@PSWorx said:
I think they are rather downloading their own page directly and stripping all HTML off it. And they use IIS and didn't think that through.
That looks like IE's page it displays when it has trouble resolving a host name, not like a 404 from IIS.
-
@toth said:
@PSWorx said:
I think they are rather downloading their own page directly and stripping all HTML off it. And they use IIS and didn't think that through.
That looks like IE's page it displays when it has trouble resolving a host name, not like a 404 from IIS.What happened to me in a similar situation: I had a file on a server indicating the current version; the app checked that to see if it needed to update (this was before VS offered you default functionality to do this).
This worked fine when the server was available. But when the host had some kind of problem and the page wasn't available for a short time, it turned out I hadn't really thought it through. It resulted in a couple hundred mails if I recall correctly.
Then again, it's good to see people are actually using your app.
-
@b-redeker said:
This worked fine when the server was available. But when the host had some kind of problem and the page wasn't available for a short time, it turned out I hadn't really thought it through. It resulted in a couple hundred mails if I recall correctly.
This reminds me of DC++ P2P application - it downloads (used to download? it's been years since I last ran it) an XML file to check if a new version is available (and additionally if the current version is deemed too old to be used). One day, this XML got somehow corrupted (not well-formed), and stayed that way for several days. The result was that DC++ crashed a few seconds after starting up.
