Ian Semmel wrote:
>>
What is the best (cheapest, smallest bandwidth, easiest to code) way to
publish updates to my .Net application?
Well, two out of three ain't bad.
Actually, my experience has proven that you'd obtain 3 out of 3 using
ClickOnce!
Apart from what's already been mentioned, ClickOnce will only download
what needs to be updated. Some of my applications use 3rd party DLL's
etc and, because of this, these application can blow-out to greater than
30 or 50MB for the initial installation. Once the application is
installed, I've found that subsequent updates only download the
"changed" items, and as this is usually just my main code, ends-up being
less than 2MB. I have many Users who have low-bandwidth Internet
connections, and these Users are very pleased that updates take no time
at all to complete.
Yes, ClickOnce would be my recommendation as it meets all of your
requirements. I distribute my apps and updates this way and would never
consider any of the other options being promoted, and I have tried other
options. Those that are criticising ClickOnce obviously haven't ever
used it!
ShaneO
There are 10 kinds of people - Those who understand Binary and those who
don't.