D
Dave Sexton
Hi,
By "ftp file synch", do you mean that you'll write your own program that
monitors an ftp directory?
That would surely work, however that's basically what ClickOnce does anyway.
Automatically or on demand, ClickOnce will check whether a newer version is
available on a web server, download it and then install it. Why reinvent
the wheel?
BTW, the requirement to defer updates when the program detects low network
connectivity doesn't really make much sense anyway. What happens if the
program detects high connectivity, then the user moves to a place with low
connectivity, or no connectivity at all, while the download is in progress?
I think that allowing the user to choose when they will perform the update
is a good choice, but if coding ClickOnce to do this is too complex for you
then I can't see how a custom solution is going to be any easier to develop
unless you already "know" exactly how to do it.
GL
By "ftp file synch", do you mean that you'll write your own program that
monitors an ftp directory?
That would surely work, however that's basically what ClickOnce does anyway.
Automatically or on demand, ClickOnce will check whether a newer version is
available on a web server, download it and then install it. Why reinvent
the wheel?
BTW, the requirement to defer updates when the program detects low network
connectivity doesn't really make much sense anyway. What happens if the
program detects high connectivity, then the user moves to a place with low
connectivity, or no connectivity at all, while the download is in progress?
I think that allowing the user to choose when they will perform the update
is a good choice, but if coding ClickOnce to do this is too complex for you
then I can't see how a custom solution is going to be any easier to develop
unless you already "know" exactly how to do it.
GL