On 12/13/2010 4:00 AM, Grigore Dolghin wrote: > I used the same approach. The idea is the internet may be down, but the > server not, and the update would work. If the server itself is down there's > no point to update because the application can't run anyway. > > (In my particular case there was one more thing - The exe was pretty big and > I split it on multiple records (512k/record) so I could show a progress bar > to the user.)
My update sizes are pretty small, as I'm only sending pure updates....no runtimes, etc. And by checking a web database version field (yes, I put that in manually when I upload the _setup.exe), it's lean and only pulls what it needs. -- Mike Babcock, MCP MB Software Solutions, LLC President, Chief Software Architect http://mbsoftwaresolutions.com http://fabmate.com http://twitter.com/mbabcock16 _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[email protected] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
