Re: Creat an Installation package for client and server
- From: "Dave Sexton" <dave@jwa[remove.this]online.com>
- Date: Tue, 28 Nov 2006 16:28:29 -0500
Hi,
I already stated that, of the three choices I supplied, #1 sounds like the
best choice to me. But if you feel like doing some coding, #2 could work as
well. #3 is a last resort - not using ClickOnce at all.
Have I misunderstood the problem at hand?
--
Dave Sexton
"piggy" <piggy@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:A59E825F-F8A3-4D98-AC4E-53A514813CC2@xxxxxxxxxxxxxxxx
Do you have any suggestions of the best way to do solve this? Appreciate
your help.
"Dave Sexton" wrote:
Hi,
ClickOnce cannot be configured to pass on updates when network
connectivity
is low, AFAIK.
--
Dave Sexton
"piggy" <piggy@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:754B9A3F-EC0A-4595-BA6B-C5A34A5C03B1@xxxxxxxxxxxxxxxx
I have read "Choose a ClickOnce update strategy" even before i asked you
the
question below. It is obvious that if there is no network connection,
there
is no update. When network is limited, how can i configure that the
application won't check for the update and download? Because of this
problem, i do think option 2 which is allow user to check for updates
maybe a
better choice since from here i can check for current network
connectivity
level.
"Dave Sexton" wrote:
Hi,
option 1 is what i thought as well. What i am not sure is i only
want
the
update to happen when the network is high which means that they can
only
do
when they are in the office. When they are on the roads, this
option
won't
happen, the update and download have to be ignored. Thanks,
That's an interesting point.
The application should work when there is no connectivity at all:
"Application updates require network connectivity. If a network
connection
is not present, the application will run without checking for updates,
regardless of the update strategy that you choose."
"Choosing a ClickOnce Update Strategy"
http://msdn2.microsoft.com/en-us/library/s22azw1e.aspx
(All citations in the remainder of this post refer to the document at
the
url above)
When there is limited connectivity, ClickOnce will still attempt to
download
any updates if you've configured it to do so.
If you will be making a lot of updates or if the speed at which
updates
are
downloaded and installed when a client has limited connectivity is
unacceptable, then you can do one of three things:
1. Choose the first option in your list (check after startup) and
configure
the update interval appropriately:
"For example, you may want to check each time the application runs, or
once
a week, or once a month. If a network connection is not present at the
specified time, the update check is performed the next time the
application
runs."
§ Specifying Update Intervals
2. Allow the user to choose when it's appropriate to check for
updates:
"For example, you might provide a "Check for Updates Now" menu item,
or
an
"Update Settings" dialog box with choices for different update
intervals."
§ Providing a User Interface For Updates
3. Use a standard "Setup and Deployment" project and require users to
periodically check an ftp site or web site for updates.
(You may even have one more option, which is xcopy deployment).
It sounds to me like option 1 is your best choice, but option 2 is
definitely worth consideration.
--
Dave Sexton
.
- Follow-Ups:
- References:
- Prev by Date: oops questions c#
- Next by Date: Re: How to get static IP or name from dynamic IP
- Previous by thread: Re: Creat an Installation package for client and server
- Next by thread: Re: Creat an Installation package for client and server
- Index(es):
Relevant Pages
|
